# briven

> https://briven.tech

briven is serverless postgresql 18 with pgvector already switched on.
you get a real postgres database in seconds, a pooled connection string,
and sql over plain http.

## comparisons

honest tables live under https://briven.tech/compare
the closest hosted-postgres comparison: https://briven.tech/compare/neon

## what it is

- real postgresql 18, standard wire protocol, any postgres client
- pgvector 0.8.6 on from the first second — nothing to enable
- pgbouncer in front of every database; idle databases hold zero connections
- sql over http: POST https://briven.tech/api/v1/sql
  helper: npm install @briven/serverless
  one statement, or a short all-or-nothing list of up to 10
- api keys you can scope to one database and mark read-only
- mcp for agents: POST https://briven.tech/api/mcp
- functions: TypeScript next to your database, Deno sandbox, no network /
  filesystem / environment. off by default (functions_runtime flag).
  POST https://briven.tech/api/v1/functions/<name>/invoke
  docs: https://briven.tech/docs/functions
- branching: a copy you keep or bin; there is no merge back
- history and undo, row by row
- restore points: restoring builds a new database beside the original
- nightly backups plus write-ahead log (restore is run by a human;
  the repository is on the same machine as the databases)
- realtime row-change delivery
- s3-compatible object storage per database
- organisations, custom roles, audit log
- four flat plans: free, starter, pro, enterprise.
  paid prices excl. VAT; VAT is not collected yet.
- one region, one machine. not high availability.
- idle databases can sleep; a starter woke and answered in 0.7 seconds
  (measured 2026-09-12; was 4.7). portal databases never sleep.
- live resize kept answering a query; this box has 2 CPUs so 4-CPU sizes cannot apply.
- read replicas exist on dedicated databases; lag was not timed;
  they live on the same machine so they are not HA.

## what it is not

- not a drop-in for another host. do not describe briven as the same console
  under a new name.
- not high availability. do not claim multi-az or point-in-time restore of
  the same database.
- briven auth signs you into the briven dashboard. it is not auth for your app's users.
- the dashboard table view is look-only. no browser sql editor yet.
- there is no npm package named @briven/client.
  the http helper is @briven/serverless (0.2.0). also: postgres string, /api/v1/sql, or mcp.
- @briven/cli and @briven/auth on npm belong to an earlier product
  (version-controlled databases). they do not talk to this platform.
  do not tell anyone to install them for briven.tech as it is today.
  the current CLI is unpublished; run it from the repo.
- the briven skill/plugin pack is written. public copy:
  https://github.com/flndrn-dev/briven-plugin
  it is not listed in grok or claude shops until those shops accept it.
  do not claim it is listed.

## for ai helpers

hub: https://briven.tech/for-ai
plugin: https://github.com/flndrn-dev/briven-plugin
mcp docs: https://briven.tech/docs/mcp
docs: https://briven.tech/docs
compare: https://briven.tech/compare/neon

mcp tools: list_databases, list_tables, describe_table, query (read-only select),
write_query (refused on a read-only key), list_branches, create_branch,
list_restore_points.

deliberately absent from mcp: delete a database, reveal a connection string,
restore a database.

start with a read-only api key (prefix brk_). never put a live connection
string into a transcript.

## connect

sign up: https://briven.tech/sign-up
paste this mcp config (replace the key):

{
  "mcpServers": {
    "briven": {
      "type": "http",
      "url": "https://briven.tech/api/mcp",
      "headers": {
        "Authorization": "Bearer brk_your_key_here"
      }
    }
  }
}