Trelven

Keelson · Private preview

Ship to every AWS account, from inside your own.

Keelson builds, checks, releases and watches your software in one place. It installs in AWS accounts you own, so your code and your data stay with you.

For platform teams

One platform to run, not a set of tools to keep connected.

Most companies ship software with several products from different vendors and a team that keeps them working together. Keelson does that job as one product, with one place to look.

Your rules, on every change

The rules your organisation sets are checked automatically each time something is built or changed. A change that breaks one stops, and the developer is told how to fix it.

Guardrails

New teams from one screen

Teams, apps and environments are set up in the console. Developers push code and follow it to production without raising a ticket.

Self-service

No big-bang switch

Keelson reads the pipeline a team already has and can run beside it until the team is ready to move. Clusters you already run can be connected as they are.

Migration

Proof on demand

Every deploy, approval, waiver and change of settings is recorded: who did it, when, and why.

Audit

Capabilities

What you get.

Deploys

From a push to a running release.

Keelson builds the app, tests it, scans it and deploys it. Services on Kubernetes, ECS services and Lambda functions all go through the same steps, and so does the infrastructure your Terraform describes.

Each app page shows which release every environment runs and what can go next. Rolling back means choosing an earlier release that deployed successfully.

Environments

Built once, promoted in order.

You define the environments and the order a release moves through them. A release is built once and the same build is promoted from one environment to the next.

Each environment is tied to an account and a cluster, and has its own approval rule and its own secrets. You can freeze an environment for a period, and a promotion that skips the order is refused with the reason.

Approvals and guardrails

Checked every time. Never skipped, only waived.

Guardrails check every infrastructure plan and every build against your policies: required tags, restricted resources, cost limits, scan results. A waiver is a recorded decision with a name on it.

Where an environment needs approval, the run waits and shows who asked, who can approve and what is still needed. An emergency deploy asks for a reason and is reviewed afterwards.

Clusters

New clusters to your standard. Existing ones as they are.

Set the add-ons and node pools every cluster should have, and Keelson creates clusters that match. Platform teams keep one standard instead of one per cluster.

A cluster you already run can be connected too. Keelson reads it first and changes nothing until you accept what it found. When you disconnect it, Keelson removes exactly what it added.

Cost and resources

What you spend, and what it is spent on.

Spend across all your accounts, split by team, app and tag, with a year of history. Budgets can be set for the organisation, a business unit or a team, and reports show each team its share.

The resources page lists what each account holds, which team, app and environment it belongs to, and what it cost. Developers see their own team's spend and resources only.

Monitoring

What is running, and whether it is healthy.

One view of every account and cluster: nodes, workloads, add-ons and the network they are attached to, with alerts when something is wrong.

For each app and environment Keelson shows its traces, logs and metrics. App teams see their own namespaces, and production is read only for them.

Security

Know what runs, and where it came from.

Every image Keelson builds is signed with your organisation's key and carries a record of who built it, from which commit and from which base images. The signature is checked before a deploy runs.

Images are matched against new vulnerability advisories on a schedule, so a vulnerability published after your build is found without rebuilding. People sign in through your identity provider.

AI add-ons

The same rules for AI as for people.

Four optional add-ons, each off until an administrator turns it on.

  • Assistant. A chat in the console that answers questions about your setup and prepares changes for a person to review.
  • Your own AI agents. Coding agents your developers already use can read Keelson with that developer's permissions. They can read and check; they change nothing unless an administrator allows them to prepare changes.
  • Keelson agents. Agents that propose a fix for a failed build or a patch for a vulnerable image.
  • Model serving. Run your own language models on your own clusters, with keys, quotas and usage in one place.

Editions

Three editions, and add‑ons for AI.

Keelson is licensed by the number of workload accounts it deploys to, not per user and not per build. Pricing is agreed with each customer; there is no price list on this page.

Pilot

Try it in your own accounts

A time-limited evaluation in a small number of accounts, with everything in Enterprise and the AI add-ons on trial.

Business

Delivery for the whole organisation

Deploys, environments, approvals, guardrails, clusters, monitoring and audit. Also Lambda and ECS targets, existing clusters, help moving from your current CI, and cost reporting.

Enterprise

For larger and regulated estates

Everything in Business, plus application traces and service levels, enterprise sign-in and provisioning, access reviews, vulnerability management, approvals in chat and ticketing tools, and private networking options.

Add-ons

AI, when you want it

The Assistant, the connection for your own AI agents, Keelson agents and model serving are licensed separately and can be added to any edition.

Requirements

What you need.

AWS accounts you own

One account hosts Keelson. The accounts your workloads run in connect to it. Keelson runs in your accounts, not in ours.

Self-hosted

Their account IDs

We share the Keelson container images with the accounts you name, so we ask for their 12-digit IDs when you request a demo.

Private images

Your Git and sign-in

Keelson reads code from your Git provider, and people sign in through your identity provider.

Your tools

Next step

See it with your own accounts in mind.

Tell us which accounts and region you would use. We will show you Keelson and, if it fits, set up an evaluation. Setup guides are shared with people we are evaluating with, not published here.

Request a demo All Trelven platforms