Integrations

Works with the tools you already use.

Connect the agent you code with, the repository you push to and the cloud you own. Every tile says its status plainly. Nothing here is implied.

  • Early accessPart of the early-access scope, confirmed per project.
  • Via MCPWorks through the open Model Context Protocol.
  • RoadmapPlanned. Not available yet.

Agents and editors

Any client that speaks the Model Context Protocol can connect to Kapten. These are the ones we test against.

Clouds

Where your workloads run. Your account, your region, your bill.

Source and build

Where your code lives and how it becomes an image.

Data and services

The dependencies your application expects, provisioned as managed services in your account.

Runtimes

If it runs in a container, it runs on Kapten.

  • Node.jsNext.js, Express, Nest, Remix…Early access
  • PythonFastAPI, Django, Flask, workers.Early access
  • GoStatic binaries, tiny images.Early access
  • Ruby, Java, .NET, RustAny containerised runtime.Early access

Notifications and signals

Where the crew reports, and what it reads.

  • SlackApprovals and incident updates in a channel.Roadmap
  • OpenTelemetryBring traces and metrics you already emit.Roadmap
  • WebhooksRun events to your own systems.Roadmap

Missing something?

Tell us what your stack needs when you request access. Integrations are prioritised by what early-access teams actually run.

Request early access

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.

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