Self-hosting

Run CodexaX entirely on your infrastructure.

What you get

Both the editor and the backend are open source. You can:

  • Build CodexaX from source for mac / win / linux.
  • Run the API + web console on your own servers.
  • Point your own copy of the editor at your backend (one config flip).

Quick start

git clone https://github.com/codexax/codexax
cd codexax
cp .env.example .env       # fill in ANTHROPIC_API_KEY at minimum
pnpm install
pnpm dev                   # api on :8787, web on :3000

Production deploy

  • API. Single Node process, SQLite by default. Swap DB_PATH + the db.ts driver for Postgres for HA.
  • Web. pnpm --filter @codexax/web build → standard Next.js output.
  • Releases. Use infra/ci/release.yml as a starting point — builds, signs, notarizes the editor, then publishes metadata to your update server.

Pointing the editor at your backend

In VS Code settings (or your fork's product.json):

{
  "codexax.apiBase": "https://api.your-domain.com",
  "codexax.webBase": "https://your-domain.com",
  "updateUrl":       "https://api.your-domain.com"
}

Hardening checklist

  • Generate a real JWT_SECRET (32+ random bytes).
  • Put the API behind TLS (Caddy / Cloudflare).
  • Configure SMSBAO_* for real SMS.
  • Set up Stripe webhooks → POST /v1/billing/webhook with the live secret.
  • Move the SQLite file to durable storage (or migrate to Postgres).

Stuck? Back to docs or email [email protected].