---
title: "Whitepapers: technical guides on real-time data sync"
description: "In-depth whitepapers on two-way sync, CDC, conflict resolution, and enterprise data architecture. Written by the engineers who built Stacksync."
canonical: https://www.stacksync.com/whitepapers
last_modified: 2026-07-05
---

# Engineering *whitepapers*

> For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md

In-depth technical references on real-time, two-way sync between CRMs, ERPs, and databases. Written by the engineers who built Stacksync.

Stacksync publishes free technical whitepapers on two-way sync, change-data-capture, conflict resolution, enterprise data architecture, and EDI modernization. Written by the engineers who built the platform, peer-reviewed by Stacksync co-founders and customer experts.

Featured Whitepaper

## The complete architecture guide for real-time two-way sync

Reference architectures for real-time two-way sync, plus conflict-resolution patterns that survive schema drift. Co-authored by engineering leaders from Supabase, Coalesce, and Stacksync.

2026 edition 4,000+ downloads Free PDF

Stacksync 2026 edition

The complete **architecture guide** for real-time two-way sync

More from Stacksync

## Other ways to go deeper.

Whitepapers are one slice of the engineering-first material we publish. If you want to go further on a topic, implementation guides, reference docs, customer architectures, and live demos sit alongside the papers.

### Demos

Interactive product walkthroughs of the connector library, schema mapping, and conflict policies, without booking a sales call.

Watch demos

### Documentation

Connector setup, schema configuration, and conflict-resolution patterns. Code samples for every endpoint, written by the team that ships them.

Read the docs

### Hands-on labs

Build a real-time Salesforce↔Postgres sync in 15 minutes, in your own sandbox. No credit card, no sales prerequisite.

Start a lab

### Product news

Release notes, new connectors, and platform changes, short, technical, and shipped weekly. Subscribe by RSS or email.

See releases

### Customer stories

How NetSuite, Shopify, and Salesforce teams use Stacksync as their integration substrate, architecture diagrams included.

Browse stories

### Reports

State of real-time integration: benchmarks, common failure modes, and an inventory of what teams replace when they adopt Stacksync.

Get the report

FAQ

## Frequently asked questions

### Are Stacksync whitepapers free to download?

Yes, every whitepaper is free. Some require an email address so we can notify you when an updated version is published; the email gate is opt-in, not required. Direct PDF links are available on each whitepaper page once you accept the terms. You control any follow-up: the guide arrives by email and every message includes a one-click unsubscribe.

### Do I need to provide my email?

Email is optional. Whitepapers can be read inline on the page without providing any identifying information. Providing an email gets you the PDF for offline reading and lets us notify you when the whitepaper is updated. Stacksync does not share your email with third parties.

### Can I cite Stacksync whitepapers in academic work?

Yes, Stacksync whitepapers are public technical references, suitable for citation in academic and industry research. Each whitepaper has a stable URL and a published date for citation purposes. For citing internal benchmarks or unpublished data, email research@stacksync.com to coordinate methodology details.

### Are whitepapers updated when the product changes?

Yes, whitepapers are reviewed quarterly. Major updates trigger a new version number and a fresh published date; the original URL stays the same. Minor corrections are noted in the changelog at the bottom of each paper. If you have the email-update opt-in, you receive a notification with a summary of what changed.

### Who writes Stacksync whitepapers?

Stacksync whitepapers are written by the engineering and product teams that build the platform, not by an outsourced content agency. Each paper goes through peer review with at least one Stacksync co-founder and at least one customer or industry expert before publication. Bylines are attributed to the primary author with contributor credit at the bottom.
