briven· techbeta v1briven vs convex
reactive queries on plain postgres, not a proprietary engine.
convex pioneered the reactive-queries pattern briven adopts. the difference is the floor: convex stores your data in its own engine, briven stores it in plain postgres. that one decision changes everything downstream — exports, self-host, sql access, data residency.
feature
briven
convex
database
plain postgres 17 + pgvector. pg_dump is your escape hatch.
proprietary engine. exports to json but you can't pg_dump out.
query language
typed query functions with auto-generated client. raw sql when you want it.
typed convex functions; no raw sql.
reactive subscriptions
listen/notify-based reactive queries on real postgres tables.
first-class reactive queries (the pattern briven adopts).
self-host
agpl-3.0 core. self-host the full engine on your own postgres.
no self-host. cloud-only.
pricing
€0 free, €29 pro, €99 team. or free self-hosted forever.
free tier + usage-based; team plan $25/mo + bandwidth + functions metering.
export
one command (`briven export`) gives you the whole project as pg_dump + bundles.
json export of records. functions and schema do not export.
sql access
sql editor in studio. psql from the cli. postgres clients connect directly.
no sql access. queries go through convex functions only.
open source
agpl-3.0 engine, mit cli + sdks. development happens in public.
closed source. cli + client sdks are open.
auth
better-auth with magic link, oauth (google/github/discord), email+password built in.
convex auth via clerk, auth0, or custom provider integration.
file storage
minio (s3-compatible) bundled. point at your own s3/r2 in self-host.
convex file storage (own engine).
when convex wins
- ·you want a fully managed nosql-like store with zero postgres concepts to learn.
- ·you prefer convex's richer ecosystem of templates, hosted demos, and pre-built integrations.
- ·you need the convex action runtime's specific timing characteristics (we're close, but not bit-identical).
when briven wins
- ·you want your data in real postgres, exportable any day with pg_dump.
- ·you want to self-host. briven runs anywhere docker runs; convex doesn't self-host.
- ·you need sql, materialised views, triggers, extensions, or any other postgres feature.
- ·you care about data residency. briven runs in eu, single-region, on your hardware if you want.
- ·you want a flat fee, not usage-based pricing surprises.