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 a shared repository in your first session.

  1. Create a workspace

    Sign up and name your workspace — it's the tenancy and billing boundary.

  2. Start a project

    Use the guided wizard: pick a template (or start empty), and environments are set up for you.

  3. Invite your cofounder

    Add a teammate with the role that fits — Reviewer works well for nontechnical cofounders.

  4. Add your secrets

    Put API keys in the Environment Vault instead of a .env file. Developers pull them with the CLI.

  5. Make a change and request a review

    Edit in the web UI or push from your editor; open a review request and merge together.

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