Comparison
How TopGun compares to other solutions in the ecosystem.
| Feature | TopGun | ElectricSQL | Firebase | RxDB | Replicache/Zero | Durable Objects |
|---|---|---|---|---|---|---|
| Primary Model | Local-First IMDG | Postgres Sync | Cloud Doc DB | Local-First DB | Client Auth Sync | Edge Stateful |
| Offline Support | First-Class | Good | Good | Excellent | Good | Limited |
| Latency | ~0ms (In-Memory) | ~5-10ms (SQLite) | Network Dependent | ~5-10ms (IndexedDB) | ~5-10ms | Edge-fast |
| Backend Control | Self-Hosted Cluster | Sync Service | Proprietary | CouchDB / Custom | SaaS | Cloudflare Only |
| Consistency | HLC + CRDT | Server Authority | LWW (Server) | Revision Trees | Server Authority | Single-Object |
| Distributed Locks | Fencing Tokens | Not Supported | Not Supported | Not Supported | Not Supported | Per-Object |
| License | Open Source | Open Source | Proprietary | Open Source | Proprietary | Proprietary |
Why TopGun?
- vs ElectricSQL:
TopGun operates entirely in-memory for zero-latency reads/writes, whereas ElectricSQL relies on SQLite access (5-10ms).
- vs Firebase:
TopGun gives you ownership of your data. Run it on your own cloud, use your own Postgres DB, and never get locked into a proprietary platform.
- vs RxDB:
TopGun includes a powerful, sharded server cluster for handling massive datasets and complex server-side logic, rather than just replication.
- vs Replicache/Zero:
TopGun uses CRDTs for automatic conflict resolution without server round-trips. Replicache/Zero requires server-authoritative mutations (simpler security model but higher latency). TopGun is self-hosted and open source; Replicache/Zero is proprietary SaaS.
- vs Durable Objects:
TopGun runs on your own infrastructure with full control over data and deployment. Durable Objects are locked to the Cloudflare platform with per-object pricing. TopGun provides a complete data grid (clustering, partitioning, search), not just edge state.