Skip to content
Telo CloudSign in

Preview · under active development

Deploy declarative backends to your own Kubernetes.

Telo Cloud is the control plane for Telo apps: projects, environments, config and secrets, rollouts and rollbacks, with every deployment pinned to an OCI module digest.

Open the consoleRead the Telo docs
telo.yamlExample
kind: Telo.Application
metadata:
  name: HelloApiExample
  version: 1.0.0
imports:
  Http: oci://ghcr.io/telorun/[email protected]#sha256-KuqDkp68S_hOl7nZ4WJLOyNAn2M3kmPSMwEaeBJbgSw
  Run: oci://ghcr.io/telorun/[email protected]#sha256-O1CdVvYs_O7Zj-PNQxMS3NdgWL6e8M2A0J9Wu0rTnIU
targets:
  - !ref exampleServer
ports:
  http:
    env: PORT
    protocol: tcp
    default: 8845
---
kind: Http.Server
metadata:
  name: exampleServer
port: !cel "ports.http"
openapi:
  info:
    title: Hello server
    version: 1.0.0
mounts:
  - path: /v1
    mount: !ref helloApi
# … the Http.Api routes and their handler are omitted
DeploymentExample
Environment
production
Module digest
sha256:9f3c1a…e47b
  1. queuedDeployment accepted
  2. resolvingModule pinned to its digest
  3. applyingHelm release upgraded
  4. progressingRollout observed
  5. healthyRollout complete

What Telo Cloud does

Everything between a published Telo module and a running release, with the access control and the paper trail a team needs.

  • projects

    Projects and roles

    Group apps into projects inside your organization. People and groups get a role per project: admin, deployer or viewer.

  • apps

    Apps and environments

    An app is an OCI module reference with one environment or many. Mark an environment as protected and only a project admin can change it or deploy to it.

  • config

    Config and secrets

    Set configuration and secrets per environment. Secrets are envelope-encrypted at rest and are never shown back once saved.

  • targets

    Deployment targets

    Register your own Kubernetes cluster as a target, with a credential confined to the namespaces Telo Cloud makes and the ones you allow, or through an agent that connects out. A connection test checks it before you rely on it.

  • deployments

    Rollout and rollback

    Each deployment is an immutable release pinned to a module digest. Follow the rollout as it happens, and roll back to an earlier release when you need to.

  • audit

    Audit log

    Deployments, config changes and membership changes are recorded with who made them and when, and can be read in the console.

How it works

From a manifest to a running release in three steps.

  1. Manifest

    Publish your app as a module

    Describe your backend in a Telo manifest and publish it to an OCI registry as a module.

  2. Deploy

    Deploy a pinned digest

    Register the module as an app in the console and deploy a version to an environment. Telo Cloud resolves it and pins the release to the module's digest.

  3. Run

    Run it on your cluster

    Telo Cloud rolls the release out on your cluster, reports its state until it is healthy, and can roll it back to an earlier release.

Where it runs

On your own Kubernetes cluster. Telo Cloud is the control plane; the workloads and their data stay on infrastructure you control.

Your Kubernetes cluster

available today

  • A Helm release per environment

    Each environment is its own Helm release in the namespace you chose.

  • The stock Telo kernel image

    Your app runs on the unmodified Telo kernel image, so there is no image for you to build.

  • Namespaced RBAC

    The service account Telo Cloud uses is bound to a namespaced role. Nothing it holds is cluster-scoped.

  • A connection test

    The console checks that the cluster is reachable, that the credential is accepted and that it carries the permissions a deployment needs.

Planned and not available yet: GitOps with Flux and a Linux VM agent.

Pricing

One flat price per organization. No per-seat fees, and no usage charges for apps on your own clusters.

Billing is not live yet. During the preview, every organization uses Telo Cloud free of charge and plan limits are not enforced. Nothing is charged until billing launches and you choose a paid plan.

  • Hobby

    $0per organization / month

    For personal projects and for trying Telo Cloud on your own cluster.

    Apps
    3
    Environments
    6
    Deployment targets
    1
    Members
    Unlimited
    Billing
    —
    Open the console

  • Pro

    $49per organization / month

    For teams running production apps across several clusters.

    Apps
    25
    Environments
    100
    Deployment targets
    5
    Members
    Unlimited
    Billing
    —
    Open the console

  • Enterprise

    Custom

    For organizations that need higher limits and invoiced billing.

    Apps
    Custom
    Environments
    Custom
    Deployment targets
    Custom
    Members
    Unlimited
    Billing
    Invoiced
    Talk to us

Every plan includes projects and roles, protected environments, config and encrypted secrets, rollouts and rollbacks, and the audit log.

Prices are in US dollars and exclude VAT and other taxes.

Hosting on Telo's and other providers' infrastructure is offered as tiers, listed with their limits and prices in the console.

Your manifests, your cluster, one control plane.

Open the console