Two-way sync
Changes in Azure Cosmos DB or Supabase instantly reflect in both systems. No stale data, no manual imports.
Keep Azure Cosmos DB 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.
Two databases that must agree is one of the oldest problems in engineering: different engines for different workloads, separate services with overlapping reference data, a migration in flight, or regional instances that share a subset of records. Hand-rolled replication across systems means change capture, conflict handling, and type mapping, all built and maintained by your team.
Stacksync syncs tables or collections between Azure Cosmos DB and Supabase continuously and bi-directionally, translating types between the two engines and resolving conflicts by rules you configure. Rows written on either side appear on the other within seconds.
Keep the same dataset live in both Azure Cosmos DB and Supabase, so each workload runs on the engine that suits it.
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
Services that own separate databases stay consistent on the records they share, without a custom replication layer.
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.
| Azure Cosmos DB objects | Supabase objects | |
|---|---|---|
| Databases Top-level namespaces that scope containers and throughput provisioning. | JSONB Columns Semi-structured payloads such as event properties or nested objects. | |
| Containers The unit of partitioning and throughput; each container maps to a synced collection. | Database Functions Postgres functions that can transform or validate synced rows. | |
| Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. | Storage Object Metadata File metadata rows that can be joined to synced application data. | |
| Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. | Tables Standard Postgres tables; the primary two-way sync target. | |
| Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. | Views Read-side projections exposed to outbound syncs. | |
| Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. | Schemas Namespaces (public and custom) that scope sync access. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Cosmos DB–Supabase connection.
Changes in Azure Cosmos DB or Supabase instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Azure Cosmos DB 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 Azure Cosmos DB or Supabase record.
Track your Azure Cosmos DB ⇄ Supabase sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Azure Cosmos DB 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 Azure Cosmos DB 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 Azure Cosmos DB 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 Azure Cosmos DB and Supabase: authenticate both systems, choose the objects to sync (such as Azure Cosmos DB's Databases and Containers), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Azure Cosmos DB and Supabase: Cross-engine sync; Migration with zero-downtime cutover; Shared reference data between services. Keep the same dataset live in both Azure Cosmos DB and Supabase, so each workload runs on the engine that suits it.
Azure Cosmos DB: REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces. Authentication: Account keys, resource tokens, or Microsoft Entra ID role-based access. 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.
Azure Cosmos DB: Throughput is provisioned in request units per container or database, which means sync read and write volume has a direct cost and throttling dimension. Supabase: PostgREST auto-generates a REST endpoint per table, with Row Level Security policies gating access at the row level. Stacksync's field mapping accounts for these differences between Azure Cosmos DB and Supabase without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Azure Cosmos DB and Supabase records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Azure Cosmos DB and Supabase connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Azure Cosmos DB–Supabase integration in-house.
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 Azure Cosmos DB and Supabase.