Keep the same verifiable evidence model. Gain control over identity, deployment and operations.
Enterprise does not change what Tallwright proves. It changes who holds which role, where the software runs, and which legal entity operates each part. For organisations with stricter security, procurement, governance or internal-control requirements.
Why Enterprise.
Your policy says keys stay in your KMS or HSM, or that evidence infrastructure runs inside your perimeter. Cloud Proof's managed identity is not enough.
A reviewer needs to name the legal entity behind every role, the hosting location, and the operational commitments before signing.
Your own audit function wants to witness the evidence chain itself, or wants an independent organisation alongside Tallwright.
Deployment paths.
Four roles decide the trust boundary: who holds the content, who hosts the evidence log, who witnesses, who holds the keys. Each path moves roles toward you. Status is stated as it is.
Managed and Self-Hosted are deployment choices, not customer categories. Vendors use them too. No public prices exist for them; the conversation starts with your requirements.
Control the trust boundary.
The question a reviewer asks is not “is it secure” but “who, exactly, does what, and under which contract”. This is the answer, role by role.
The organisation whose agents produce the records and whose customers may later challenge them. Owns the content throughout.
Whoever runs the Tallwright software: Tallwright under Cloud Proof and Managed, your team under Self-Hosted.
Where the evidence log lives. Always inside your environment; Tallwright never hosts it.
The independent party that witnesses checkpoints. Tallwright by default; your auditor, or another independent organisation, as an addition.
Managed by Tallwright under Cloud Proof. Under your control with Own Identity, when it ships.
Each role is attributed to a named legal entity in the contract and in the Witness Practice Statement, so an auditor can trace responsibility without asking.
Enterprise requirements.
Named roles, least privilege, SSO where your identity provider requires it.
Documented custody, rotation and separation per deployment path.
Every witnessing and every verification logged, exportable.
Separate Environments for staging, marked as such on verification.
Proof history backed up and restorable; reconciliation after restore.
Defined process, notification windows, post-incident reports.
What you can hand your reviewer today.
The Witness Practice Statement, security documentation, the DPA with technical and organisational measures, the subprocessor list and the Verification and Evidence Policy. Later audits and certifications are listed with their real status.
When scrutiny gets serious.
Audits, investigations, disputes, third-party review. Under every deployment path the other side gets the same thing: a check they run themselves, against a witness that is not you.
Tallwright establishes integrity and evidence consistency: that a presented record matches the witnessed state and that the chain is intact.
It does not establish truth or completeness, and no deployment choice makes it do so. Self-Hosted gives you control of operations, not a different claim.
Tell us which roles you need to hold.
Identity, hosting, witness, operations. We reply within [RESPONSE TIME] with what we can meet now, what is coming, and what it costs.