Prepare your first Kapten deployment.

1. Prepare your application

Choose one application to start with. Record its repositories, services, build methods, runtime configuration and data dependencies. Include background workers and scheduled jobs if the application needs them.

Identify a health check and a small user journey you can use to validate the deployment. Keep secrets out of documents and access requests.

2. Request access

Use the early-access form to introduce your team and project. Explain the environment you want to deploy and any provider, region or operating constraints.

The public demo uses sample data. It is a way to explore the intended experience, rather than a connection to your cloud account.

3. Agree the connection

During onboarding, confirm the supported provider or existing-cluster setup with the Kapten team. Review the permissions and credential handling for that connection with the person who owns the account.

Follow the connection instructions provided for your setup. Cloud-provider provisioning and external-cluster registration are different workflows; do not assume that one set of instructions applies to both.

4. Define an environment

A project groups your application. An environment represents a deployment context such as staging or production. Components are the workloads and dependencies that make up that environment.

Start with a non-production environment where possible. Specify its configuration, data needs and resource ownership before connecting the application source.

5. Validate a first release

Use the deployment workflow available to your account, inspect its output, and verify that the application serves the expected request. Check service connectivity and confirm that you can find runtime logs.

Before using the setup for production, work through the production-readiness guide with your team. Agree the recovery path and who will operate the environment.