Skip to content

A real platform for your own Kubernetes clusters.

Anyport brings push to deploy, a preview per pull request, managed databases, domains with HTTPS, logs, metrics and roles to the clusters you already run, or to one we run for you.

Free for three clusters you attach, with no card and no metered compute. No cluster yet? Anyport Cloud runs one for you.

curl -fsSL https://anyport.dev/cli.sh | sh -s -- --init

Or from the terminal: the CLI signs you in and connects a cluster. The quick start covers it.

01Why this one

A deploy experience, many clusters, your own compute unmetered.

A deploy experience

Push to deploy, numbered revisions, rollback, previews, managed databases, terminals, logs and metrics.

Every cluster in one organization

One set of roles and one audit log across every cluster, yours or one we run.

Your own compute, unmetered

On clusters you attach, containers, builds, storage and logs run on hardware you already pay for.

How the alternatives compare, cited from their own pricing pages.

02The product, running

Under a minute, push to serving.

A push that builds, rolls out and serves over HTTPS, and how it got there, with no YAML written at any point.

Rendered from the console's own components. Sample project, real interface.

03Who it's for

You already own the hardware.

More clusters than dashboards

Development on a laptop, staging on a box, production in two regions, one console.

You ship into customers' infrastructure

Each customer's cluster, on their network, in one console. No VPN and no kubeconfig to hold.

You repatriated, and the deploys got worse

Push to deploy, rollbacks, HTTPS, logs and metrics, back on hardware you own.

Nothing can dial in

A rack behind CGNAT is a supported setup here, because your cluster opens the connection.

04How it works

Connect a cluster, point at your code, push.

  1. Two commands, and the cluster is connected.

    01

    Connect a cluster

    One command against a cluster you run, or against a bare machine to have Anyport install k3s first. No ports opened, no credentials handed over.

  2. A repository or an image, built or pulled on your cluster.

    02

    Point Anyport at your code

    Connect a GitHub repository and Anyport builds it on your cluster from your Dockerfile. Or deploy an image you already publish.

  3. The commit you pushed, live on its own row.

    03

    Push

    Every push rolls out as a numbered revision with a URL, HTTPS on your own domain, and a one-click rollback.

  4. A pull request becomes a project on its own URL.

    04

    Open a pull request

    It gets the whole project on its own URL with its own database, and is deleted when the pull request closes.

What a preview environment is, and what it costs you →

05How it reaches your clusters

The connection only goes one way.

You install an agent that dials out and accepts nothing. No open port, no exposed API server, no kubeconfig shared with us.

No inbound ports. Your cluster opens the connection and requests travel back down it, so a machine behind NAT still serves a real domain over HTTPS.

Outbound only

One connection, opened by the agent, and none accepted.

Your credentials stay put

No kubeconfig leaves your cluster. We hold a hashed agent token.

Standard Kubernetes underneath

Ordinary objects in your cluster. Lose our control plane and your apps keep serving.

Your data stays on your hardware

Builds, logs and metrics stay on your cluster. Only opt-in gateway traffic touches us.

What the agent can do, and what data leaves →Or run the control plane in your own network

06What Anyport does today

A full platform, not a deploy button.

Everything below ships today, on every cluster you connect.

Deploying

  • Push to deploy
  • Or any image registry
  • Builds on your cluster
  • Numbered revisions
  • One timeline
  • Readable diffs
  • A preview per pull request

Scheduled and one-off work

  • Cron schedules
  • Tasks inherit the app
  • Run by hand, kept in history
  • Pre-deploy commands
  • Timeouts and retries

Traffic and domains

  • A URL on deploy
  • Your domain, certificates included
  • Ownership re-checked
  • Publish from private clusters

Databases and services

  • PostgreSQL
  • MySQL
  • MongoDB
  • ClickHouse
  • Qdrant
  • Redis
  • OpenSearch
  • RabbitMQ
  • NATS
  • Object storage
  • Mail catcher
  • Backups to your bucket
  • DATABASE_URL injected

Starting from something

  • One-click stacks
  • Save as a template
  • Duplicate across clusters

Operating it

  • Logs and metrics per app
  • A terminal into any container
  • Debug containers for distroless
  • Pause a project
  • Persistent disks
  • Configs and secrets
  • The agent updates itself

From your terminal

  • The anyport CLI
  • Browser sign-in, no tokens
  • anyport dash
  • anyport port-forward
  • anyport mcp

Teams and governance

  • Admin, developer, viewer
  • An audit log
  • Terminal access as a permission
  • One organization, every cluster

Every item, in a sentence →

07What it costs

Compute on your own clusters is never metered.

Straight to your load balancer: never counted.
Through our gateway: counted.

Free

Three clusters

Every feature, unlimited members, apps and projects. No card.

$5a month

$5 of credit back, then pay as you go

More clusters at $2 a month each, Anyport Cloud at $5 a cluster, and 100 GB of gateway traffic a month.

10 GBa month, free

The one thing counted

Gateway traffic for clusters with no public address. Your own load balancer is never counted.

How the traffic allowance works →No cluster? Anyport Cloud bills from credit →

Connect a cluster, or start one on Anyport Cloud.

A few minutes if a cluster is already running, and no machine to look after if we run it. Still weighing it? The first questions people ask are answered in one place.

Rather talk to an engineer first?

Tell us what you run and we will walk you through the first cluster. Awkward ones are the case we most want to hear about.