How the family works.
Everything inside.
This wiki is the plain-English reference for the Zodyria systems. Each page explains what a system is, what it can do, and how to engage with it — no jargon, no gatekeeping.
You don't need to understand the stack. You need to understand the shape.
Four layers that make the fleet run.
Zodyria is not one tool — it is four interconnected systems that work together so you never have to touch them.
Command Center
The flagship dashboard where the whole family reports. Deploy agents, watch live fleet status, schedule the night shift, approve class-C actions. One window into twelve lanes of work.
↗ Read the Command Center guide System 02Discord Auto-Sync
A self-cleaning Discord control plane where every guardian has its own channel, reports land in threads, and stale messages auto-expire. The same dashboard mirrored into the app you already keep open.
↗ Read about Discord Sync System 03Guardian Agent Fleet
Twelve named agents, each with a craft, a voice, and a lane. Not anonymous bots — a family. Zodiax audits. Zythria reconnoitres. Zegix guards the keys. And a chief-of-staff routes every order.
↗ Meet the Guardian Fleet System 04Multi-Tenant Setup
Three doors into the same fleet: Admin, Team and Client. Each sees only what they should. Manage employees, contractors and external clients from one instance — with isolated views, billing and audit trails.
↗ Explore Multi-TenantHow to read this wiki.
You don't need to read everything. Pick the layer that matches your role.
I'm exploring
Start with the Command Center — it's the flagship. Then visit the Guardian Fleet to see who does what. That's enough for a first pass.
I'm setting up
Read the Discord Auto-Sync page to understand how orders and reports flow. Then Multi-Tenant if you plan to bring a team or involve clients.
I'm integrating
All four pages cover the API shapes, hook points and autonomy tiers. The Command Center page has the technical dimensions; Multi-Tenant covers the permission model.
Principles every system obeys.
Human-gated, always
Money, keys, deletes and public posts never self-approve. A system may propose; a human decides. Written in code, not policy.
A/B/C autonomy tiersEverything is audited
Who proposed, who approved, what happened, when. Every action logged, timestamped, never deleted. The ledger is the law.
Immutable audit trailYour data stays yours
Plain files on your own server instance. Export any time, keep everything. No lock-in, because owning the brain is the whole point.
Exportable. Always."Every system is built so the most dangerous action an agent can take is a proposal. The approval is always — always — a human's call."