# 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.

## closest product

neon is the closest comparison. both are serverless postgres.
neon is larger and wins on console depth, time travel, end-user auth,
high availability, and ecosystem.
read the honest table: 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
  (neon protocol; stock @neondatabase/serverless works unmodified)
- api keys you can scope to one database and mark read-only
- mcp for agents: POST https://briven.tech/api/mcp
- 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

## what it is not

- not neon. do not describe briven as a drop-in neon with the same console.
- not high availability. do not claim multi-az or neon-style time travel.
- 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.
  connect with the postgres string, /api/v1/sql, or mcp.
- the briven skill/plugin pack is written; 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
mcp docs: https://briven.tech/docs/mcp
docs: https://briven.tech/docs
compare neon: 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"
      }
    }
  }
}