What is briq

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

It is not a code interpreter, a browser sandbox or a deployment platform.

What you get

• Any OCI image from a public registry: postgres:16, redis:7-alpine, ghcr.io/you/api:sha-abc.
• Recipes: ready-made stacks (postgres, redis, more in the cookbook) that return connection strings.
• One MCP server at https://api.briq.cloud/mcp. Your client signs in through the browser, or uses an API key where there is none. Works with Claude Code, Cursor, VS Code, Codex, Claude, Gemini CLI and OpenCode.
• Guardrails: spend caps, concurrency limits, allowed sizes and registries per agent. Every response carries costCentsSoFar and sleepsAt.
• EU hosting: Firecracker microVMs in Paris by default, or another region. One private network per team.
• Per-second billing: briqs go to sleep when nothing uses them and wake on the next use, and a sleeping briq is not billed. See Cost.

Get started

Paste one prompt into your agent and it sets briq up itself: see the Quickstart. To set up a client by hand, see Clients.

Next

• Concepts: briqs, stacks, recipes, agents, lifecycle.
• Cost: what a briq costs, and how the bill follows what runs.
• MCP tools: every tool, with an example.
• Cookbook: every recipe, with params, outputs and calls.
• Security: isolation, what briq stores, disclosure.

For agents

Every page here and in the cookbook is also Markdown: add .md to its URL (/docs/concepts/fork.md) or send Accept: text/markdown. /llms.txt indexes them; /llms-full.txt is the whole site in one file.