Opening up: public docs and a live demo

From today, two things about Vera are public that used to require a sales call.

The documentation. Architecture, API reference, MCP server, deployment, security and data governance, and our validation evidence — the same documents our customers and their auditors use — are now published openly, both on this site and on GitHub. The reasoning engine and console source remain proprietary (they are the company), but the interfaces are open and documented in full: how the console talks to the engine is exactly how your systems can talk to it. Reviewers who need source-level access can get it under NDA.

The demo. A live demonstration environment running the real pipeline against a dedicated field-service demonstration workspace — two regions, three depots, technicians, vehicles, customers and a realistic rulebook. Report a disruption, watch the reasoning trace stream in, click the reference chips, reject a plan and read the unsat core. Access is gated behind a workspace sign-in; demo credentials are available on request.

Why do this? Because our entire pitch is verifiability, and a company selling verifiability should not ask you to take its word for anything. The architecture claims are checkable against the documentation. The product claims are checkable against the demo. The validation claims are written down with numbers and methodology.

There's also a market reason. European logistics is being courted by AI vendors whose products are impressive, opaque and hosted elsewhere. We think the winning position for European operational AI is the opposite: open interfaces, EU-region data, model sovereignty as a configuration option, and decisions you can prove. Publishing is how we hold ourselves to that.

Vera 1.4 itself brings the demonstration workspace, the documentation set, and a round of console polish. If you've been waiting for a reason to look — this is the easiest it will ever be.