SOIT Docs
Getting Started

Quickstart

Start a local SOIT stack with Docker and open the web workspace.

The quickest way to try SOIT is the local Docker stack. One command starts the web application, API, database, queue, object storage, vector database, Vault, migrations, bootstrap job, and knowledge ingestion worker.

Prerequisites

  • Docker with Docker Compose.
  • A clone of the SOIT repository.
  • Roughly 8 GB of free memory for the full service set (PostgreSQL, Redis, Milvus, MinIO, Vault, API, web).

Start the stack

Run from the SOIT repository root:

cp .env.example .env
docker compose -f docker/docker-compose.yml up -d postgres redis minio etcd milvus vault migrate bootstrap api web knowledge-ingest-worker

Then open:

  • Web UI: http://localhost:5000
  • API base and API docs: http://localhost:9200

Sign in with the bootstrap admin account configured in .env (BOOTSTRAP_ADMIN_EMAIL and BOOTSTRAP_ADMIN_PASSWORD).

What starts

ServiceRole
PostgreSQLBusiness data, runtime ledger state, and outbox events
RedisQueues and runtime coordination
Milvus (with etcd)Vector search for knowledge retrieval
MinIODocument storage and runtime artifacts
VaultWorkspace-scoped secret references
migrateApplies Alembic database migrations, then exits
bootstrapCreates the admin account and initial workspace, then exits
apiFastAPI backend on port 9200
webWeb workspace on port 5000
knowledge-ingest-workerAsynchronous document ingestion and indexing

Check that everything is healthy

curl http://localhost:9200/health/ready
curl http://localhost:5000/
docker compose -f docker/docker-compose.yml ps knowledge-ingest-worker

Expected results: the API reports ready, the web app responds, and knowledge-ingest-worker stays in the running state. If the API is not ready yet, the migrate and bootstrap jobs may still be completing — the full stack should come up within a few minutes on a warm image cache.

Take a first tour

After seeding the demo workspace (next page), verify the main product surfaces:

  1. ModelHub shows the seeded test provider and models.
  2. Knowledge contains the seeded refund policy document.
  3. Agents can answer a refund-policy question with a citation.
  4. Workflows can execute the support-ticket triage path.
  5. Runs and Observe show response events, run steps, tool calls, child workflow runs, costs, citations, and audit records.

Next steps

On this page