Join the waitlist
// Two-way sync · Airtable ⇄ Google Sheets

Two-way sync
that can prove it.

Most tools claim two-way sync. We measured how they actually behave — phantom updates, silently vanishing edits, deletes that never propagate. SyncPair is a sync engine with a full audit trail: no edit is ever lost silently.

01 / What we measured

Your current sync is broken in ways it can't tell you about.

Before writing a line of product code, we instrumented the Airtable and Google Sheets APIs and ran naive two-way sync the way the popular automation tools do it. These aren't hypotheticals — every number below is a measured result.

EXPERIMENT E3
1 → 3one inserted row, three false “updates”

Phantom updates

Insert a single row mid-sheet and position-based triggers report every shifted row as “edited.” Sorting flagged 5 of 6 untouched rows. With sync running, each phantom becomes a real write to the other side.

EXPERIMENT E5
3 secuntil the losing edit vanished — unlogged

Conflicts decided by luck

Two people edit the same record within one poll cycle. The “winner” is whichever poll happens to fire first. The losing value appeared in no event, no log, no history — it simply ceased to exist.

EXPERIMENT E4
0events emitted for a deleted record

Deletes are invisible — or worse

An Airtable delete produces zero events, ever. A Sheets delete fires a storm of fake “edits” to every row below it — and can silently hand the dead row's identity to its neighbor.

EXPERIMENT E2
loop, from one date-format mismatch

Stability by accident

When a naive sync loop “works,” it's because of an undocumented platform quirk — not design. One type coercion, one timestamp column, one trailing space, and it echoes forever: a write per minute, silently burning quota.

// Measured 2026-07-06 against live Airtable + Google APIs. Full methodology available on request.

02 / How SyncPair is different

An engine that owns the truth — not glue that hopes.

The platforms give you snapshots, not events: no changed-field list, no old values, no writer identity. Reliable sync means the engine keeps its own state. Every component below exists because a measured failure demanded it.

/01

Identity ledger

Every record mapped by durable ID — survives inserts, sorts, and renames without duplicates or orphans.

/02

Echo suppression

Origin-tagged writes and content hashing. Our own writes can never boomerang back as “changes.” No loops, by design.

/03

Conflict journal

Concurrent edits are detected, both values are kept, your policy picks the winner — and the loser is never silently discarded.

/04

True delete handling

Deletes are detected by ledger sweep, propagated exactly once, and tombstoned so they can never resurrect from the other side.

/05

Restart-safe

Downtime backlog replays through the same audited pipeline — no double-applies, no catch-up floods, no ghost records.

/06

Audit feed

Every synced change, conflict, and delete in one reviewable trail. When someone asks “what touched this record?” — you have the answer.

19:06:38Z SYNC Orders!rec8Kd31 → Sheet1!A17 field: Status “Packed” → “Shipped” 19:07:02Z SYNC Sheet1!A22 → Orders!recQz90 new record created (ledger key L-0142) 19:07:14Z CONFLICT Orders!rec2Vb77 — both sides edited within window policy “newest wins” applied · losing value journaled, recoverable 19:08:00Z DELETE Orders!recM3x08 → row removed · tombstoned (no resurrection)
03 / Pairs

One pair. Flat price. Done properly.

No per-row metering, no per-seat creep. You pay for a synced pair that works and can prove it. Founding waitlist members lock in launch pricing.

● First release

Airtable ⇄ Google Sheets

True bidirectional create / update / delete, with the full audit feed.

○ Roadmap

Google Sheets ⇄ monday.com

Vote for your pair when you join the waitlist — demand sets the order.

04 / Early access

Stop hoping your sync worked.

Join the waitlist for early access and founding-user pricing. We'll also send you the full failure-mode write-up — useful even if you never buy.

No spam — product updates only. Unsubscribe anytime.