omadia
Back to home

install

Install omadia in minutes.

clone, configure, up, open.

Local install runs the full omadia stack on one machine via Docker Compose. One file, seven services, host-bound to 127.0.0.1. No external dependencies beyond an Anthropic API key.

BOOT LOG

$ docker compose up -d

  • ✔ Container omadia-postgres-1 Started
  • ✔ Container omadia-kroki-1 Started
  • ✔ Container omadia-minio-1 Started
  • ✔ Container omadia-ollama-1 Started
  • ✔ Container omadia-presidio-1 Started
  • ✔ Container omadia-middleware-1 Started
  • ✔ Container omadia-web-ui-1 Started
ready, http://localhost:3333/setup
pre-1.0, public preview

APIs and database schemas may break between minor versions until 1.0.0. The OSS distribution is preview-quality. Fine for evaluation, production rollouts stay a deliberate choice.

latest releasev0.56.0

prerequisites

What's needed before starting.

Three boxes to tick. Once the images are pulled, the stack boots in about a minute.

Docker + Compose

docker engine 24+, compose v2

Docker Desktop, Colima, OrbStack, or a plain Docker Engine on Linux. Anything that ships `docker compose` v2.

Anthropic API key

collected by the setup wizard

Sign up at console.anthropic.com and grab a key. The setup wizard collects it on first boot and encrypts it into the per-plugin vault. No file edits needed in the happy path.

~4 GB free RAM

postgres + middleware + sidecars

Comfortable headroom for postgres, the middleware, the admin UI, and the four sidecars (kroki, minio, ollama, presidio). The stack idles low after boot.

quickstart

Four steps between clone and the first agent.

Every command is copy-paste from the canonical README, top to bottom.

Clone

github, MIT-licensed

The OSS distribution lives in the byte5ai/omadia repository. Default branch is `main`. Tagged releases (v0.x.y) are recommended for stable deployments.

git clone https://github.com/byte5ai/omadia.git
cd omadia

Up

seven services, one network

Compose auto-discovers `docker-compose.yaml`. Brings up postgres, the middleware kernel, the admin UI, and all four sidecars on the omadia network. No `.env` file needed in the happy path.

docker compose up -d

Open + setup wizard

admin UI, first boot

The admin UI lands on `/setup` on first boot, unlocked until a user exists. The wizard creates the first administrator and stores the Anthropic API key encrypted into the per-plugin vault. Then `/setup` self-locks (returns 410 Gone) and `/login` takes over.

open http://localhost:3333

Optional customize

middleware/.env, power-user only

For headless boots, model overrides, or rotating secrets outside the vault, a copied and edited example file does the job. Most operators never need this. Defaults cover the happy path.

cp middleware/.env.example middleware/.env
$EDITOR middleware/.env   # override defaults (optional)

first boot

Setup wizard does the rest.

On first boot, /setup is unlocked until a user exists. It creates the first administrator and stores the Anthropic API key encrypted into the per-plugin vault. Once an administrator exists, /setup self-locks (returns 410 Gone) and /login takes over.

optional profiles

Modular sidecars for advanced setups.

The root compose ships every sidecar. To opt in piece by piece, the `infra/docker-compose.yml` file exposes three named profiles that mix freely.

--profile diagrams

Kroki + Mermaid companion + MinIO for the diagrams capability. Rendered Mermaid, Graphviz, PlantUML and Vega-Lite, signed PNG URLs.

docker compose -f infra/docker-compose.yml --profile diagrams up -d

--profile embeddings

Ollama running in-tenant for embeddings. No external API required. Boots a small model for vector retrieval against the knowledge graph.

docker compose -f infra/docker-compose.yml --profile embeddings up -d

--profile privacy-presidio

Microsoft Presidio NER sidecar for the privacy-proxy detector plugin: names, addresses, organisations, DE IDs.

docker compose -f infra/docker-compose.yml --profile privacy-presidio up -d

All three at once: `--profile diagrams --profile embeddings --profile privacy-presidio`. Profiles never break the base stack. Opt-in only.

plugin hub

Install plugins from the Hub.

Once omadia is up, point it at the Hub to discover and install plugin ZIPs (channels, integrations, agents), each pinned by a SHA-256 checksum. The Hub is the canonical omadia plugin registry. The in-app store mirrors what's published there.

Visit hub.omadia.ai

Pre-1.0: the Hub serves omadia-author plugins today, each pinned by SHA-256. Third-party publishing opens at 1.0.

next steps

From boot log to first agent.

Build an agent

The Builder writes the TypeScript, runs the typechecker, and ships a signed ZIP plugin. Live preview while it builds.

Open the Builder

Tune the voice

Kemia exposes twelve persona axes, four boundary categories, and a sycophancy level, bundled and exportable.

Open Kemia

Run a pilot

30-minute call. omadia runs live on a real workflow, and the result is a finished draft.

Get in touch