Evidence that your agent stays on its rails
A Vijil certificate says this agent, on this harness, against this policy, scored this on this date. It is produced again with every change, so the evidence stays as current as the agent.
What the certificate says, and what it does not
A certificate is an assertion we make to a third party: scoped, dated, and expiring, carried on the agent card, produced from the trust score at one point in time. It does not say the agent is safe, and it does not say the agent will still score that next quarter. That is why it carries a date rather than a verdict.
It is an artifact, not a status. A lapsed certificate does not make an agent worse; it makes the claim stale. Reverifying on every change is what keeps the claim true, and it is why verification belongs in your release process rather than in a one-time audit.
Every release, verified
Each step is labeled with what you can run today, what we set up with you, and what is still in development.
Register the agent. It gets an identity and an agent card that carries its declared purpose, tools, and policies.
$ vijil register ./my-agentEach code or configuration change runs an evaluation in your CI, against your policies, for reliability, security, and safety.
$ vijil evaluateThe release passes or stops on the result. We set the gate up with you during the six-week engagement.
Dome enforces the same policies at runtime, on the agent's inputs, outputs, and tool calls.
$ vijil protectVijil issues a signed certificate on the agent card: scoped, dated, and expiring.
Darwin, now in development, will propose fixes as pull requests when production telemetry shows a failure.
Start with one agent in six weeks
We run the lifecycle with you on one agent, set up the release gate in your CI, and hand you the controls for the next one.