Choosing your vessel
Stop managing compliance in spreadsheets
Spreadsheets, GRC platforms and outside counsel are each built for a different job. This page sets out what each is for, and what Landfall adds.
What Landfall does
The corpus behind it is 12 binding regulations and 6 technical standards, 421 obligations in all, across 7 jurisdictions.
| Capability | Landfall | How |
|---|---|---|
| Pre-built regulation library (12 regulations, 6 standards)Unique421 obligations, each cited to its article and versioned with the seed | 421 obligations, each cited to its article and versioned with the seed | |
| Deterministic EU AI Act risk classificationUniqueRules over your questionnaire answers; no model in the loop, the basis recorded per flag | Rules over your questionnaire answers; no model in the loop, the basis recorded per flag | |
| Obligation-to-ticket translationUniqueBacklog items with acceptance criteria and the article attached | Backlog items with acceptance criteria and the article attached | |
| Product-specific mappingTrigger conditions over your answers, recomputed when they change | Trigger conditions over your answers, recomputed when they change | |
| AI interpretation, optionalNarrative on the provider you choose, or none at all; never a verdict | Narrative on the provider you choose, or none at all; never a verdict | |
| Code scanningFindings by pattern, file and line; file contents never enter a prompt | Findings by pattern, file and line; file contents never enter a prompt | |
| Exports to Jira, Linear and GitHubTickets with citations, plus a JSON audit bundle and the audit report | Tickets with citations, plus a JSON audit bundle and the audit report | |
| Hash-chained audit trailUniqueEach entry carries the hash of the one before it; the report verifies the chain | Each entry carries the hash of the one before it; the report verifies the chain | |
| Evidence collectionEvidence attached to the obligation it satisfies, with the retention decision logged | Evidence attached to the obligation it satisfies, with the retention decision logged | |
| CI gateUniqueAn authenticated HTTP check your pipeline calls; strict mode fails the build on an open gap | An authenticated HTTP check your pipeline calls; strict mode fails the build on an open gap | |
| Multi-jurisdiction coverage7 jurisdictions, selected per project | 7 jurisdictions, selected per project | |
| Coverage gap detectionObligations that apply but have no approved mapping are listed in the report | Obligations that apply but have no approved mapping are listed in the report |
The full picture
Each approach is built for something. Here is what, and where Landfall fits next to it.
Spreadsheets and wikis
Sheets, Confluence pages, shared documents
Built for
- Recording what the team decided, in a format everyone can open
- Getting started today, with no procurement
- Sharing a list with anyone inside or outside the organisation
What Landfall adds
- A mapping that is recomputed from the rules when your answers change
- The article attached to every ticket, rather than a cell reference
- A hash-chained audit log in place of an edit history
Good for documenting. Landfall keeps the document and the mapping in step.
Enterprise GRC platforms
Risk, control and policy management suites
Built for
- Organisation-wide risk and control registers
- Policy management and attestation campaigns
- The compliance and audit functions as the primary users
What Landfall adds
- Obligation-to-ticket translation for the engineers who build the product
- A deterministic, rule-based mapping with the basis recorded for every verdict
- A CI gate, so an approved mapping is enforced in the pipeline and not only reported
Built for the compliance function. Landfall is built for the product team that has to ship the change.
Outside counsel
Law firms and compliance consultants
Built for
- Interpreting a novel question of law
- A defensible opinion on a specific decision
- Representation when it matters
What Landfall adds
- A standing mapping that updates when your product changes, between opinions
- Engineering tickets with the article attached, ready for counsel to review
- An audit trail that records what was decided and on which basis
Counsel decides the hard questions. Landfall makes sure the answer reaches the backlog and stays on record.
Built differently
Landfall is built for the teams that have to turn a regulation into engineering work: in public bodies, in banks and insurers, and in product teams.
Obligation to ticket, article attached
Every backlog item carries the obligation it implements and the article it comes from, with acceptance criteria an engineer can act on. An engineer, a privacy officer and an auditor read the same line.
Deterministic, rule-based mapping
Which obligations apply is decided by trigger conditions over your answers, not by a model. The same answers give the same mapping, and the basis for each verdict is recorded. AI is optional and writes narrative, never a verdict.
Hash-chained audit trail
Every decision, approval and export is logged, and each entry carries the hash of the one before it. The log is tamper-evident, and the audit report includes the verification.
A gate in your pipeline
The CI gate is an HTTP check your pipeline calls against the project. In strict mode it fails the build on an open gap, so compliance becomes an exit code your engineers already understand.
See it on your own product
Bring a product or service you are responsible for. We walk through the mapping on it, with the articles attached.