Platform
One platform underneath every application
Each module is a view onto the same records, the same people and the same workflow engine. Switch a module on and it inherits everything below: the control library, the organisation tree, the access model, the audit log.
Reading the same record
Risk register
scores against it
Architecture
Six layers, one thread
Each layer references the one below it. That is what makes traceability a property of the model rather than a reporting exercise run after the fact.
- 1OrganisationLegal entities, locations, departments and functions, modelled separately, because regulators care about the legal structure and work happens in the operational one.
- 2Strategy, execution and financeVersioned strategies, a weighted objective tree, initiatives down to tasks, and budgets that follow the same spine, so an objective knows what it costs and what delivers it.
- 3Business catalog and assetsDomains, capabilities, services, processes and the asset register, so technical findings can be expressed as business impact.
- 4Control libraryJurisdictions, authorities, domains, controls, questions and maturity descriptors. Every framework is a view onto this layer.
- 5Risk and complianceRegisters, indicators, assessments and third parties that all resolve against the same controls rather than keeping private copies.
- 6Evidence and auditReviewed evidence, findings with dependency-aware remediation, retention and legal holds, and an append-only platform audit log.
Strategy to control
Does our risk profile threaten our plan?
The strategy deck and the risk heatmap are usually two documents nobody can join. Here they are one chain: strategy, objectives, risks, indicators, delivery work and money, so the board can ask which objectives are exposed, what is being spent to protect them, and whether it is working.
Strategy and objectives- StrategyTechnology & cyber resiliencev3 · published
- ObjectiveResidual cyber risk within appetiteweight 10% · 2 risks
- InitiativeCyber defence modernisationfunded · on track
- ProjectPAM completionmilestone 31 Oct
- TaskMigrate service accountsdue Friday
- PersonSarah Whitfieldassignee
Control
Privileged access is reviewed each quarter by the system owner
PPTDF applicability
One owner · one procedure · one evidence trail
Control library
Frameworks are views, not silos
One control carries mappings to every standard that references it, each graded rather than boolean, with one standard marked primary. Import any standard you are held to, wherever you operate; where two ask for the same thing, the control is tested once.
Frameworks and controlsWorkflow Designer
No code, but real logic
Every lifecycle-bound module ships with a system flow you can copy and change: structured conditions, scheduled and date-field triggers, approvals, escalation ladders and acknowledgement campaigns, drawn as a flowchart, simulated before publish, and run by the engine with every step logged.
The Workflow Designer- Finding created · severity ≥ HighTrigger
- owner.department = TechnologyCondition
- Remediation plan → Head of TechnologyApproval
- No decision in 5 days → CISOEscalation
- Set state: In progress · notify assigneesAction
Versioned, simulated before publish, run by the engine with every step logged
Active company
One context at a time
Every tenant-scoped row carries a company foreign key. Access is validated per request, and the active company is selected explicitly, so there is no default-company fallback to fall through.
Tenant isolation at the database
Below the application, on every query
Database row-level security enforces company boundaries for every module, independently of application code. A permission check that is wrong in the application still cannot read another tenant's rows, and the runtime refuses to start with a role that could bypass it.
Security and trustAccess model
Permissions per action, owned by people
Bundles operate on individual lifecycle transitions, roles are scoped to entities and objects, and separation-of-duties pairs are declared rules with logged exceptions, which is what makes segregation of duties demonstrable rather than asserted.
Access control| Action | asset-viewer | asset-coordinator | asset-approver | asset-admin |
|---|---|---|---|---|
| View | Allowed | Allowed | Allowed | Allowed |
| Create and edit | Not allowed | Allowed | Not allowed | Allowed |
| Submit for intake | Not allowed | Allowed | Not allowed | Allowed |
| Send to review | Not allowed | Allowed | Not allowed | Allowed |
| Send back | Not allowed | Allowed | Allowed | Allowed |
| Approve | Not allowed | Not allowed | Allowed | Allowed |
| Activate | Not allowed | Not allowed | Allowed | Allowed |
| Module settings | Not allowed | Not allowed | Not allowed | Allowed |
Every module ships bundles at this granularity. Segregation-of-duties conflicts are declared as rules, with logged exceptions.
- Board risk pack · Q3Group · 12 entitiesGeneratedMon 06:00
- Compliance posture · ISO/IEC 27001Northbridge BankScheduled1st monthly
- Third-party concentrationGroupGeneratedFri 18:00
Dashboards and reports
Same figures in the dashboard and the report
Report templates, schedules and runs with recorded scope; share links with an access log; webhooks and BI export. Generated reports are stored alongside the records they cite, so the number in the board pack cannot drift from the register.
Reporting and dashboardsInherited by every module
Platform services
Switch a module on and it gets all of this without configuration.
Roles and separation of duties
Records are owned by named people. Object-level scoping, SoD pairs and role-gated transitions decide who may move what, in every module.
Learn moreLinked records
Any record links to any other, in both directions. A detail page shows the whole neighbourhood: risk, control, asset, objective, finding, vendor.
Learn moreDashboards and reports
Executive dashboards across compliance, findings, policy, risk, strategy and finance; generated reports stored with the evidence they cite.
Learn moreImport, custom fields, languages
Bulk data import, custom fields on any module, notification rules, full-text search and per-user locale, including right-to-left languages.
Learn moreDocuments and evidence
Collect once and cite from every record that needs it. Checksums, classification, retention policies, legal holds and evidence packages.
Learn moreMy Work and notifications
One queue of tasks, approvals and acknowledgements across every module, with multi-channel notifications and per-user preferences.
Learn moreDeploy your way
On your infrastructure, or ours
Both modes are supported and maintained, for organisations wherever they operate. For hard data-location requirements, on-premise is a real answer rather than a roadmap item. Packaged as Startup, Mid-Market and Enterprise tiers.
Single-tenant, on your infrastructure
One organisation, one deployment, running on infrastructure you control. Where data lives is your decision, not a vendor policy.
- Deployed into your own environment, wherever that is
- Single company record in the database
- No dependency on shared hosted infrastructure
Multi-tenant SaaS
Hosted in a single agreed region per customer, with isolation enforced by the database. Users may hold access to several companies and switch context explicitly.
- Row-level security on every table, for every query
- Access validated per company on every request
- No default-company fallback in critical paths
See the platform against your own structure
Bring your entity hierarchy and the frameworks you report against, and we will walk the model end to end on a fully populated demonstration tenant.
No commitment required. A typical demo runs 45 minutes.