Beta Open
Look around before you talk to anyone
The console is open in beta. Register, create an organisation, add a project and see how the pieces fit. No call, no demo booked in a week's time.
What beta means here
It is a real system, running the real pipeline. It is also an evaluation environment, and being straight about the difference matters more for this product than most.
- Do not put evidence in it you would need later. Send synthetic or scrubbed events. Anything that has to stand up in front of an auditor belongs on a box of your own.
- Expect it to change underneath you. Screens move, and environments may be reset.
- Beta signatures are beta signatures. Every mechanism is real and verifiable, and production signing keys are generated separately. Evidence sealed from then on is the evidence anyone would rely on in a dispute.
What to try
- Register an organisation and sign in.
- Add a project and an environment, and issue a key.
- Send a handful of events, using the copy-paste client in the docs.
- Fetch a receipt, verify it, then change one byte of the payload and verify again.
That last step is the whole product in ninety seconds. The send events and verify a receipt pages walk through both sides.
Coming soon
Listed so you can plan around it, and deliberately not described as available:
- Client libraries for Python, JavaScript and Go. Until then the API is the supported path, and it stays supported afterwards.
- Custom field mapping in the console — defining and mapping your own field names yourself. Today we write the mapping for you from a sample of your log lines.
- Anomaly detection over the sealed trail.
- Payload encryption and erasure, which is why beta boxes should carry synthetic data today.
Ready to run it on real events? Tell us what you need to prove and we will come back with what it takes to get you set up.