Skip to content

Docs · Quickstart

One command to a usable login

The standing contract of the repository: docker compose up on a fresh clone reaches a usable login with zero configuration. Everything below is detail around that one command.

Before you start

  • Docker Engine with the compose plugin. Docker Desktop is fine. The stack builds locally on first run; any recent machine with about 8 GB of free RAM is comfortable.
  • Optional: a Mistral API key for model features. Without it the stack still runs: login, capture, dashboard, and queue all work, and model calls fail with a typed error instead of pretending.
  • Node 22 and npm only if you develop. Not needed to run the stack.
  1. 1

    Clone and start

    First run builds the images and initializes identity, which takes a minute or two.

    git clone https://github.com/Cogeto/cogeto.git
cd cogeto
docker compose up
  2. 2

    Open it and sign in

    The dev edge serves a self signed certificate from a local certificate authority, so your browser will warn once. Accept it.

    Open https://localhost and sign in as the dev bootstrap admin: admin@cogeto.localhost with password DevPassword1! You are looking at your own instance.

  3. 3

    Add a model key

    Copy .env.example to .env, set your key, and bring the stack up again. Dev defaults are safe for localhost only; a preflight container refuses known dev secrets on any non localhost domain.

    cp .env.example .env
docker compose up -d

The Ana sandbox

A fictional consultant with weeks of accrued memory, seeded through the real public API: contradictions to resolve, lapsed facts, a signed deletion receipt. The access password is printed by the seed job. Never run the demo profile on an instance holding real data.

COGETO_DEMO_MODE=1 docker compose --profile demo up --build
docker compose logs demo-seed

If something looks wrong

Port 80 or 443 is already taken

Another web server is running. Stop it, or change the published ports in a compose override.

Chat or extraction returns a model gateway error

No model API key is set. That is the designed behavior without a key, not a crash.

A one shot init container shows exited (0)

Normal. Preflight, database init, migrations, storage init, and identity init run once per up and exit.

Starting over

docker compose down -v deletes all data, including the instance signing key and receipts. Fine on a dev box; never the answer on a real instance.

docker compose down -v deletes everything, including the instance signing key and the receipt chain. On a real instance the answer is always the rehearsed backup restore, never a wipe.

Where to go from here

When the evaluation convinces you, production is a different, safer path: signed images and one operator script.

Self hosted, in productionRunning locally, the full reference

Rather see it on your documents first?

The pilot reads a real document set of yours and ends with the signed findings report.

Start a pilotBack to all paths