Skip to content
Data warehouse ⇄ Database

Starburst Enterprise to Supabase integration — real-time, two-way sync

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.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Starburst Enterprise and Supabase

Connect Supabase and Starburst Enterprise with one live, two-way sync: operational rows flow into the warehouse, and computed results flow back where systems can read them fast.

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.

Common use cases

  • 01 Write curated or reconciled results back to lakehouse tables through connectors that support inserts
  • 02 Read federated views that join warehouse, lake, and database tables, then sync the result into operational tools like a CRM
  • 03 Reflect auth.users state into support and CRM systems so teams see account status without querying the database
  • 04 Push product events captured in Supabase Postgres to marketing tools for lifecycle campaigns

Common sync patterns

Offload heavy reads

Point analytical queries at the synced copy in Starburst Enterprise and keep Supabase focused on its operational workload.

Operational data in the warehouse, minus the pipeline

Rows from Supabase land in Starburst Enterprise as they change, replacing hand-built CDC and batch extract jobs.

Serve warehouse results at database speed

Aggregates or model outputs computed in Starburst Enterprise sync into Supabase, where whatever reads from that database gets them without querying the warehouse.

What you can sync between Starburst Enterprise and Supabase

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 How this pairing syncs
Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. Schemas Namespaces (public and custom) that scope sync access. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping.
Tables Queryable relations; writes pass through to sources whose connectors support them. Tables Standard Postgres tables; the primary two-way sync target. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Views Engine-level SQL views used to shape federated data before syncing it out. Views Read-side projections exposed to outbound syncs. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Materialized views Precomputed results that make repeated sync reads cheaper. JSONB Columns Semi-structured payloads such as event properties or nested objects. Materialized views is specific to Starburst Enterprise and JSONB Columns to Supabase — each maps to any object or custom field on the other side.
Columns Typed per the Trino type system, mapped from each source's native types. Database Functions Postgres functions that can transform or validate synced rows. Columns is specific to Starburst Enterprise and Database Functions to Supabase — each maps to any object or custom field on the other side.
Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. Storage Object Metadata File metadata rows that can be joined to synced application data. Catalogs is specific to Starburst Enterprise and Storage Object Metadata to Supabase — each maps to any object or custom field on the other side.

How changes propagate between Starburst Enterprise and Supabase

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Starburst Enterprise Supabase Interval-based propagation

DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.

DeliveryEach detected change is applied to Supabase as a row-level write, with types converted between the two schemas.

Supabase Starburst Enterprise Sub-second propagation

DetectionSupabase pushes changes as they happen — webhook events backed by change data capture. Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime.

DeliveryEach detected change is applied to Starburst Enterprise as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
  • Supabase: SQL access is bounded by connection limits (pooled connections are provided); the REST layer is subject to the platform's limits.
What ships with Starburst Enterprise ⇄ Supabase

Connect Starburst Enterprise and Supabase for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Starburst Enterprise–Supabase connection.

Real-time

Two-way sync

Changes in Starburst Enterprise or Supabase instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Starburst Enterprise or Supabase data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Starburst Enterprise or Supabase record.

Observability

Monitoring

Track your Starburst Enterprise ⇄ Supabase sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Starburst Enterprise and Supabase.

How the Starburst Enterprise and Supabase connectors work

Starburst Enterprise

Integration surface
ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
Authentication
Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
Change detection
Query-based polling; Starburst is a query engine and exposes no change log of its own
Capabilities
read · write
Rate limits
Throughput is governed by cluster sizing and resource groups rather than API quotas

Supabase

Integration surface
Direct PostgreSQL wire protocol connection, plus an auto-generated REST API (PostgREST)
Authentication
Database credentials (connection string) for SQL access; API keys (anon / service role) for the REST layer
Change detection
Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes
Capabilities
read · write · CDC · webhooks
Rate limits
SQL access is bounded by connection limits (pooled connections are provided); the REST layer is subject to the platform's limits
How it works

How to connect Starburst Enterprise to Supabase — three steps, no code

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.

  1. 01

    Connect your apps

    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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Starburst Enterprise connected
    Supabase connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Starburst Enterprise ⇄ Supabase
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Starburst Enterprise Supabase
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Starburst Enterprise and Supabase integration FAQ

SECURITY

Security teams trust Stacksync

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.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 470 integrations available for Starburst Enterprise and Supabase.

Popular · 4 of 470
All Starburst Enterprise integrations All Supabase integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own