Cost
Per-second pricing, four sizes, and where the numbers show up.
briq meters compute per second while a briq is creating or running, from its own state
transitions. A briq that is not running is not metered at all. Prices are per size, in euro.
| Size | vCPU | RAM | Disk | Per hour |
|---|---|---|---|---|
nano | shared 1 | 512 MB | 2 GB | €0.006 |
small | shared 1 | 2 GB | 10 GB | €0.03 |
medium | shared 2 | 4 GB | 20 GB | €0.06 |
large | performance 2 | 8 GB | 40 GB | €0.12 |
A small Postgres that lives for 40 seconds costs €0.0003; the agent's test run in the
getting started transcript rounds to one cent. These figures come from
SIZES in @briq/core; the pricing table on the landing page is rendered from the same object.
You pay for the work, not the wait
The meter follows the agent, not the calendar. A briq stops on its own after idleMinutes
(default 60) with nothing touching it, and a stopped briq is not metered — so an agent that runs
a two-minute migration and moves on pays for the work, not for the eight hours its briq would
otherwise have sat there on its TTL.
Coming back is cheap and automatic: the next call that needs the briq starts it, the disk is
kept, and up to 2 GB of memory (nano and small) the machine resumes from a memory snapshot in
about a second. A briq serving an exposed URL is held open instead, since briq cannot see that
traffic. See lifecycle for the details.
What else costs money
- Stopped briqs are not metered today. Disk is kept for free while the briq exists; a storage line for long-lived stopped briqs and their volumes is planned, and will be announced before it is charged.
- Public endpoints and egress are included in v0. Per-key egress allowlists arrive in v1.
mediumandlargerequire the Pro plan and a card on file.
Free tier
Enough for a developer's evening. The exact allowance is set once the provider cost of small is
confirmed, and will be shown in the dashboard as credits.
Where you see it
- Every API response about a briq includes
costCentsSoFarandstopsAt. - Every MCP tool result ends with
cost so far €x.xx · stops at HH:MM. briq_quotaandGET /v1/quotareturn remaining daily spend for the key.- The dashboard shows spend today, credits left and a usage chart per team.
Caps
Spend caps are per key and per day (dailySpendCapCents). The check runs before create; during
the run, the reconciler stops the key's briqs once the cap is crossed. A team-level kill switch is
available to admins.
Billing is prepaid credits: manual top-ups in v0, Stripe in v1. Usage is reconciled monthly against the provider invoice.