promotion pipeline gatekeeper

Promotion gates for the pipeline you already run.

Add one step to your CI/CD and Lockstep enforces the order: register a version, validate it, promote it. Development to UAT to Production, never out of sequence.

One-month free trial. No payment details required.

# CI: register the new build in the first stage
- name: Register version in Development
  uses: iktech/publish-artifact-javascript-action@v1.0.0
  with:
    apiToken: ${{ secrets.ARTIFACTZ_TOKEN }}
    stage: Development
    flow: Simple
    name: payments-api
    type: DockerImage
    version: 1.4.2

# Later: promote it to the next stage in the flow
- name: Promote to the next stage
  uses: iktech/push-artifact-javascript-action@v1.0.0
  with:
    apiToken: ${{ secrets.ARTIFACTZ_TOKEN }}
    stage: Development
    name: payments-api

The gap in most pipelines

Pipelines deploy. Nothing governs promotion.

CI/CD tools are good at shipping whatever they are told to ship. They are not built to decide whether a version has earned its place in the next environment.

  • Skipped stages

    A build goes straight to production because nothing in the pipeline said it could not.

  • Version drift

    latest points at something different in every environment, and nobody is sure what was actually tested.

  • No single answer

    “Which version is running where?” should take one look, not a search through build logs.

The dashboard

One look tells you which version is running where.

Every registered artifact and every stage in a single table. See what is in production, what is waiting in UAT, and what has only reached integration test.

Registered ArtifactsFlow: All
ArtifactProductionUATIntegration testDevelopment
demo-frontend1.2.0.61.2.0.61.2.0.8not in stage
demo-customer1.2.0.71.2.0.71.2.0.16not in stage
demo-policy1.2.0.231.2.0.231.3.0.41not in stage
demo-dbnot in stagenot in stagev1.3.1v1.3.1
demo-clientnot in stagenot in stagenot in stage1.4.5
Outlined versions are ahead of production and still working their way through the flow.

How it works

Register. Validate. Promote.

Lockstep sits between your builds and your deployments and enforces one rule: versions move through your promotion pipeline one stage at a time, in order.

  1. Register

    Your CI registers each new build version in the first stage of its flow. That is the only way in.

  2. Validate

    Your CD pipeline asks Lockstep which version belongs to the stage, deploys exactly that version, and tests it there.

  3. Promote

    Push the validated version to the next stage with a single pipeline step. Any attempt to skip a stage is refused.

Features

Deployment governance without the ceremony.

Everything you need to control artifact promotion from development to production, and to prove afterwards what happened.

  • Stage-by-stage promotion gates

    Define your stages and combine them into flows. A version enters at the first stage and can only move forward one stage at a time.

  • One source of truth for versions

    See which version of every artifact is running in every environment, in one place, without asking around.

  • Promotion history and audit trail

    A complete record of every promotion for every artifact, ready for audits and compliance reviews.

  • Docker images and Java libraries

    Pin an exact image tag or library version to each stage instead of trusting latest.

  • Reusable flows

    Describe Development → UAT → Production once and reuse the same release flow across all your artifacts.

  • Scoped API tokens

    Separate read and write scopes let deployment pipelines look up versions without being able to change them.

Integrations

Works with the CI/CD you already run.

Lockstep integrates in both directions. Your CI registers new versions as they are built, and your CD pipelines retrieve the right version for each stage before they deploy.

  • Jenkins
  • GitHub Actions
  • Azure DevOps
  • Tekton Pipelines
  • Gradle
  • Argo CD
Read the getting started guide

Deployment automation

Promote a version, and the deployment follows.

Once promotion is governed, deployment can be automatic. Let each stage react the moment a new version arrives.

  • Event triggers

    Start a deployment automatically whenever an artifact version changes in a stage.

  • Stage bindings

    Give each stage in your release flow its own deployment rules.

  • GitOps with Argo CD

    Keep Kubernetes environments in sync as soon as a new version is promoted.

Pricing

Simple plans. Start free.

Every account starts with a one-month free trial with no usage limits. No payment details required.

  • Free

    €0/month

    • 1 user
    • Up to 5 artifacts
    • 1,000 API calls a month
    Start free
  • Heavy Usage

    €25/month

    • Up to 25 users
    • Up to 200 artifacts
    • Unlimited API calls
    Try it free

Prices exclude VAT where applicable. Full pricing details

FAQ

Questions, answered.

What is Lockstep?

Lockstep (formerly artifactz.io) is a SaaS service that governs artifact promotion in CI/CD pipelines. It records which version of each artifact belongs to each environment and only lets a version move to the next stage after it has been registered and validated in the one before.

What is artifact promotion?

Artifact promotion is moving one specific, already-built version of your software through your environments — for example Development, then UAT, then Production — instead of rebuilding it for each one. What you tested is exactly what you release.

How does Lockstep stop a version from skipping a stage?

You define stages and combine them into a flow. Once an artifact is linked to a flow, a new version can only be added at the first stage, and from there it can only be pushed forward one stage at a time. There is no path that jumps straight to production.

Does Lockstep replace my CI/CD tool or artifact registry?

No. Lockstep works alongside the tools you already use. Your CI registers each new version with Lockstep, and your CD pipeline asks Lockstep which version belongs to a stage before it deploys. Your builds, registry and deployment tooling stay where they are.

Which CI/CD tools does Lockstep integrate with?

Lockstep has plugins for Jenkins, GitHub Actions, Azure DevOps, Tekton Pipelines and Gradle, and supports GitOps deployments with tools such as Argo CD.

What kinds of artifacts can Lockstep track?

Docker images and Java libraries. You can pin a specific image tag or library version to each stage, and the Gradle plugin can resolve dependency versions from Lockstep during the build.

How much does Lockstep cost?

There is a Free plan (1 user, up to 5 artifacts, 1,000 API calls a month), a Standard plan at €15 a month and a Heavy Usage plan at €25 a month. Every new account starts with a one-month free trial with no usage limits, and no payment details are needed to sign up.

What happened to artifactz.io?

artifactz.io is now Lockstep. It is the same service with a new name, and existing accounts, API tokens and plugins keep working.

Bring your releases into lockstep.

Set up your stages, connect your pipeline, and know exactly which version is running where.

This website uses cookies. By continuing to browse this site, you agree to this use.