Triplit

Triplit — Full-stack database that syncs: local cache, server, relational queries, offline. Triplit is a syncing database with a client-side store, a typed relational query builder and a server you can run yourself. Data is modelled as triples, which is what makes fine-grained sync and partial replication practical. Schemas are defined in TypeScript and pushed. It is the smallest project on this list by team size, and correspondingly thin on surrounding services. Founded 2023. Open source.

We track it in 1 comparison — Convex alternatives — so every claim below is a cell in a table you can open and check rather than an impression. Across those rosters it sits against 10 other tools, and what follows is where it visibly separates from them.

Where it wins.

• Local-first sync — Yes, which only 3 of 11 tools here manage.

Each of those is ranked against the whole roster on its category page, not against a hand-picked subset, so a first place here means first of everything we list.

Where it gives ground.

• Auth — bring-your-own, 8th of 11. Supabase records built-in.
• MCP server — No. Convex records Yes.
• File storage — No. Convex records Yes.
• Full-text search — No. Convex records Yes.

None of these disqualify it on their own. They are the fields to check against your own requirements before you commit, because they are the ones where a competitor genuinely does better.

Provenance. 20 of 26 tracked fields carry a value for Triplit, and 7 of those cite a document you can open. Last verified 2026-07-20. Every figure keeps its own provenance — measured by us, claimed by the vendor, inferred, or community-reported — and we would rather print a dash than a guess.

Its nearest neighbour in our data is Appwrite. Triplit is ahead on Local-first sync (Yes against No) and Optimistic writes (Yes against No). Appwrite takes Cron & scheduling (Yes against No) and Auth (built-in against bring-your-own). That pattern repeats across the rest of the roster — see Triplit alternatives for the other rivals, each compared the same way.

Founded

2023

Licence

Open source

Fields we track

20 of 26

Last verified

2026-07-20

Technically the most elegant local-first model here — typed relational queries over a triple store, with real partial replication. Also the smallest team on the page, with no storage, no auth and no functions around it.

Local-first sync

●Yes1st of 11

Vendor-claimedverified 2026-07-20source

Auth

bring-your-own8th of 11

Inferred

MCP server

○No8th of 11

Inferred

File storage

○No8th of 11

Inferred

Full-text search

○No9th of 11

Inferred

Exit cost

48th of 11

Inferred

Vector search

○No8th of 11

Inferred

GitHub stars

4,0009th of 10

Inferred

Triplit is the right call in these situations, each one drawn from a field we actually record:

• Offline-first apps that need relational queries rather than document blobs.
• Teams happy to supply their own auth and file handling.
• Projects where sync correctness matters more than ecosystem size.
• Local-first sync is your binding constraint. Triplit records Yes, which only 3 of the 11 tools in the Convex alternatives roster do. We define that field as whether the client keeps a queryable local store that serves reads offline and reconciles with the server on reconnect.

Reach for something else when any of the following is a requirement rather than a nice-to-have:

• Auth. Triplit records bring-your-own, 8th of 11 in the Convex alternatives roster. Supabase records built-in on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• MCP server. Triplit records No on the Convex alternatives table. Convex records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• File storage. Triplit records No on the Convex alternatives table. Convex records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Full-text search. Triplit records No on the Convex alternatives table. Convex records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Exit cost. Triplit records 4, 8th of 11 in the Convex alternatives roster. Neon + Drizzle records 1 on the same field. If that is a hard requirement rather than a preference, start elsewhere.

We publish this block because a comparison that only lists what a tool is good at is marketing. Every figure above sits on the same page as its source, and the field definitions are on the category tables if you want to check how we measured them.

What we don't know. 6 of the 26 fields we track for Triplit are still blank: Hard limits, Cold start, Function timeout, Pricing model, Entry price and Egress metered. Those render as dashes rather than as zeroes or assumptions, because an empty cell and a bad cell are not the same thing and only one of them is honest. If you know any of these figures and can point at a document, tell us.