briqbriq

What is briq

The services your agent's work needs, through one MCP server and one API key.

briq gives any AI agent the services its work needs. The agent says "run postgres:16", briq runs it on a real microVM in Paris, returns a URL and credentials, and tears it down when the agent is done.

It is not a code interpreter, not a browser sandbox and not a deployment platform. It is the missing primitive between "the agent knows about Postgres" and "the agent has one".

What you get

  • Any OCI image. postgres:16, redis:7-alpine, ghcr.io/you/api:sha-abc. Public registries in v0, private registries in v1.1.
  • Recipes. Typed, tested stacks (postgres, redis, more in the cookbook) that return ready-to-use connection strings.
  • One MCP server. Streamable HTTP at https://api.briq.cloud/mcp, Bearer API key. Works with Claude Code, Claude Desktop, Cursor, Codex, OpenCode and Gemini CLI.
  • Guardrails. Spend caps, concurrency limits, allowed sizes and registries per key. Every response carries costCentsSoFar and stopsAt.
  • EU hosting. Firecracker microVMs in cdg (Paris), one private network per team.
  • Per-second billing. Four sizes from €0.006 to €0.12 per hour. Briqs auto-stop when the agent goes quiet, and a stopped briq is not billed.

Two minutes to your first briq

Get a key

Sign in at briq.cloud/app, open API keys, create one. Keys look like bq_live_… and carry a policy: by default 5 concurrent briqs, €10 per day, sizes nano and small.

Add the MCP server

claude mcp add briq --transport http https://api.briq.cloud/mcp \
  --header "Authorization: Bearer $BRIQ_API_KEY"

Other clients are covered in Getting started.

Ask for a database

run the migrations against a fresh postgres

The agent calls briq_run({ recipe: "postgres" }), receives DATABASE_URL, runs your migrations, and calls briq_destroy when it is done. Each tool result ends with a line like cost so far €0.01 · stops at 18:42, so the model and you both know what is running and what it costs.

Where to go next

  • Concepts: briqs, stacks, recipes, keys, lifecycle, cost.
  • MCP tools: every tool with input, output and an example call.
  • Cookbook: every recipe with params, outputs and copy-paste calls.
  • Security: isolation model, what briq can see, disclosure.