GoSync
Offline sync engine, self-hosted- gosync-server (one binary)
- SQLite file, or your Postgres
- Cost
- Free, MIT licensed. You pay only for your own server.
- Pick it when
- Offline writes on servers you control, with the least to operate.
For web apps that have to work where the internet doesn't.
Offline writes, real-time across devices, conflicts merged for you. One small Go binary on servers you control.
An illustration of how GoSync behaves, simulated in your browser. People, places and numbers are fictional.
GoSync isn't for every app. Answer four questions about yours and follow the lit wire. If another tool fits better, we'll tell you which.
Offline writes, on servers you control, without adopting a database platform: one small binary with SQLite or Postgres, and a client that handles the outbox, merging and tabs for you.
Start with the Quick Start →Every option below is good at something. The difference is what you deploy, what you operate, and whether people can keep working offline. Outlined blocks are things you run yourself.
Facts checked against each project's own docs and announcements, October 2026. Spotted something out of date? Tell us.
No schemas to declare and no sync code to write. Read and write a local database; GoSync handles offline, real-time and conflicts.
Apps keep reading and writing without internet. Changes sync automatically when the connection returns.
Each device downloads only what changed since its last sync and uploads only its own pending writes. Batched, compressed and safe to retry.
Every field is merged independently on a hybrid logical clock. Concurrent edits to different fields both survive, and every device converges.
JWT auth with your own secret or any JWKS provider (Auth0, Clerk, Supabase, Firebase). Every user's data is isolated on the server.
Data lives in IndexedDB, not localStorage, so it isn't capped at 5 MB and survives reloads, restarts and crashes.
The server compiles to a single, static binary. No JVM, no Python runtime, no complex environment setup required.
Don't just build apps. Build resilient systems that survive the chaos of the real world.
Signal drops in basements and rural areas. The app spins. Data is lost.
Internet goes down during the morning rush. The POS stops. Revenue stops.
Two users edit the same ticket. "Last write wins" overwrites everything.
Each next step closes a gap we listed above. No promised dates: the order follows what people building with GoSync need most.
Go compiled to WebAssembly, syncing IndexedDB over WebSockets.
It proved the idea, and showed what was missing: anyone could read anyone's data, and old writes could overwrite new ones. So v2 started from scratch.
Offline outbox, per-field conflict merging, auth, multi-tab, PostgreSQL scale-out, metrics.
Tested in Chromium, Firefox and WebKit, and under load: 1,000+ writes a second with p99 under 100 ms.
Sync images and documents with the records they belong to.
Field work runs on evidence: a receipt, a crop, an ID card. Today you upload those separately.
Rules that decide which records each person downloads.
A health worker needs her own households, not the whole region's, on a small phone.
useCollection('todos') instead of wiring watch() to state yourself.
Less glue code in the most common way GoSync is used.
A command-line view of a device's outbox, cursor and recent changes.
When something looks wrong in the field, you should see exactly what's waiting and why.
Character-level merging for fields many people edit at once.
Shared notes shouldn't lose a paragraph when two people type together.
Android and iOS libraries alongside the web client.
GoSync works on phones as a web app today; some teams need native apps.
Building something that needs one of these, or something else? Tell us what you're building →