Serve read-heavy workloads from SQLite that Conjoin operates and backs up for you. On a paid plan, you can add replicas in other regions, so Conjoin serves each read from the region nearest to your user.
Conjoin streams every write to a SQLite instance into durable storage and serves reads in-process from the instance itself. Your code calls SQLite through the same Conjoin Database SDK that Conjoin provides for Postgres.
SQLite executes each query in-process, so a read completes in < 1ms with no network hop. Conjoin brings replicas in other regions up to date within ~30-150ms over the fast replication path.
On a paid plan, you can place SQLite replicas in any supported region. Conjoin then routes each read to the nearest replica.
Because SQLite is an embedded engine, Conjoin executes each query directly against the database file, with no connection pool, handshake, or TLS negotiation per request.
Conjoin streams every write to durable storage, so the data persists across restarts. Conjoin also uses that storage as a second replication path, over which every replica catches up within 1-10 seconds when the fast path is unavailable.
With auto-pause turned on, Conjoin stops the compute of an idle instance and resumes the instance when your application sends its next query. You set auto-pause separately for each instance.
When a region becomes unavailable, Conjoin routes the reads for that region to the nearest healthy replica in another region. You change no code for the failover.
Conjoin Live captures SQLite changes through WAL hooks and streams them to your frontend. Use useCollection for real-time subscriptions, define a Live View for a server-side query, or route changes to other systems through a Change Stream.
Conjoin takes a daily snapshot of every SQLite instance and keeps point-in-time recovery between snapshots. By default, Conjoin writes the backups to Conjoin Storage in a separate region, so you can restore the data after an outage in the region of the instance.
When a region becomes unavailable, Conjoin routes the reads for that region to the nearest healthy replica in another region. You change no code for the failover.
Conjoin Live captures SQLite changes through WAL hooks and streams them to your frontend. Use useCollection for real-time subscriptions, define a Live View for a server-side query, or route changes to other systems through a Change Stream.
Conjoin takes a daily snapshot of every SQLite instance and keeps point-in-time recovery between snapshots. By default, Conjoin writes the backups to Conjoin Storage in a separate region, so you can restore the data after an outage in the region of the instance.
In-process query execution
Real-time write propagation
No pooling or handshakes
Product catalogs, feature flags, and configuration stores usually receive far more reads than writes. SQLite executes each of those reads in-process, while on a paid plan Conjoin can also serve them from replicas in other regions.
Your service queries its catalog or its flags on an engine that executes each query in-process, with no connection pool to size for read traffic.
Serve content tables, lookup data, and reference data from SQLite, while your Postgres primary processes the writes and the transactions.
Conjoin answers the reads for that data from SQLite, so your Postgres primary receives only the writes and the transactions.
Turn on auto-pause for your development and staging instances. Conjoin stops the compute of an instance while it receives no queries and resumes the instance with the next query.
Conjoin pauses and resumes those instances for you, so you write no script to stop and start them on a schedule.
With SQLite replicas in the regions where your users are, Conjoin sends each read to the replica nearest the user. A read that otherwise has to cross a continent can then complete in single-digit milliseconds.
Conjoin picks the region for every read, so your application code contains no list of regions or routing rules.
Conjoin will open with a free Build tier, while the pricing page already lists the launch prices for Pro and Business. If you tell us what you're building, we'll talk you through early access.