For Accountability — in your Change Management Process

Your change management process is already defined, and it is defined for a reason. Evitrus verifies every change against it, continuously, so the company's posture is the process it actually follows. From that same record you can see what changed, and how fast you ship.

Linear, GitHub and compute send events into Evitrus. Change Groups fill, shift, and feed metrics. Compute asks; Evitrus answers allow or block.
Signals from Linear GitHub GitHub Actions Kubernetes ECS SDK

The problem

Accountability still means reconstructing every change.

Your change management process already produces a ticket, a review, and a rollout. Those facts sit in Linear, GitHub, and the cluster — not in one record. When someone asks what changed, who approved it, and whether the process was followed, you join the events from those tools by hand.

Tracking a change means following breadcrumbs.

In an incident you open the rolled-out version, walk the git history, and look for the pull request. You hope that pull request has a ticket. The ticket is what says why the change was made, and whether it can be reverted safely.

Every tool's integration is its own project.

Someone has to build and keep the connections from the ticket, to the pull request, to the service that rolled out. When that work falls behind, or the tools change, the record tracking falls apart.

An auditor asks about one change.

Three months after the deployment, someone asks why this change was rolled out and who approved it. The question goes back to the engineering teams, in the hope that the internal process was followed at the time and the evidence is still in the system.

How Evitrus helps

The events are collected as the change happens.

Evitrus keeps change events from the tools you connect in one stream. People who do not work in those tools every day can read the same stream.

See what, who, and why.

You can read what rolled out, who acted, and why, as completely as those systems documented it. A pull request and a rollout are shown as one change when they share a tag. A Linear issue is kept in the same stream, with its identifier and its title.

Check a recorded change against the process you expect.

Evitrus can look for a review, a deployment to staging, a successful test or scan, or similar events before the rollout. And you can add further checks that look for other events. The result is shown on the change, so you can see if the process was followed.

You can refuse a rollout that misses a guideline you set.

After defining a policy, you can enforce it. Instead of finding out after the fact, you can block a rollout that misses a guideline you have set up before it hits production.

Sometimes the process has to be skipped.

Evitrus supports audit-tracked emergency windows, in which the controls are skipped. The bypass is recorded on the same stream as the other events, so you can see who used it, when, and why.

How it works

Five steps. One evidence chain.

Evitrus ingests events from the tools you already use, groups them into Change Groups, and gives you insights and customizable enforcement for your change management processes.

Use cases

Built for the people who get asked.

Security

Signed at ingest. Hosted in Germany.

To ensure you trust the data, we have built Evitrus with a strong focus on security and privacy.

Tamper-proof events

Each event is sealed with a content hash when it is stored. Events cannot be modified after they are accepted.

Hosted in Germany

The managed service runs in Germany. The events you send stay in that European Union cluster.

Strong tenant isolation

Tenant isolation is enforced at the core of Evitrus, from the API down all the way into the data storage.

For more detail, see the security whitepaper.

Closed beta

Sign up

Want to give it a try? We are still in closed beta. You can give us a short introduction and we will be in touch!

We may contact you about the beta. See our privacy policy.

Not convinced? Try out the demo!

Browse Evitrus in Demo mode to get a feeling. It’s read only access to a full feature tenant with seeded data.