briven· techbeta v1migrate / postgres
add reactivity, typed functions, and hosting to the postgres you already run.
if you're running raw postgres + a hand-rolled service layer, briven is the smallest possible upgrade: same database, same SQL, but with a typed function layer, reactive subscriptions, and zero-config deploys on top.
what you're afraid of
will my schema change?
no. we pg_dump your tables exactly as they are and pg_restore them into briven's data plane. column types, constraints, indexes — all preserved.
do i have to give up writing raw SQL?
no — briven's ctx.db.execute("...") is the SQL escape hatch. the typed builder is for the common case; raw SQL is one method call away.
what about my pg_cron / pg_partman / pg_stat_statements extensions?
briven's postgres is the same postgres. pgvector + pg_cron are enabled by default; we can enable additional extensions on your project tier.
the conceptual mapping
your mental model survives the move. left column: what you call it in raw postgres. right column: where it lives in briven.
| raw postgres | briven |
|---|---|
| your schema.sql | briven schema DSL via introspection (one-shot script) |
| your service layer (express / fastify / etc.) | briven functions (one file per endpoint) |
| pgbouncer + connection pooling | briven's built-in pooling |
| your existing backup pipeline | briven's automated backups + your existing pg_dump pipeline still works |
what the migration actually costs
ranked honestly: what comes for free, what we automate, what stays manual.
- free
data — pg_dump | pg_restore. zero transformation.
- auto
schema port — introspection script reads your information_schema and emits briven DSL.
- manual
service-layer port — your http handlers become briven functions. usually ~1 day for a medium app.
questions you actually have
- why not just keep my postgres setup?
- you can. briven adds reactivity, typed deploys, and hosting; if you're happy with what you have, the only thing you're missing is reactive useQuery.
- is briven's postgres different in any way?
- postgres 17 with pgvector + pg_cron enabled. otherwise identical. you can `pg_dump` from briven to anywhere any day.
- what about replication / read replicas?
- on the team tier. brivens managed read replicas come online without a config change.
ready to start? no signup needed
leave us your email and we'll reach out within one business day. your raw postgres stays untouched the entire time.
already got a briven account?
jump straight into the in-product wizard for a more detailed intake form — you can save progress and track status from your dashboard.