Keelson

Docs

Documentation

Keelson's docs currently live in the open-source repository, the same place the code does. A hosted documentation site is coming; until then, these links go straight to the source.

Reference

Getting started

Set up a development environment and make your first contribution.

Opens on GitHub

Self-hosting

Run the complete platform yourself with Docker Compose.

Opens on GitHub

Deployment

Deploy targets and the Vercel integration.

Opens on GitHub

Security

The security model, controls, and responsible disclosure.

Opens on GitHub

Architecture

System design, deployables, and the invariants we hold.

Opens on GitHub

Quickstart

From zero to your first approved agent run in one session.

  1. Create a workspace and a project

    Sign up, name your workspace (the tenancy and billing boundary), and start a project from a template or an imported Git URL.

  2. Configure an AI provider

    Use platform credits, or bring your own key: Anthropic or any OpenAI-compatible endpoint, on every plan.

  3. Submit a request

    Describe the change you want. The agent writes a plan; nothing touches the repository yet.

  4. Approve the plan

    Read the plan, narrow the path scope if you want, then approve. The run executes once, inside enforced limits, on its own branch.

  5. Review the verdict and merge

    An independent review grades the result. Read it, review the change, and merge or close. The decision is always yours.

The CLI

The CLI is Apache-2.0 and lives in the same repository, under apps/cli. It signs in once, then reads the environments you are allowed to read.

keelson login
keelson vault pull                 # writes .env.local, chmod 600
keelson vault run npm run dev      # secrets injected, nothing on disk
keelson scan                       # pre-push credential scan

Values pulled to disk land in .env.local with owner-only permissions, and the command warns you if that file is not covered by your .gitignore.

How the Environment Vault works