Two-way sync
Changes in Starburst Enterprise or Supabase instantly reflect in both systems. No stale data, no manual imports.
Keep Starburst Enterprise and Supabase in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Operational databases and analytical warehouses want the same data at different moments. Analysts want Supabase's rows in Starburst Enterprise, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in Supabase where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in Supabase sync into Starburst Enterprise in real time, and result tables in Starburst Enterprise sync back into Supabase, with schema and type mapping between the two systems handled for you.
Point analytical queries at the synced copy in Starburst Enterprise and keep Supabase focused on its operational workload.
Rows from Supabase land in Starburst Enterprise as they change, replacing hand-built CDC and batch extract jobs.
Aggregates or model outputs computed in Starburst Enterprise sync into Supabase, where whatever reads from that database gets them without querying the warehouse.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Starburst Enterprise objects | Supabase objects | |
|---|---|---|
| Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | Database Functions Postgres functions that can transform or validate synced rows. | |
| Tables Queryable relations; writes pass through to sources whose connectors support them. | Storage Object Metadata File metadata rows that can be joined to synced application data. | |
| Views Engine-level SQL views used to shape federated data before syncing it out. | Tables Standard Postgres tables; the primary two-way sync target. | |
| Materialized views Precomputed results that make repeated sync reads cheaper. | Views Read-side projections exposed to outbound syncs. | |
| Columns Typed per the Trino type system, mapped from each source's native types. | Schemas Namespaces (public and custom) that scope sync access. | |
| Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | auth.users Managed authentication users, often mirrored into CRM or support systems. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Starburst Enterprise–Supabase connection.
Changes in Starburst Enterprise or Supabase instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Starburst Enterprise or Supabase data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Starburst Enterprise or Supabase record.
Track your Starburst Enterprise ⇄ Supabase sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Starburst Enterprise and Supabase.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate Starburst Enterprise and Supabase with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Starburst Enterprise and Supabase objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Starburst Enterprise and Supabase: authenticate both systems, choose the objects to sync (such as Starburst Enterprise's Schemas and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Starburst Enterprise and Supabase connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Starburst Enterprise–Supabase integration in-house.
Yes — Stacksync ships production-grade connectors for both Starburst Enterprise and Supabase. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Starburst Enterprise: Query-based polling; Starburst is a query engine and exposes no change log of its own. On Supabase: Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Starburst Enterprise side: Tables, Views, Materialized views, Columns, plus custom fields where Starburst Enterprise exposes them. On the Supabase side: Storage Object Metadata, Tables, Views, Schemas. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Starburst Enterprise and Supabase.