v2.0 is live

For web apps that have to work where the internet doesn't.

GoSync

Offline writes, real-time across devices, conflicts merged for you. One small Go binary on servers you control.

Open Source (MIT)
Go server · WebAssembly client
Self-Hosted
A real day, scroll to live it

One day. Almost no signal.

07:30
TownHillsideBus stopRiver villageTown
07:305G 93%
Today's visits0/23
Up to date
  • No visits yet
Regional officegosync-server · the office PC
0of 23 visits received
Nothing yet today

An illustration of how GoSync behaves, simulated in your browser. People, places and numbers are fictional.

  1. 07:40 · Leaving town. Amara is a community health worker. Today: 23 household visits across two villages, most of them with no signal at all. Her app loads once, here, on town 5G.
  2. Hillside · no signal. Each visit saves instantly on the phone. No spinner, no retry button. Visits waiting to be sent sit in an outbox on the device. Without GoSync: Forms that refuse to submit, or entries lost when the page reloads.
  3. Bus stop · one bar, six minutes. Enough. Only the 8 new visits travel, a few kilobytes, and the regional office sees them before the bus leaves. Without GoSync: A full re-upload that times out, or duplicates when the retry fires twice.
  4. Same house, two people. At the office, the supervisor corrects Ana Lima's phone number. In the river village, offline, Amara records her second tetanus dose. Neither knows about the other.
  5. Merged, not overwritten. Different fields, different people: both changes survive. The phone and the server end up with exactly the same record. Without GoSync: Whoever syncs last silently erases the other person's change.
  6. Battery 3% · app closed. Five visits are still waiting. Closing the app, a reboot, a crash: the outbox lives in the phone's storage, not in memory. Without GoSync: Unsent work lives in memory and dies with the app.
  7. Back in town. Everything sends on its own. 23 visits, none lost, none duplicated. The server is one small program on the regional office's own machine.
  8. 23 visits recorded, all delivered.
Honest routing

Is GoSync the right tool? Flip the switches.

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.

yesnonoyesyesnonoyesyesnoyesnoQ1Q2Q4Q3Q4Q4Yjs or AutomergeZeroFirebase or Supabase RealtimePowerSync CloudFirebasePowerSync Open EditionGoSyncyour app
This is what GoSync is for

GoSync

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 →
The honest comparison

What you'd actually have to run.

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.

GoSync

Offline sync engine, self-hosted
You run 2 things
  • gosync-server (one binary)
  • SQLite file, or your Postgres
Offline writesBuilt in: outbox, retries, per-field merge
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.

Firebase

Google's managed database
Vendor runs it
  • Runs on Google Cloud. Can't be self-hosted.
Offline writesBuilt in (Firestore offline persistence)
Cost
Free tier, then billed per document read, write and delete, plus storage.
Pick it when
You want nothing to operate and Google Cloud is acceptable.

PowerSync

Sync layer for your existing database
You run 4 things
  • PowerSync service
  • Storage database (Postgres or MongoDB)
  • Your source database
  • Your write API (uploadData)
Offline writesBuilt in; writes go through an API you build
Cost
Open Edition free (source-available). Cloud from $49/month.
Pick it when
An existing Postgres, MongoDB or MySQL must stay the source of truth.

Zero

Instant, query-driven sync over Postgres
You run 3 things
  • zero-cache (replication manager + view syncers)
  • Postgres with logical replication
  • Your query and mutate API
No offline writesOffline writes not supported, by design
Cost
Open source (Apache 2.0). Hosted plans available.
Pick it when
Online collaborative apps that want instant UI over Postgres.

ElectricSQL

Streams Postgres data to clients
You run 3 things
  • Electric sync service
  • Postgres with logical replication
  • Your own write path
Offline writes: DIYReads sync; offline writes are yours to build
Cost
Open source (Apache 2.0). Electric Cloud is winding down after the Databricks acquisition.
Pick it when
Streaming Postgres data into clients, with writes handled your way.

Supabase

Hosted Postgres platform
Vendor runs it
  • Hosted Postgres platform (or self-host its stack)
Offline writes: DIYNot built in: add PowerSync or build your own
Cost
Free tier, then paid plans.
Pick it when
Your app is mostly online and built on Postgres.

Facts checked against each project's own docs and announcements, October 2026. Spotted something out of date? Tell us.

Developer Experience

A Few Lines. That's It.

No schemas to declare and no sync code to write. Read and write a local database; GoSync handles offline, real-time and conflicts.

app.js
1import { createClient } from '@harshalpatel2868/gosync-client';
2
3const db = await createClient({
4 url: 'wss://sync.example.com/sync',
5 getToken: () => auth.getIdToken(),
6});
7
8// Saved locally first: works offline, syncs when online
9await db.set('todos', id, { title: 'Ship it', done: false });
10
11// Live across tabs and devices; conflicts merge automatically
12db.watch('todos', (todos) => render(todos));
Features

Everything You Need. Nothing You Don't.

True Offline-First

Apps keep reading and writing without internet. Changes sync automatically when the connection returns.

Bandwidth Efficient

Each device downloads only what changed since its last sync and uploads only its own pending writes. Batched, compressed and safe to retry.

Conflict-Free Merging

Every field is merged independently on a hybrid logical clock. Concurrent edits to different fields both survive, and every device converges.

Secure by Default

JWT auth with your own secret or any JWKS provider (Auth0, Clerk, Supabase, Firebase). Every user's data is isolated on the server.

Real Local Database

Data lives in IndexedDB, not localStorage, so it isn't capped at 5 MB and survives reloads, restarts and crashes.

Single Binary

The server compiles to a single, static binary. No JVM, no Python runtime, no complex environment setup required.

Use Cases

Built for the Real World.

Don't just build apps. Build resilient systems that survive the chaos of the real world.

Field Operations

Logistics, Delivery, Inspection Apps
The Problem

Signal drops in basements and rural areas. The app spins. Data is lost.

The GoSync Fix
  • True Offline: The driver's app writes to local storage instantly. No spinners.
  • Queueing: GoSync holds the "Delivered" status in a persistent queue.
  • Auto-Reconcile: The second they hit 4G, only that pending change is uploaded.

Point of Sale

Retail, Kiosks, Inventory
The Problem

Internet goes down during the morning rush. The POS stops. Revenue stops.

The GoSync Fix
  • Business as Usual: The POS continues to accept orders and modify inventory locally.
  • Safe Edits: Each field merges independently: one till changes a price while another fixes a description, and both survive. Record each sale as its own entry rather than editing a shared stock count.
  • Batch Sync: When online, queued orders upload in batches. Each is applied exactly once, even if an upload is retried.

Collaborative SaaS

Kanban Boards, Task Trackers, CRMs
The Problem

Two users edit the same ticket. "Last write wins" overwrites everything.

The GoSync Fix
  • Shared Logic: Every client and the server apply the exact same deterministic merge rules.
  • Field-Level Updates: Only the fields you change are sent, and each one merges on its own.
Built in the open

Where GoSync has been, and where it's going.

Each next step closes a gap we listed above. No promised dates: the order follows what people building with GoSync need most.

ShippedLive today
  1. v1.0

    The prototype

    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.

  2. v2.0

    The production engine

    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.

You are here
NextWhat we're building toward
  1. Attachmentscloses a gap

    Photos and files

    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.

  2. Per-person datacloses a gap

    Sync only what's yours

    Rules that decide which records each person downloads.

    A health worker needs her own households, not the whole region's, on a small phone.

  3. React

    React hooks

    useCollection('todos') instead of wiring watch() to state yourself.

    Less glue code in the most common way GoSync is used.

ExploringIdeas we're weighing
  1. Tooling

    Sync inspector

    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.

  2. Collaborationcloses a gap

    Collaborative text fields

    Character-level merging for fields many people edit at once.

    Shared notes shouldn't lose a paragraph when two people type together.

  3. Mobilecloses a gap

    Native mobile clients

    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 →