Two-way sync
Changes in Exasol or Supabase instantly reflect in both systems. No stale data, no manual imports.
Keep Exasol 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 Exasol, 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 Exasol in real time, and result tables in Exasol sync back into Supabase, with schema and type mapping between the two systems handled for you.
Aggregates or model outputs computed in Exasol sync into Supabase, where whatever reads from that database gets them without querying the warehouse.
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Point analytical queries at the synced copy in Exasol and keep Supabase focused on its operational workload.
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.
| Exasol objects | Supabase objects | |
|---|---|---|
| Views Read-only query surfaces often used as curated sources for reverse ETL. | Tables Standard Postgres tables; the primary two-way sync target. | |
| Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. | Views Read-side projections exposed to outbound syncs. | |
| UDF scripts In-database functions that can transform synced data after load. | Schemas Namespaces (public and custom) that scope sync access. | |
| Users and roles Grant read/write access for the dedicated integration account. | auth.users Managed authentication users, often mirrored into CRM or support systems. | |
| Schemas Namespaces that group the tables a sync reads from or writes into. | Row Level Security Policies Row-level access rules that govern what the REST layer exposes. | |
| Tables Primary sync target; columnar relational tables written with standard SQL. | JSONB Columns Semi-structured payloads such as event properties or nested objects. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Exasol–Supabase connection.
Changes in Exasol or Supabase instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Exasol 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 Exasol or Supabase record.
Track your Exasol ⇄ Supabase sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Exasol 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 Exasol 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 Exasol 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 Exasol and Supabase: authenticate both systems, choose the objects to sync (such as Exasol's Views and Virtual schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Exasol: Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients. 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 Exasol side: UDF scripts, Users and roles, Schemas, Tables, plus custom fields where Exasol exposes them. On the Supabase side: Schemas, auth.users, Row Level Security Policies, JSONB Columns. 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.
Common patterns for Exasol and Supabase: Serve warehouse results at database speed; Fresh analytics without loading windows; Offload heavy reads. Aggregates or model outputs computed in Exasol sync into Supabase, where whatever reads from that database gets them without querying the warehouse.
Exasol: SQL over JDBC/ODBC drivers and a WebSocket-based client protocol. Authentication: Database credentials (username and password). Supabase: 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. Stacksync manages authentication, retries, and rate limits on both sides.
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 Exasol and Supabase.