The Wire · Showcase
SUPABASE SHIPS CLICKHOUSE REPLICATION AND HARDENS CUSTOM AUTH
By RepoJournal · Filed · About Supabase
ClickHouse is now a first-class replication destination in Studio, gated behind a private alpha flag and built with client-side validation that blocks insecure and internal URLs.
The big move today is ClickHouse integration [1]. Studio now renders a full configuration form for ClickHouse destinations with URL, user, password, and database fields. The implementation includes client-side validation that rejects any target pointing to loopback addresses, RFC 1918 ranges, link-local ranges, CGNAT blocks, or IPv6 ULA space. This is security by default, not an afterthought. The flag is off by default, so you won't see this in production orgs yet. In parallel, the auth layer shipped support for multiple custom sign-in providers [2]. The UI now renders all configured custom providers on the sign-in page while staying backward compatible with the legacy single-provider setup. Over in go-tpc, error propagation got fixed [3]. TPCC subcommands were exiting with code 0 even on failure, masking preparation errors upstream. That's now corrected. The realtime team squashed a flaky reconnector test [4] that was making local development harder. Small fix, high signal-to-noise on CI runs.
One email a day. Unsubscribe in one click.
What actually shipped in Supabase, written up every day — commits, pull requests, releases, and security advisories.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → If running ClickHouse replication, reach out to sales to enable the private alpha flag supabase/supabase [plan]
- → Review custom auth provider config if you're using multiple sign-in options - migration is backward compatible supabase/supabase [monitor]
- → Upgrade go-tpc if you're running TPCC benchmarks - error handling is now reliable supabase/go-tpc [plan]
References
- [1] feat(studio): add ClickHouse replication destination ↗ supabase/supabase
- [2] Add support for multiple custom auth providers in custom-content (#48030) supabase/supabase
- [3] Propagate errors to top-level for TPCC ↗ supabase/go-tpc
- [4] chore: fix reconnector flaky test ↗ supabase/realtime