Government
For ministries, agencies, and statutory bodies.
Cross-agency federation without data leaving the ministry. Compliance built in (PDPA, MyGovEA-aligned). Audit-immutable by default.
Phase 4 — shipped · Government Hub modules
For governments, startups, third sector, investors, and individuals.
Same codebase. Different Hubs. One federated network.
Every Hub is a self-contained installation with its own cryptographic identity. Same codebase whether you're a ministry, a startup, or a citizen.
The Hub Federation Protocol exchanges verified credentials and anonymised aggregates — never raw PII. Permission grants are explicit, auditable, and revocable.
Every Hub speaks MCP today, and A2A, ACP, and AP2 ride federation as signed envelope subtypes. Agents act under the same permission model as humans.
Every clip below is a screen recording of the current build — one government Hub running the chassis plus six module collections, captured straight from the dev stack.
Eleven legal-entity kinds on one spine, NRIC encrypted at rest, Hub-signed credentials with StatusList2021 revocation, and a federated life-event work queue. BM + EN.
Documents encrypted at rest, shared only through revocable grants. The wallet holds verified third-party credentials and presents them without surrendering the originals.
Double-entry accounts, journal, and budgets. It issues Hub-signed income-band attestations — a tax filing consumes the band, never the ledger.
HR, departments, budgets, and procurement next to documents, workflows, and forms — the same chassis, immutable audit log underneath.
A Hub is what a WordPress site is to the web — a sovereign installation that becomes whatever its modules make it. Pick the door that fits.
Cross-agency federation without data leaving the ministry. Compliance built in (PDPA, MyGovEA-aligned). Audit-immutable by default.
Stop re-entering the same data into twelve portals. Submit verified credentials to programmes. Run your own ops without surrendering your dataset.
Portfolio Hubs share metrics with you, not raw books. Federated diligence. Reporting that doesn't require a quarterly spreadsheet ritual.
A private Hub for your credentials, documents, and life-event flows. Sign in once. Prove what you need to prove. Hold the originals yourself.
Most platforms add privacy after the data has already been centralised. OmniHub never centralises it in the first place. Every Hub holds its own data; every cross-Hub exchange is mediated by the Hub Federation Protocol.
A standard HFP-ID at /.well-known/omnihub-hub declares the Hub's DID, public key, and supported protocols.
Before any data crosses, the requesting Hub declares purpose, retention, and the agent (if any) initiating the exchange. The receiving operator grants or denies.
Hubs answer with verified yes/no attestations, differentially-private aggregates, or tokenised datasets. The raw rows stay home.
A Postgres trigger rejects mutations. Both Hubs hold a hash-chained record. Operators can prove what happened — and what didn't.
Phases 1–4 of the roadmap are complete and tagged (v0.4.x): the chassis, the organisational Hubs, the Individual Hub, and the Malaysian Government Hub — roughly 1,850 backend tests green at PHPStan level 8, plus a full-stack browser e2e suite. We'd rather show you the roadmap than the marketing brochure.
Every Hub operator owns their data absolutely.
PII never crosses Hub boundaries in raw form.
Community Edition is AGPL-3.0, forever.
AI agents are first-class actors, not bolt-ons.
OmniHub is designed to be deployable anywhere Docker runs. No mandatory cloud, no phone-home, no telemetry you didn't opt in to.