01
Start local
Run Bitter where the repo already lives. Files, diffs, commands, and operator judgment stay close to the work.
Bitter Factory
The hosted half of the substrate.
Run Bitter locally. Connect Factory when the agent-run business needs hosted runners, scoped credentials, durable evidence, deploys, backups, email, credits, or a dashboard — kept under one operator-owned account.
Join the Indie list
Indie planned at $49/mo. Dedicated Box and Enterprise tiers follow.
Hosted runners
Scoped credentials
Durable evidence
Deploy lanes
Backups
Shared credits
Email / webhooks
Web dashboard
Workflow
Local-first. Operator-owned. Hosted when it has to be.
02
Sign in once
Factory connects the hosted half of the substrate: runners, credential grants, durable evidence, deploy lanes, backups, email, and credits.
03
Compound the substrate
Heavier work moves to hosted runners. Receipts and credentials accumulate in one account. The substrate keeps compounding while the operator stays in the loop.
Hosted layer
One operator-owned account for the substrate behind the CLI.
Runners, credentials, evidence, deploys, backups, and dashboard state should not be rebuilt for every project — and they should not live on whatever vendor was special last quarter. Factory keeps the substrate operator-owned and reachable from the CLI through one account.
Wire it yourself
Multiple vendors, keys, queues, scripts, dashboards, and recovery paths before any of the agent work can run cleanly.
- Mailbox provider
- Secrets manager
- CI and hosting account
- Worker queue for hosted agents
- Logging and run history
- Backup and recovery scripts
- Usage dashboard
Connect Factory
Factory keeps those services behind the same operator-owned account the CLI already uses.
- Single sign-in
- Shared service credits
- Credential grants
- Hosted runners
- Durable evidence and receipts
- Deploy and backup lanes
- Dashboard
Constellation
The substrate, broken out by service.
Runtime, evidence, credentials, verification, browser checks, identity, hosting, checkout, support, email, uptime, and analytics — twelve services already running on the operator's side, evidence of what one unusually autonomous business looks like in practice.
Runtime and workcells
BitterGrid
Hosted execution, release records, deployment records, workcells, and recovery paths for agent-built software.
Evidence and memory
BitterLog
Append-only run receipts, raw traces, artifacts, and evidence history for future runs.
Scoped credentials
BitterPass
Operator-approved credential grants for agents touching APIs, cloud consoles, billing systems, and internal tools.
Verification
BitterQA
Behavior checks, artifacts, verdicts, failure reports, and reruns.
Browser evidence
Bitter Browser
Screenshots, DOM snapshots, traces, and verification commands from a controlled browser environment.
Identity and account
BitterHub
Identity, billing, app registry, entitlements, credits, and shared access across Bitter services.
Static hosting
Radicchio
Fast custom-domain publication for small sites, probes, tools, and static properties.
Payment handoff
BitterCheckout
Stripe Checkout routing for small products that need to charge without building a billing team.
Support agent
BitterDesk
Embeddable support, safe intake, evidence-bound conversations, durable transcripts, and human handoff.
Email relay
BitterPost
Signed form submissions, reply-ready email delivery, and auditable handoff logs.
Uptime monitoring
BitterPing
HTTP, HTTPS, health-check, and heartbeat monitoring with down and recovery alerts.
Analytics
BitterAnalytics
Sessions, search, revenue, and uptime data collected across properties and served through one API.
Dashboard
Substrate state, in one operator-owned view.
Hosted runs, credential grants, deploy state, backups, receipts, usage, and next actions across every property — readable from the same account the CLI uses, on the operator's side of the substrate.
Plans
Start shared. Isolate when needed.
Indie connects one operator to the shared hosted substrate. Box moves the substrate onto a managed server. Enterprise adds governance, audit, private deployment, and spend controls.
coming soon
$49
/mo
Indie
For one operator running an unusually autonomous software business with Bitter CLI.
- One Factory account
- Hosted agents and run history
- Credentials, evidence, backups, deploy lanes, stats, and dashboard
- Shared credits across hosted services
dedicated server
Custom
managed server
Box
Dedicated infrastructure for heavier or more isolated agent work.
- Managed Hetzner server
- Isolated runners and deploy lane
- Box-scoped logs, backups, and services
- Factory account and dashboard included
governed scale
Custom
contact
Enterprise
For organizations increasing agent and inference volume under policy, audit, and spend controls.
- SSO, policy, audit, and governance
- Private or dedicated deployment options
- Spend, credit, and model-use controls
- Enterprise support and integration planning
Talk to bitter
Connect the hosted half of the substrate.
Building an unusually autonomous software business and want to think the substrate through together? The Indie list and the Box and Enterprise conversations all run through one inbox.