Skip to content

Seylo documentation

Deploy to Kubernetes clusters you were never given the credentials for.

Understand the model

Seylo holds no cloud credentials for your clusters and opens no inbound connection to them. Knowing why changes how you evaluate everything else.

What Seylo is

Create your organisation

Sign up, verify your domain, and understand the four roles before you invite anyone.

Create your organisation

Connect your identity provider

Entra ID, Google Workspace, Okta, Auth0, Keycloak, or SAML. Map your existing groups to Seylo roles.

Set up single sign-on

Connect a cluster

One Helm command, run by you, inside your cluster. It dials out; nothing dials in.

Install the agent

Deploy

Ship a new image tag through approval, watch the rollout land, and roll back from history.

Your first deployment

Connect a coding agent

Point Claude Code or another MCP client at one namespace you open. It never holds a cluster credential, and it cannot reach a second namespace.

Coding agents and MCP

Observe

Install the observability chart. Metrics, logs and traces stay in your cluster; Seylo queries them for dashboards, alerts and agents.

Observability

FinOps

Right-size from real usage at list prices, approve proposals item by item, and let Seylo apply savings only inside limits you set.

Cost and optimisation

The three things worth knowing before you evaluate

Section titled “The three things worth knowing before you evaluate”