Features Access Docs
Open console
Early access · managed Kubernetes, without the cluster

Your code is running.
You never opened a Dockerfile.

Sprintsail is a managed application platform. Point it at a directory of source: it works out the language, installs the dependencies, builds it, starts it, and keeps it running. Attach Postgres, Redis, object storage, search, or a queue and the credentials land in the app’s environment. No cluster to provision, no YAML to maintain, no pipeline to assemble first.

THE CORE WORKFLOW

One command. Source to running.

One command uploads your directory, works out the language, builds an image, and starts it. No Dockerfile to write and no pipeline to assemble first. Compatibility note: the client is the standard cf CLI, so a team that already has it installed has nothing new to install.

orders-api — bash

FEATURES

The things an app needs. Already wired up.

🚀

From source to running app

The platform works out what the app is, installs its dependencies, and produces a runnable image it then starts. Node, Python, Go, Java, Ruby, .NET — or bring your own image. No Dockerfile required.

🛒

Services, self-service

Postgres, Redis, object storage, search, and queues are one request away. Provisioning happens for you, and binding puts the credentials into your app environment as variables. Teardown is as clean as creation — nothing orphaned, nothing left running.

🧭

No cluster to run

Nothing to provision, size, upgrade, or patch. Capacity, node health, certificates, routing, and platform upgrades are ours. You get somewhere to push and a place to watch it run; the Kubernetes underneath is never something you open.

📊

Logs and real metrics

Live application logs and per-instance CPU and memory, read from the running instances rather than a cached summary. A single sick instance is visible instead of averaged away.

🔐

Permissions you inherit

Every action runs as you. Your SSO identity carries its org and space roles into each request and the engine enforces them per call — the console can never do more on your behalf than you can do yourself.

🗂

Workspaces per environment

A workspace for the team, and separate environments inside it for dev, staging, and prod. Create one in the console and it is there in the terminal in the same breath; delete it in either place and it is gone from both.

CLI-FIRST

Console or terminal. Same platform.

Connect
cf api https://api.sprintsail.comcf login --ssocf target -o acme -s prod
Deploy
cf push orders-apicf appscf app orders-api
Operate
cf logs orders-apicf scale orders-api -i 3 -m 1Gcf set-env orders-api KEY value
Services
cf marketplacecf create-service postgres small orders-dbcf bind-service orders-api orders-db

ACCESS

Early access, deliberately small.

Sprintsail is open to a small number of teams while we run it in anger. We would rather support a handful of applications properly than ship a signup button and a queue of tickets.

Early access

Talk to us

Bring an application you actually care about. We onboard you, you push, and we stay on the other end of the line while you do it.

  • Self-service workspaces, environments, and app deploys
  • Postgres, Redis, object storage, OpenSearch, queues
  • Live logs, per-instance metrics, and scaling
  • Console and cf CLI against the same API
  • Direct access to the engineers who operate it
Request access

Inside your boundary

Drydock

If the platform needs to live inside your compliance boundary rather than ours, that is Drydock — the same engine, deployed single-tenant in your environment.

  • Single-tenant, inside your boundary
  • The engine Sprintsail itself runs on
  • The same platform — no rewrite to move
  • Operated by the team that built it
See Drydock

Bring one app. Push it today.

Early access is open to a small number of teams. Tell us what you want to run and we will get you onboarded.

Request access →