Pricing
Three plans.
No telemetry.
Self-host for free under BSL 1.1, take Solo to lift the agent cap, or Solo Lead to add a Master that drives a swarm of workers. Source-available, no per-seat fee, no telemetry.
Self-hosted
$0
Forever. Self-host the relay.
- ✓1 developer seat — no licence keys, no activation
- ✓3 agents per developer (Claude Code, Aider, Gemini CLI, Cursor, Cline, anything else)
- ✓All features: kernel sandbox, mobile HITL, supply-chain protection, token monitor, loop detector, git auto-checkpoint, command palette, skill engine
- ✓E2E encryption (AES-256-GCM) — keys on your CLI and phone, never on the relay
- ✓Audit logs (JSONL, SIEM-friendly), Telegram + PWA notifications
- ✓No telemetry — tamer never phones home
- ✕Master
Solo
$5/mo
Unlimited agents on your laptop.
- ✓1 developer seat — no licence keys, no activation
- ✓Unlimited agents per developer (Claude Code, Aider, Gemini CLI, Cursor, Cline, anything else)
- ✓All features (same as Self-hosted)
- ✓E2E encryption, audit logs, Telegram + PWA notifications
- ✓No telemetry
- ✕Master
Solo Lead
$15/mo
Lead a worker swarm with one Master.
- ✓1 developer seat — no licence keys, no activation
- ✓Unlimited agents per developer
- ✓All features (same as Self-hosted)
- ✓E2E encryption, audit logs, Telegram + PWA notifications
- ✓No telemetry
- ✓One Master — Tamer's supervisor agent that drives one or more workers (see Features)
What is a Master? A Master is Tamer's supervisor agent that drives one or more workers — generating Work Items, auditing results, and routing decisions to your phone. See Features → Master Agent →
Self-hosted: you pay only for the infrastructure you choose to host the relay on (a small Docker container fits in < $5/month on most providers, or $0 on a spare VM). Source on GitHub; each release converts to Apache 2.0 four years after publication (BSL 1.1).
Looking for a hosted version?
A managed-relay offering for teams that don't want to run their own infrastructure is on the radar but not yet released. If you'd like to be informed when it ships — or if you have specific requirements (single-tenant, EU-only data residency, SSO) — open a GitHub issue and tell us what you need.
Tell us what you need →No commitment. No mailing list. We just want to hear from teams blocked by the self-host requirement.
License questions
- Can I use tamer commercially in my company?
- Yes. BSL 1.1 permits internal commercial use from day one — your developers can use tamer to ship paid software, and your company can deploy the relay internally for its own teams without limit. The only thing BSL restricts during the four-year window is reselling tamer itself as a managed competing service. After four years each release converts to Apache 2.0, lifting that restriction too.
- What exactly does BSL 1.1 restrict?
- Only one thing: offering tamer (or a substantially similar product derived from tamer's code) as a paid hosted service to third parties. Building anything else with or on top of tamer — even commercial products — is fine. The full text is short and human-readable; see the LICENSE file.
- When does each release become Apache 2.0?
- Four years after that release's date. Newer releases reset their own clock, but earlier ones remain on schedule. Once a release converts, it is freely usable under Apache 2.0 forever — including for resale.
- Do I need a contributor licence agreement (CLA) to contribute?
- No CLA is required for community contributions today. Pull requests are welcomed under the project's existing licence. If a CLA becomes necessary later (e.g., to dual-licence parts of the code), it will be announced before any change.
- Can I fork tamer?
- Yes — BSL is source-available. Fork, modify, and run for any non-resale purpose. If you publish a fork, BSL terms travel with the code; once each release converts to Apache 2.0 the fork can do whatever Apache 2.0 permits.
Note — the answers above are written to be readable, not legally exhaustive. The LICENSE file is the authoritative source. If you need a written confirmation for procurement / legal review, open a GitHub issue.