Twelve modules. One set of rules underneath them.
Most business software makes you choose between a suite that does everything badly and a stack of tools that never agree on who you are. The platform is one substrate — identity, isolation, audit, residency — with modules switched on as you need them.
What every module inherits
These four are not features of a module. They are the reason a module can be trusted with anything.
One database, isolation enforced in it
Access rules live in Postgres and deny by default. A query that cannot prove which tenant it belongs to returns nothing — the isolation does not depend on application code remembering to filter.
One identity, one audit trail
Per-admin accounts with two-factor available on every account. Privileged actions are written to an append-only trail, so the record of who did what does not depend on the module they did it in.
One residency decision
Where a workload may run is decided before the request leaves, and refused if it cannot be satisfied. Adding a module does not add a new place your data might end up.
One approval gate
Nothing a model writes is sent or actioned on its own. Drafts wait for a person, and the approval is recorded alongside the draft.
The suite, by what it does
Status is the real status. A module marked planned is a module we have designed and not yet built, and it will keep saying planned until that changes.
Operations
4 modulesUnified Dashboard
In buildEvery module in one workspace, with a single view of what needs you now.
Calendar & Reminders
In buildOne calendar of record. Deadlines land automatically and chase themselves.
CRM
In buildContacts, deals and follow-ups that keep themselves current so nothing slips.
ERP · MRP
PlannedInventory, demand and resource planning that anticipates instead of reacting.
Communication
2 modulesMessaging Agent
In buildTurns the traffic across your messaging channels into tasks, deadlines and answers, with reply drafts you approve.
Email Agent
PlannedTriages the inbox, surfaces what needs you, and drafts the rest for a one-tap approval.
Assurance
3 modulesWeb Compliance Agent
LiveScans a website for accessibility, SEO and security-header problems and returns a prioritised fix list.
Cybersecurity Posture
PlannedContinuous posture scoring mapped to the frameworks your buyers actually ask about.
Regulatory Compliance
PlannedJurisdiction-aware obligations, consent records and breach workflows in one place.
Intelligence
3 modulesResearch Agent
PlannedMulti-source research returned with its citations, including market and trade-show intelligence.
Business-Case Agent
PlannedModels, projections and board-ready narratives built from your own operating data.
Knowledge Management
PlannedThe answer your team needs, with the document it came from attached.
Detail on each module, including what it does and does not do today, is on the modules page. Sequencing is on the roadmap.
The controls are the product
A platform that holds your operating data earns that on evidence. Here are four of the ten controls that are merged today — the security page carries all of them, and the four things we have not done yet.
Per-admin identity
Every administrator has their own account. Two-factor authentication is available on every account, using time-based codes and single-use recovery codes.
Least privilege by default
A capability is off unless it has been explicitly switched on for that tenant. The check is an equality test against an explicit true, not a truthiness test.
Append-only audit trail
Privileged actions are recorded to an append-only trail. Records are added, never edited in place.
Secret scanning on every push
Every push and pull request runs a secret scan that fails the build on a hit. It is a blocking check, not an advisory one.
See it against your own site first.
The Web Compliance Agent is the module that is live today. Point it at your domain and it returns a prioritised list of what is wrong, mapped to the clause each finding comes from. You do not need an account to run it.