Every agent governed. Every skill shared. Solo for you. Pro for your team.
Brewale is one governed connection for your team's agents — per-tool permissions, shared skills and conventions, and access you can revoke in a click. Solo is a flat monthly price for one developer. Pro is priced per seat and adds your team.
The trial clock only starts on your org's first MCP request. Setup time is free.
What a Pro seat buys
One seat covers everything Brewale does — for every agent that person runs. Solo includes the same for one developer, without teammates.
Access control
- Per-tool access control with read/write/delete classification.
- Org-wide defaults, per-user overrides, permission ceilings.
- Draft → publish lifecycle — nothing reaches an agent until you say so.
- Mark a member inactive and their MCP access pauses within ~5 seconds — and they're not billed as a seat.
One connection, every agent
- Skills and conventions served to Claude Code, Codex CLI, Cursor, VS Code, Zed — any MCP-compatible agent.
- Yours to keep — export every skill as markdown anytime, or sync your own GitHub repo.
- One-command setup via npx brewale.
Security that's shipped, not promised
- OAuth 2.1 with Dynamic Client Registration.
- Org-scoped API keys, plus service accounts for headless agents and CI.
- TOTP two-factor auth and Sign in with Google.
- Every token stored encrypted at rest.
One developer or a whole team
Every plan includes everything Brewale does. Pro adds your team.
Solo
For one developer
- Unlimited skills & conventions
- MCP server access
- GitHub sync for skills and conventions
- Custom MCP integrations
- Per-user access control
- Usage analytics
- 14-day free trial — no card required
Pro
For teams of any size
- Unlimited skills & conventions
- MCP server access for your whole team
- GitHub sync for skills and conventions
- Custom MCP integrations
- Per-user access control
- Usage analytics
- 14-day free trial — no card required
Solo has every Brewale feature for one developer. Inviting teammates and reviewers needs Pro — upgrade from Settings → Billing whenever you're ready, prorated.
On Pro, seats adjust automatically as people join or leave — no manual seat management. Inactive members aren't billed.
The clock starts when you do
Your 14-day free trial starts the first time your team uses the Brewale MCP server — not when you sign up. Take as long as you like to set up.
Subscribe before the trial ends and unused trial days carry over to checkout — subscribing early never costs you trial time.
The 14-day no-card trial is a commitment in our Terms of Service (§ 9) — not just marketing copy.
Billing that manages itself
No seat lists, no hidden line items, no lock-in mechanics.
On Pro, seats count themselves.
Every active member is a seat, and seats adjust automatically as people join or leave — you never manage a seat list. Set someone inactive and they keep web access, stop counting as a seat, and their MCP access pauses until they're reactivated.
Start on Solo, grow into Pro.
Solo covers one developer. When you want to add a teammate, upgrade to Pro from Settings → Billing, or right where you invite them. The change is prorated.
Invoices go where you want.
Billing managers receive every receipt, invoice, and payment alert — add them in Settings → Billing, including addresses like finance@ that never log in.
Leave cleanly.
Cancel anytime from your billing settings; you keep access until the end of the billing period. And if a payment ever fails, we warn — we don't cut off your team's access.
No surprises.
Only admins can subscribe, checkout only accepts the plans on this page, and double-subscribing is blocked while a subscription is live.
How Pro seats are counted
Your billing settings always show the live seat count, the per-seat price, the total, and your renewal date.
Questions people actually ask
What exactly will I pay?
It depends on the plan. Solo is €8 per month, flat, for one developer: every Brewale feature except the team ones (inviting teammates and reviewers). Pro is €25 per organization member per month, for teams; seats adjust automatically as people join or leave, with no manual seat management. Prices on this page are rendered live from our billing provider, so what you see is what you're charged. There's nothing else to buy on either plan.
Do I need a credit card to try Brewale?
No. Every organization gets a 14-day free trial of Pro, no credit card required. The trial runs before you ever enter payment details — you pick Solo or Pro when you subscribe, and you're only charged once you do.
When does the trial clock actually start?
On your organization's first MCP request — the first time your team actually uses the Brewale MCP server, not when you sign up. Setup time is untimed, so you can take as long as you need before day 1 begins.
Can I start on Solo and add teammates later?
Yes. When you're ready to bring someone in, upgrade to Pro from Settings → Billing, or right from the invite screen when you try to invite them. The change is prorated, and from then on your seats follow your member count.
What if I subscribe before my trial ends — do I lose the remaining days?
No. Unused in-app trial days carry over to checkout: the full 14 if your trial hasn't started yet, or the remaining days (rounded up) while it's running. Subscribing early never costs you trial time.
What happens to billing when someone joins or leaves the team?
On Pro, seats reconcile automatically as members join or leave — there's no seat list to manage. Your billing settings always show the current seat count, the per-seat price, the total, and your renewal date. Solo is for one developer, so adding someone means upgrading to Pro first.
What about members who aren't using it?
On Pro, an admin can mark a member inactive: they keep web access, they're not billed as a seat, and their MCP access is paused until reactivated. One honest note: inactivity affects seat billing, not the trial — the 14-day trial clock doesn't pause.
Can I cancel anytime?
Yes — manage or cancel your subscription anytime from your billing settings. You keep access until the end of the billing period.
What happens if a payment fails?
We warn, we don't cut off. Your team keeps MCP access while the payment issue is resolved, and your billing managers get a payment-issue alert. The only state that loses MCP access is an expired free trial.
Who receives the invoices?
Billing managers receive all billing emails — receipts, invoices, and payment-issue alerts — and manage the subscription and payment method in the billing portal. Admins choose them in Settings → Billing, including addresses like finance@ that never log in.
Is there annual billing?
Billing is monthly today.
Is the free-trial promise actually binding?
Yes. The 14-day no-card trial is a commitment in our Terms of Service (§ 9), not just marketing copy.
Which agents are covered?
Any MCP-compatible agent, on every plan — Claude Code, Codex CLI, Cursor, VS Code, Zed, and headless agents or CI via service accounts. Setup is one command: npx brewale.
Set up your organization
Start free — 14-day trial, no card. The clock only starts on your org's first MCP request.
Works with Claude Code, Codex CLI, Cursor, VS Code, Zed — any MCP-compatible agent.
One-command setup via npx brewale.