I built a 9-agent AI council with post-quantum signing — fully self-hosted

conchaestradamiguelangel-droid — Tue, 09 Jun 2026 20:59:08 +0000

Most AI setups give you one model and a chat box. ENLIL gives you nine specialized agents that deliberate, vote, and sign their decisions with post-quantum cryptography — all running on your own server, with your own API keys.

No subscriptions. No cloud vendor. No data leaving your infrastructure.

What is ENLIL?

ENLIL is an open-source AI council: nine autonomous agents ("gods" from the Sumerian pantheon) that each hold a different analytical role. When you submit a document or question, all nine agents analyze it independently and reach a consensus. The result is cryptographically signed with ML-DSA-87 — a NIST post-quantum standard.

The nine gods and their roles:

Anu — supreme oversight, final validation
Enlil — coordination and strategy
Enki — technical analysis
Ninhursag — risk assessment
Nanna — pattern detection
Utu — compliance and ethics
Inanna — creative alternatives
Nergal — adversarial red-teaming
Ningishzida — memory and context

Each decree (the council's output) carries a 4627-byte ML-DSA-87 signature. Tamper with it and verification fails. Every decree is immutable once issued.

Why post-quantum signatures?

ML-DSA-87 (formerly CRYSTALS-Dilithium) is one of the three algorithms standardized by NIST in 2024 for post-quantum security. Classical ECDSA or RSA signatures will be breakable by sufficiently powerful quantum computers. If you're signing documents that need to remain trusted for 10+ years, you need to start now.

ENLIL uses liboqs-python (Open Quantum Safe bindings) to generate and verify these signatures natively in Python.

Architecture

Client sends request to FastAPI on port 8002. Nine agents run in parallel via OpenRouter using your own API key. A consensus engine collects all nine responses and signs the result with ML-DSA-87. The signed decree is stored in PostgreSQL and indexed in Qdrant for semantic memory. The client receives the final signed decree.

Self-hosting in 3 commands

git clone https://github.com/conchaestradamiguelangel-droid/enlil
cd enlil
cp .env.example .env
docker-compose up -d

The stack spins up: FastAPI on 8002, Qdrant on 6333. No other dependencies.

What's running in production

The live instance at enlil-council.com has issued 877 decretos since launch. The dashboard shows real-time god status, decree history, and signature verification for each output.

Typical p50 latency is under 8 seconds for a full 9-god deliberation round.

Why GPL v3?

Because if you run ENLIL as a service for others, the license requires you to share your modifications. The collective intelligence stays collective. Commercial use is fine — closed forks are not.

What ENLIL is not

Not a chatbot wrapper
Not a SaaS product
Not a framework you integrate into something else

It is a sovereign decision layer. You run it. You own the decrees. You verify the signatures.

Roadmap

Bridge layer connecting ENLIL to AEGIS (9-layer cyber defense system)
Multi-tenant mode (one instance, multiple isolated councils)
Webhook output for decree events
Web UI for decree verification without API access

Try it

Repo: https://github.com/conchaestradamiguelangel-droid/enlil
Live dashboard: https://enlil-council.com/dashboard
License: GPL v3

Star it if you're building in the self-hosted AI space — issues and PRs welcome.

DEV Community: conchaestradamiguelangel-droid