Docker Compose
Docker Compose is the fastest way to run Alquimia Platform locally. It starts the runtime together with the supporting services: Kafka, PostgreSQL, Redis, Qdrant, MinIO, Vault, and an OCI registry.
When to use this guide
Section titled “When to use this guide”- Local development and prototyping.
- Demonstrating the platform to stakeholders.
- Testing agent configurations before promoting them to a shared environment.
What runs
Section titled “What runs”| Service | Purpose |
|---|---|
| Runtime | HTTP API and agent execution |
| Kafka | Event bus between master and worker roles |
| PostgreSQL | Persistent audit worklog and registry data |
| Redis | Session state, caches, and locks |
| Qdrant | Vector store for knowledge bases |
| MinIO | S3-compatible blob storage for attachments |
| Vault | Secret storage and dynamic credentials |
| OCI registry | Storage for agent packages and Boltzmann Brains |
Get started
Section titled “Get started”- Clone the
alquimia-runtimerepository. - Copy the example environment file and fill in the required secrets.
- Start the stack with Docker Compose.
- Verify the runtime health endpoint responds.
In Docker Compose the runtime typically runs in a single-process mode where master and worker share a container. This is convenient for local work but not recommended for production.
Environment setup
Section titled “Environment setup”At minimum you will need:
- An API token for authenticating requests.
- Database credentials for PostgreSQL.
- A Vault token for secret resolution.
- Object-store credentials for MinIO or S3.
- A signing key for CloudEvent integrity.
- An LLM provider API key if you want to run real inferences.
Store these values in the environment file; never commit secrets to source control.
Next steps
Section titled “Next steps”- Register your first agent
- Kubernetes & OpenShift — move to a production-grade deployment.
- Configuration — understand the runtime configuration model.