Rivet

Deployment under control.

Rivet deploys only what passed verification and what a person approved. A deployment is done only once Rivet has also checked the live environment.

Rivets

Production needs a second confirmation.

Once approved, a plan stays fixed. Every deployment leaves a record, and an uncertain result is never passed off as a success.

A production deployment plan in Rivet: verification by Temper is done, and the launch waits for a second confirmation.

What you verify before deployment.

  • Exactly what you approved will run.

    An approved release plan in Rivet: the exact version of the app, how long the plan is valid, and both approvals.
  • What runs where.

    Deployment history in Rivet: for each app and environment, the last verified release and the deployment time.

From plan to verified release.

  1. An exact plan.

    The plan sets the version, the environment, and the procedure, and stays fixed once approved.

    A release plan in Rivet: the environment, the artifact and its exact version, how long the plan is valid, and the record of the plan and production approvals.
  2. Evidence from Temper.

    Without a verified test, the plan doesn’t pass.

    Evidence from Temper in a release plan: a link to the run, the project, the profile, the verdict, and the verified criteria.
  3. Approval.

    Production needs a second confirmation.

    Production approval in Rivet: a launch to the production environment is allowed only after a second confirmation that names the environment.
  4. Deploy and verify.

    The result is recorded only after the real environment is checked.

    Deployment progress in Rivet: queued, deployed, verified, checked by Temper, and the result Verified.
  5. History.

    For every app, you see the last verified release.

    Deployment history in Rivet: for each app and environment, the last release, the deployment time, and the status Verified.
Server management in Rivet: a production and a test server with the results of availability, disk, memory, and service checks.
Server checks and incidents in one place.

What you can count on.

  • An uncertain result is not passed off as a success.

  • Two deployments to the same environment never run at once.

  • Server checks and incidents are in one place.

See how Rivet deploys.