Deploy pipeline

From the code you write to the service you run.

Bring your repository, define the environment and follow your release. Keep builds, deployment output and application health in one continuous workflow.

Request early accessExplore the demo
Source
Your application repository
Build
Dockerfile or supported builder
Context
A named environment
Visibility
Build and deployment output

Inside the product

A release is more than a build.

Give every step its place, from the first commit to the moment the application is ready to serve.

Interface previews
Illustrative data · Early access

  • From commit to a running service

    Keep the source, build and release in one workflow. Follow the change from your repository to the environment where it belongs.

  • Your build, your way

    Bring your Dockerfile or use the supported build path for your application. Keep the build settings close to the service that uses them.

  • Know when it is ready

    A successful build is the start. Follow the rollout and check that the new application version can actually serve traffic.

  • Keep the previous release close

    Find the version that was running before a change. Plan recovery around a known build, with database migrations considered separately.

  • A place to review each change

    Preview environments are designed to bring the application and its dependencies into a separate review context before production.

    Planned capability

  • The output stays with the run

    Read the build and deployment output in context. When a release needs attention, start with what happened during that run.

See it in context

Watch a release come together.

Follow a sample application from source to deployment. The walkthrough connects the build, the services and the environment they run in.

kapten / deployProduct preview
Illustrative experience with sample data.Open the interactive demo

Early accessBuild methods, rollout controls and preview automation depend on the capabilities available to your early-access setup.

The workflow

A release your whole team can follow.

  1. 01

    Connect the source

    Choose the repository, branch and build method for the service.

  2. 02

    Define the destination

    Set the environment, configuration and dependencies before the release.

  3. 03

    Follow the outcome

    Inspect the build, rollout and application health in sequence.

Planning a first deployment?Work through the readiness guide

Good to know

A little more
before you start.

Have a particular application or setup in mind? Bring it to the early-access conversation.

Talk through your setup ↗
Can I use my own Dockerfile?

The deployment design supports a repository Dockerfile. Confirm the build context and runtime requirements for your application during onboarding.

Does rollback undo a database migration?

Restoring an application version and reversing a database change are separate operations. Plan migration compatibility and data recovery alongside the release.

Are preview environments automatic?

Pull-request lifecycle automation is part of the roadmap. Confirm which triggers and cleanup controls are available for your early-access setup.

Connected capabilities

One part of a bigger picture.

Build with Kapten

Start with one service.
Build from there.

Tell us what you want to deploy. We review each request and follow up about fit and onboarding on your preferred cloud.

Request early access Explore the demo

Free during early access. No card required. Cloud usage billed separately.