Skip to main content
Two local paths. Docker Compose runs the full stack as containers. nasiko up runs infrastructure in Docker and the Nasiko server as a local process. A remote cluster is just a URL — see Install and connect. From a clone of the nasiko repo:
Set at least:
  • ADMIN_PASSWORD — password for the admin account
  • OPENAI_API_KEY — a model provider key
  • AGENT_JWT_SECRET — uncomment and set (openssl rand -base64 48) if you will route coding agents
  • SECRETS_ENCRYPTION_KEY and JWT_SECRET — already filled with dev values in the example; replace them outside a laptop trial
The dashboard is http://localhost:8080. Sign in as admin with ADMIN_PASSWORD. First start compiles the server image and takes several minutes.
Compose sets TEMPO_URL, LOKI_URL, CODING_AGENT_OTLP_ENDPOINT, MCP_GATEWAY_PUBLIC_URL, and LLM_GATEWAY_BASE_URL for you. That is why coding-agent traces and model routing work on Compose without extra exports.

​
Services and ports

Network name: nasiko. Agent containers join it. For a Rust developer loop (infra in Docker, server via cargo): docker compose -f docker-compose.infra.yml up -d, then just run / just dev. Same ports; the server binds 8080 on the host.

​
nasiko up

Starts Compose infrastructure and runs the server from ~/.nasiko/bin/nasiko-cp (pulled as nasiko/cp:latest if missing). Config is ~/.nasiko/.env. The CLI registers the cluster as local. nasiko up does not set ADMIN_PASSWORD, JWT_SECRET, AGENT_JWT_SECRET, TEMPO_URL, LOKI_URL, or CODING_AGENT_OTLP_ENDPOINT. Export them in that shell, or use Compose. The server is a child of the terminal — closing it stops Nasiko. Details: Install and connect. If the image pull fails, build from source:

​
Next

Configuration

Environment variables.

Backup and restore

What to snapshot.