OPENBAKER
HOSTED

We run it for you

Managed by us at app.openbaker.org. No infra to run. Early access is invite-only — your invite includes a token. Run baker instance new and paste it in.

  • No Docker, no server
  • Automatic updates
  • Your API keys stay encrypted on the instance
  • Models: OpenAI, Anthropic, others
Request access →
SELF-HOSTED

Your own server

baker sets up the whole instance for you — pulls the image, generates config, starts the container, creates your admin account. Requires Docker.

  • Complete data ownership
  • No usage limits
  • Air-gapped friendly
  • Any model via any API-compatible provider
View source ↗

Setup is inside the CLI

You don't clone a repo. You don't write config files. You run baker and it walks you through everything.

01

Install baker and run it.

$ npm install -g @openbaker/cli
$ baker
02

Choose your instance type. Hosted uses your invite token. Self-hosted uses Docker — on this machine or a remote server.

  ? What do you want to do?
    › New instance
      Connect

    ? What type of instance?
    › Hosted  (app.openbaker.org)
      Self-hosted (Docker)
03

For self-hosted: baker checks Docker, pulls the image, generates config, starts the instance.

 Docker found
 Image pulled
 Config generated
 Instance started on :3000
04

Create your admin account. baker connects automatically. Done.

  ? Your name:   Mike
  ? Email:       me@example.com
  ? Password:    ············
 Connected to localhost:3000
Already have an instance running? Run baker connect to skip setup and connect directly with a URL and token.

Compare

HostedSelf-hosted
Setup timeNone~5 min
InfrastructureManagedYour server
UpdatesAutomaticManual (git pull + restart)
Your API keysLocal onlyLocal only
Data ownershipOpenBaker serversFully yours
CostTBD (free in early access)Free
LicenseAGPL-3.0AGPL-3.0

Security

Early access means a small, known user base. We treat that as a security property, not just a product state.

Invite-only access
The hosted instance is not open registration. Accounts are granted by invite token only. Tokens are single-use and tied to an email address. If you didn't get an invite from OpenBaker directly, you don't have access.
No Discord
OpenBaker does not have a Discord server. We don't run support, announcements, or community there. If someone is pretending to be OpenBaker on Discord, it's not us. Contact and support go through the site only.
API keys stay on your instance
Your provider API keys (OpenAI, Anthropic, etc.) are stored encrypted on the instance — hosted or self-hosted. They are never transmitted to the CLI in plaintext and never leave the server. The CLI authenticates with a session token, not your keys.
Threat model
OpenBaker is a tool that runs AI against your workspaces and has access to your shell context. We take that seriously. The hosted instance runs on isolated infrastructure with no multi-tenant data leakage by design. Self-hosters control their own attack surface entirely.
We will not ask for your token
OpenBaker support will never ask for your account token, API key, or password. If anyone claiming to be OpenBaker staff requests credentials, do not provide them and contact us through the site.
Verified accounts only
Email verification is required before any account becomes active. Unverified accounts cannot authenticate, submit ideas, vote, or access the hosted instance. This is not optional and will not be removed.
Anonymous analytics. Manage