Platform
Where it runs is your decision, not ours
Some clients cannot put project data on somebody else's machine, and that requirement is usually contractual rather than negotiable. Both options run the same software.
Hosted
Run by us, in the European Union. Updates, backups, monitoring and restore testing are ours. This is the right choice for most organisations and it is the one that costs less in total, because the alternative includes somebody's time.
On your own infrastructure
Installed on servers you control, on your premises or in your own cloud tenancy. You keep physical custody of the data; you take on the operational responsibility that comes with it — backups that are actually restorable, an upgrade window, and somebody whose job it is.
We will say plainly when this is the wrong choice for you. A shop of thirty people rarely benefits from running its own instance, and a client requirement that has never been tested is worth testing before it drives an architecture.
What the field work needs
Field capture is built to work offline. An inspector in a yard with no coverage records what they see and it synchronises when a connection appears. This is not a degraded mode bolted on afterwards; the alternative is paper, and paper is what we are replacing.
Documents
Sealed documents are rendered server-side, deterministically, so that regenerating a document later produces the same document. Verification pages are public by design: a third party holding a certificate must be able to check it without an account and without contacting you.
Getting your data out
Full export in open formats — the records, the attachments, the sealed documents and their verification data. No notice period, no per-export charge, and no format that requires our software to read.
This is worth being blunt about: a quality record you cannot take with you is not a record you own. Ask every vendor how their export works before you sign, and ask them to demonstrate it rather than describe it.
Updates
Hosted instances are updated by us on a schedule you can see. Self-hosted instances are updated by you, with a supported version window — running a version several years old is possible and it is not supported indefinitely, because the codes underneath it move.