Skip to content

Real-time two-way sync between Supabase and SQL Server

Map the fields once, and every write moves both ways in milliseconds. Supabase row inserts land in SQL Server, SQL Server updates land back in Supabase.

public.customers Database SQL Server public.customers Database SQL Server
<200ms
p95 propagation
$100
Free credits
SOC 2
ISO 27001 · HIPAA

Trusted by fast-scaling teams, from YC startups to enterprise platform teams

Capabilities

Everything you need to sync SQL Server

Connects over SQL over the TDS wire protocol (Tabular Data Stream), via ODBC/JDBC/ADO.NET drivers, mapped field-by-field into Supabase, with row-level audit and no backend of your own to run.

Two-way, not one-way

Every table maps to a SQL Server object both ways. Insert a row in Supabase and it lands in SQL Server; update a record there and Supabase reflects it back.

Live, not batched

SQL Server Native Change Data Capture. Changes land in Supabase in milliseconds, not on the next polling cycle.

Databases Two-way synced
Schemas Two-way synced
Tables Two-way synced

Every object, standard or custom

Any object the API exposes can be mapped into Supabase, with schema discovery doing the field-matching for you.

Use cases

What teams ship first

Patterns a two-person team can ship in a week. Any table in Supabase maps to any object in SQL Server.

Real-time

Two-way sync

Changes in SQL Server instantly reflect in Supabase, and back. No stale data, no manual imports.

Bi-directional sync between SQL Server rows and Supabase tables, so .NET line-of-business apps and modern product tools share one dataset.

Expose Supabase records as SQL Server tables that existing SSRS reports and internal .NET apps can query.

Mirror on-premises ERP data held in SQL Server into Supabase, for cloud CRM and support systems to read.

Feed a warehouse from both SQL Server and Supabase continuously with native CDC, instead of SSIS batch jobs.

Why builders sync Supabase and SQL Server

Ship without a backend

No custom ETL jobs, webhooks, or sync scripts to write and maintain. Map Supabase tables to SQL Server objects like Databases and Schemas once, and every write stays in sync from there on.

Every write moves both ways

Changes in Supabase reach SQL Server in real time, and back. databases, schemas and tables stay consistent everywhere they live.

Built to run in production

Your Supabase write-ahead log is read directly, and SQL Server changes are picked up the moment they happen, so sync keeps pace with live traffic. No polling delays, rate limits, or extra load on your database.

How it works

Four steps, and no backend to maintain

01

Connect

OAuth your project and the system. Schemas read automatically.

02

Map

Tables to objects, fields to fields. Transforms run inline.

03

Sync

Historical backfill, then continuous CDC both ways.

04

Monitor

Row-level logs, latency and one-click replay.

Sync Supabase with SQL Server
from React

One client, the same auth as your Supabase project. If you know the Supabase client, you already know this one.

Read the docs
import { createClient } from '@stacksync/client'const stacksync = createClient(  process.env.SUPABASE_URL,  process.env.STACKSYNC_API_KEY)export default function Deals() {  const [deals, setDeals] = useState([])  useEffect(() => {    stacksync.from('deals').select('*')      .then(({ data }) => setDeals(data))  }, [])  return <DealList items={deals} />}
Pricing

Free for Supabase builders

Normally $1,000/mo. Yours at $0 during launch week.

Launch week: 10,000 accounts only
Supabase Connect
$1,000 $0 / month

Plus $100 in sync credits on the house. No card, no sales call, the same self-serve start you got with Supabase.

7,840 of 10,000 claimed2,160 left

Takes about 2 minutes · cancel in one click · export every mapping you build

  • 1 active two-way sync, real-time
  • AI agents and MCP servers
  • Workflows on any synced change
  • 3 collaborators
  • Migration review with a Stacksync engineer

“We went from treating data integration as a necessary evil that consumed our best engineers to having it just work, reliably, at scale, in real-time.”

Alex Marinov · VP of Technology, ACERTUS

Trusted by 1,000+ teams · SOC 2 Type II · ISO 27001

Security

Security teams trust Stacksync

The integration layer is where compliance reviews stall. Row-level audit, residency and DPF certification for US, EU, UK and CH transfers, so procurement is a form, not a quarter.

Learn more about security
SOC 2 Type II SOC 2 Type II
ISO 27001 ISO 27001
HIPAA BAA HIPAA BAA
GDPR GDPR
CCPA CCPA
CSA STAR CSA STAR
DPF US-EU-UK-CH
→ Security with benefits

SSO & SCIM

Okta, Azure and Google SSO, with SCIM provisioning.

Alerts

Sync issues to email, Slack, PagerDuty or WhatsApp, with retry and revert.

Secure connections

Connects to your systems your way.

OAuth 2SSH tunnellingSSL certificatesIP whitelistingVPN gatewayVPC peering
FAQ

Supabase + SQL Server FAQ

How does Supabase sync with SQL Server?

Stacksync watches your Supabase tables via CDC and SQL Server's API in real time. A write on either side maps to fields on the other and propagates in milliseconds, with row-level logs for every change.

Is the Supabase + SQL Server sync two-way?

Yes. Changes made in Supabase propagate to SQL Server and vice versa. One-way flows are also supported when a direction should stay read-only.

Do I need to write backend code to connect Supabase and SQL Server?

No. Authenticate both systems, pick objects and fields to map, and enable the sync. Most integrations go live in minutes with no infrastructure to manage.

Is my SQL Server and Supabase data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, HIPAA, GDPR, CCPA and CSA STAR certified, and holds the EU-US, UK and Swiss Data Privacy Framework (DPF) certification. Data is encrypted in transit, with a zero-persistent-storage architecture: records aren't retained after a sync operation.

Sync Supabase and SQL Server this afternoon