Modular distro

Editions: one platform,
shaped per client.

An edition is Clodia reduced to exactly what a business needs โ€” declared in one YAML blueprint, terraformed in one command, upgradable forever because it never forks the platform.

What a blueprint decides

Everything about the edition, nothing about the code.

๐Ÿงฉ Features

jobs, topics (off / single workspace / full), RAG (off / single collection / multi), channels, PWA, helpdesk. Off means no endpoint exists โ€” real attack-surface reduction.

๐Ÿค– Agents

Ship only the native agents you need (even just one), plus the agents from your domain packs โ€” installed and registered with their own PKI identity.

๐Ÿ“ฆ Packs

Your vertical as one unit: skills + rules + MCP connectors + agent seeds. Private packs install from a local path โ€” they never need to be published.

๐Ÿ”Œ Integrations

Whitelist which native connectors and MCP servers exist. Optionally allow manual MCP paste for power users.

๐Ÿง  Providers

Declare the allowed AI engines (at least one). EU data-residency via AWS Bedrock supported out of the box.

๐ŸŽจ Brand & language

Name, logo and accent color from the first login pixel โ€” plus a vocabulary map: your users can see "pratiche", the platform keeps speaking "topics" internally.

Three commands

From blueprint to running edition.

# 1. terraform: compose, datadir, profile, repos, boot
$ python3 clodia-build up blueprint.yaml

# 2. the client claims the first admin from the browser (WebCrypto)

# 3. finalize: install packs, register agents, create jobs
$ python3 clodia-build finalize blueprint.yaml

The builder lives in clodia-platform/builder with example blueprints. Blueprints never contain secrets โ€” the builder rejects them; credentials are set post-install through the vault.

Professional service

Want an edition delivered for your business?

We design the blueprint, build your domain pack and deliver a governed, backed-up instance โ€” commercial licensing available if AGPL doesn't fit your policies.

Talk to us