Platform
Microcelium, defined
A developer platform with agents, messaging, observability and integration baked in. Build your product on top; we run the layer underneath — everything beneath the waterline so your team can stay above it.
Organisation as Code
Define your business in code
Your organisation structure, roles, access controls and integrations — defined as declarative YAML. When it changes, Microcelium automatically updates every connected system.
Git-backed, version-controlled and human-readable. Consumable by any tech — no vendor lock-in, no proprietary console. It's just YAML in a repo.
organisation:
departments:
- name: "Engineering"
manager: "john.doe@company.com"
staff:
- name: "Jane Smith"
role: "Senior Developer"
email: "jane.smith@company.com"
start_date: "2024-01-15"
access_levels:
- github
- aws
- office365
Office 365
User provisioning, group memberships, access permissions
Active Directory
Authentication, security groups, organisational units
GitHub / GitLab
Repository access, team memberships, permissions
Slack / Teams
Channel access, team assignments, notifications
AWS / Azure
IAM roles, resource access, billing allocation
HR Systems
Onboarding workflows, training, compliance tracking
Facilities
Badge access, desk assignments, equipment provisioning
Monitoring
Alert routing, escalation policies, on-call schedules
New hire onboarding goes from hours to minutes. Role changes propagate everywhere instantly. Leaver access revoked across all systems immediately. Full audit trail for every change.
Agentic Automation
Autonomous agents, human oversight
Intelligent software agents handle business processes, make decisions and coordinate activities. Humans stay in the loop for critical decisions.
The five cards below are the roles agents play in the fabric. The named shipping roster is smaller and is listed on /components: Platform, Onboarding and Welcome Agents are available now in general availability; Hive-Mind Agent is in beta.
SysOps, BCDR, Policy, SecOps, Support, Triage and Reporting Agents are on the roadmap. Each named agent fills one or more of the roles shown here.
Process Agents
Business workflow orchestration, routing and escalation. Route invoices, manage approvals, coordinate multi-step operations.
Integration Agents
Tool-calling across the provider network — Stripe, Xero, Moodle, calendars, messaging. HMAC-signed, MDXF-stamped, audited.
Monitoring Agents
Platform playbook execution. Auto-heal common failures (certificate renewals, queue backpressure, disk thresholds). Escalate to on-call when a runbook needs human judgement.
Roadmap: SysOps Agent
Compliance Agents
ISO 27001 control-map checks, evidence generation, continuity and disaster-recovery drills. Real-time policy gate: evaluate every event against OaC, auto-remediate or escalate.
Roadmap: BCDR Agent (continuity/evidence) + Policy Agent (real-time gate)
Security Agents
Access anomaly detection, threat triage from audit logs, incident coordination. Feeds incidents into the SysOps escalation chain.
Roadmap: SecOps Agent
These are the roles agents play in the fabric. Platform Agent, Onboarding Agent, and Welcome Agent ship today; SysOps, BCDR, and SecOps are in development. See the components catalogue for status and scope.
What this actually looks like
A concrete scenario — invoice routing, from arrival to payment, without anyone staring at a dashboard.
07:32 — Supplier invoice lands by email. The Email provider drops it onto the message bus as an MDXF envelope with a UUID.
07:32 — Ingestion Engine parses the PDF, extracts amount (£4,200), vendor, project code and tax.
07:32 — A Process Agent reads the Organisation as Code policy for this amount band (£1,000–£10,000 → project manager, 4-hour timeout). It looks up the project owner from OaC: Jane.
07:32 — The agent posts to Jane's Slack with extracted fields and a PDF preview. It waits.
07:32 — Nothing else is on fire. Humans get on with actual work.
11:14 — Jane approves in Slack. The agent writes the approval to the ledger, calls the bank's API through the REST provider, and closes the workflow. Full audit trail lands in Loki with the original UUID.
Timeout path — If Jane hadn't responded by 11:32, the agent would have re-posted with @channel, then escalated to the finance director at 15:32 per the same OaC policy. Every step stamped.
On a typical deployment: hundreds of invoices per month flow through this workflow, with a handful flagged as exceptions for Finance review. No one watches a dashboard for the routine case; agents only escalate when policy says they should.
Human-Agent Collaboration
Agents provide recommendations and context for human decisions. Configurable escalation thresholds. Full audit trail. Humans can override any agent decision.
What ships
A full component surface, already built
Microcelium ships as composable layers: Prism API (Laravel-modular backend) carries your business logic; Glass UI (TypeScript/React + React Native) renders it when you want a full web + mobile app, or run Prism API headless behind your own frontend. Agents, AI providers, and integrations plug in through a common fabric.
46–71 weeks
of commodity engineering eliminated before you write a line of business logic. See the breakdown →
Composable
auth, multi-tenancy, CRM, payments, reporting, scheduling, AI and more — opt into what you need.
Day one
auth, messaging, observability, integrations and compliance already in place — your team starts on business logic from the first commit.
Architecture Methodology
The Pyraburg Principle
Eight structural layers give the platform its stability; the iceberg line means your team owns the top 20% — business logic, UI surfaces, custom agents — while 80% of the machinery runs invisibly beneath.
Every layer has a purpose and every component has a clear boundary. The interactive layer-by-layer breakdown lives on the architecture page.
See the architecture in detail
Dive into the Pyraburg layers, component relationships, data flows and the full tech stack.