Your infrastructure application platform

Your apps.
Your infra.
Spawned.

Spawner deploys and operates your applications on infrastructure you own. Bring a server or let Spawner provision one; it builds the private network, Kubernetes platform, releases, traffic, and regional capacity around your apps.

BRING OR PROVISIONSPAWNOPERATE
A rotating Spawner cube cycles through Kubernetes, Helm, Terraform, and Cloudflare.
The CLI cube, liveYour app → Your infra
your-project
$ spawner
✓ App       Compose + Dockerfile discovered
✓ Capacity  Hetzner provisioned · BYO supported
✓ Platform  Headscale · k3s · Helm · Cloudflare
LIVE https://web.example.com
The outcome

Managed-platform speed.
Infrastructure you own.

You give Spawner an application and capacity. It turns them into a working platform, deploys the app, exposes it safely, and keeps the system operable.

What Spawner solves

From raw capacity
to a running app.

Spawner owns the work between “I have code and servers” and “my application is live, private where needed, scalable, and recoverable.”

  1. 01
    BYO SSH · Hetzner · provider registry

    Bring or provision

    Use an existing Linux server or ask a registered provisioner to create capacity. Spawner keeps the same machine contract either way.

  2. 02
    Terraform · Headscale · dog · k3s

    Build the platform

    Provision machines, connect them through a private tailnet, install the cluster, and enroll the operator that owns Day-2 work.

  3. 03
    Compose · Dockerfile · BuildKit · Helm

    Spawn the app

    Discover the application, build immutable images, deploy services and state, then wait for real readiness before continuing.

  4. 04
    Cloudflare · regions · runtime API

    Run it

    Route healthy traffic, balance regions, scale or roll back releases, and create on-demand game servers or other runtime instances programmatically.

The platform Spawner assembles

Not just provisioning.
Not just deployment.

Spawner connects compute, networking, orchestration, application delivery, public traffic, and operations into one owned platform.

01BYO · PROVISION

Bring your own or provision

Attach an SSH-accessible server, provision Hetzner capacity, or extend the typed provider registry without changing the platform lifecycle.

02HEADSCALE · REGIONS

Private multi-machine network

Headscale and Tailscale connect control planes and workers across regions without exposing the cluster network to the public internet.

03K3S · HELM · DOG

Operated Kubernetes

Spawner installs k3s, deploys through Helm, verifies readiness, and routes Day-2 health, logs, repair, scale, and cleanup through dog.

04BUILD · DEPLOY · PROMOTE

Application delivery

Compose and Dockerfiles become reviewed apps, BuildKit produces immutable images, and CI promotes the same digest through environments.

05TUNNEL · LOAD BALANCE

Domains and traffic

Cloudflare tunnels, DNS, Access policy, regional pools, load balancers, and health probes expose only the services you select.

06API · TCP · UDP · HTTP

Programmable runtimes

Create leased, release-pinned runtime instances for game servers, chatrooms, agent sessions, previews, and other on-demand workloads.

07APPS · WORKERS · PVC

Services and state

Run web apps, workers, cron jobs, and StatefulSets with explicit secrets, configs, persistent volumes, quotas, and service-to-service policy.

08DAY-2 · RECOVERY

Operations and recovery

Saved plans, signed approvals, immutable releases, scale, rollback, federation capacity, and encrypted state recovery keep ownership inspectable.

The simple definition

Spawner spawns your app
into your infrastructure.

It can create the capacity or use what you already have. Either way, you get one operated application platform instead of assembling Terraform, private networking, Kubernetes, releases, tunnels, load balancing, and recovery by hand.

OPEN SOURCE · PKCE · VERIFIED PUBLISHER

This domain is the official public identity of the Spawner CLI. OAuth credentials remain in the operating system credential store; no client secret is distributed.