Skip to content
Database

Connect TiDB to any app with two-way sync.

Two-way sync TiDB across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • 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
Object catalog

What Stacksync syncs in TiDB.

These objects sync between TiDB and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where TiDB exposes them.

Databases
MySQL-style schemas addressed by any MySQL-compatible client.
Tables
Row data stored in TiKV; the primary unit for reads, writes, and CDC.
Views
Logical views for shaping reads before syncing outward.
Columns
MySQL-compatible types mapped to fields in the paired system.
Indexes
Secondary indexes that keep incremental sync queries efficient.
Sequences
Server-side ID generation relevant when external systems write rows.
API surface

How Stacksync connects to TiDB.

The connector runs on TiDB's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection
MySQL wire protocol (SQL)
Authentication
Database credentials (MySQL-compatible username/password)
Change detection
Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works
Rate limits
Throughput scales with cluster size rather than fixed API quotas

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Supported
  • Webhooks Not available
What ships with TiDB

Connect TiDB for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in TiDB instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever TiDB 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 TiDB record.

Observability

Monitoring

Track your TiDB sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the TiDB connector.

TiDB is bought by platform and data engineering teams running MySQL-family workloads that have outgrown a single node; PingCAP positions it as a MySQL-compatible distributed SQL database that serves transactions and real-time analytics (HTAP) on the same data. It typically sits as the system of record behind fintech ledgers, multi-tenant SaaS, and operational-intelligence workloads, so it accumulates high-volume transactional data the rest of the stack needs to read.

  • Data engineering
  • Database administrators
  • Platform engineering
  • Backend engineers

  1. Two-way sync between TiDB tables and SaaS tools so operational edits made in either system converge

  2. Stream row-level changes to a warehouse or Kafka via CDC for near-real-time analytics

  3. Consolidate formerly sharded MySQL workloads into TiDB and sync the unified data outward to business systems

  4. Serve mixed transactional and analytical workloads on synced data using TiFlash columnar replicas

  5. Sync CRM or ERP records into TiDB Tables so customer-facing applications query operational data over the MySQL protocol, with changes written back to the source system.

  6. Replicate curated TiDB Views or Tables into a downstream warehouse or reporting database without building custom pipelines.

All TiDB integrations

Pick the system you need to keep in sync with TiDB. Each page covers the sync setup, field mapping, and common workflows for that pair.

CRM · 30

ERP · 24

Database · 13

Data warehouse · 9

Business productivity · 28

Accounting and finance · 13

How it works

Set up TiDB in minutes, without APIs.

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 TiDB with its 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
    TiDB connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the TiDB objects to sync — Stacksync auto-detects the schema, 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 · TiDB
    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
    TiDB database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo

FAQ

TiDB connector FAQ

What can I sync with the TiDB connector?

TiDB's core objects — Databases, Tables, Views, Columns and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to TiDB?

Via MySQL wire protocol (SQL), authenticated with Database credentials (MySQL-compatible username/password). Changes are detected as follows — log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works. Stacksync manages rate limits, retries, and schema changes automatically.

Is the TiDB connector two-way?

Yes. Changes made in TiDB propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does a TiDB integration take to set up?

Most TiDB integrations go live in minutes: authenticate TiDB and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is TiDB data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. TiDB data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

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
CSA STAR
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
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