Start with a sandbox. Move to production when you are ready.
Sign up in the Portal, create an organisation, open a sandbox. When you need production, join the waitlist.
Sandboxes run on staging with test data. Production access is by waitlist.
Security and trust
The rules the engines enforce.
We publish principles and mechanisms, not badges. Every item below describes something the engines or the Portal actually do.
-
Tenancy: the key is the address
An API key identifies the tenant. What is stored is an HMAC-SHA256 of the secret, never the secret itself. An unknown key receives a uniform 401 so that key probing learns nothing.
-
Secrets shown once
A sandbox API secret is displayed once at creation. It is not retrievable afterwards; rotate to obtain a new one.
-
Environment isolation
Portal trials provision only in the staging databases of each engine, through the engines' platform doors. Production platform doors are closed: no production platform secret exists. LedgerHash platform sandboxes are constrained in the database to the test environment; BookingHash sandbox keys are bh_test_.
-
Server-side only
The browser never calls an engine. Every engine call is a Portal server-side adapter call. This marketing site makes no calls to any engine at all.
-
Hash-chained audit
Every fact writes its event in the same transaction. BookingHash keeps a per-booking SHA-256 chain with insert-time seal guards and triggers that block updates and deletes. LedgerHash seals entries and closes periods under a Merkle root; seals are immutable for every role.
-
Write-once anchoring
Both engines support anchor records written to storage with Object Lock in compliance mode. BookingHash anchoring is a per-tenant daily opt-in; LedgerHash anchoring is operator-triggered. Neither is automatic for every record.
-
Hosting and processors
Engine data lives in AWS, eu-west-2 (London). The Portal is hosted on Vercel and uses Clerk for authentication, Resend for transactional email and Upstash for rate limiting. This site is served by Cloudflare with cookie-free analytics.
What we do not claim
- No certification or third-party audit is claimed. When something is independently verified, it will be stated here with its scope.
- No uptime, latency or incident statistics are published.
- Hashing is tamper-evidence, not encryption and not secrecy.
- Nothing here is a public network; verification is tenant-scoped.
Reporting a security issue
If you believe you have found a security issue, contact us through the channels on the contact page. Please do not test against production systems or other tenants' data; the acceptable-use policy applies.