Skip to main content

Get started with Sprintsail

Sprintsail is a managed application platform. You push source code; it detects the language, builds it, runs it, and keeps it running — with managed Postgres, Redis, object storage, search, and queues available to bind to your app.

This page takes you from an empty account to a running application.

Early access

Sprintsail is currently open to a small number of teams while we run it in anger. Request access and we will onboard you directly.

What you need​

  • An account on the platform (see early access above)
  • The cf CLI, version 8 or later — install it here
  • An application you can run locally

You do not need a Dockerfile, a Kubernetes manifest, or a CI pipeline to start.

1. Sign in​

Sprintsail uses single sign-on. Your identity carries your roles with it, and every action you take — in the console or the CLI — is checked against those roles by the platform itself. There is no shared admin account.

Sign in to the console at console.sprintsail.com, or point your CLI at the API:

cf api https://api.sprintsail.com
cf login --sso

2. Get an org and a space​

An organisation is your team. A space is an environment inside it — most teams run dev, staging, and prod.

First-time users are guided through creating an org during onboarding. Once you have one, create spaces as you need them:

cf create-space prod -o acme
cf target -o acme -s prod

Orgs and spaces are real objects in the platform, not console bookkeeping. Create one in the console and the CLI sees it immediately; delete it in either place and it is gone in both.

3. Push your source​

From your application directory:

cf push orders-api

That uploads the directory, runs buildpack detection, installs dependencies, builds a runnable image, and starts it. Watch the output — detection tells you which buildpack matched.

See Deploy from source for the details, including how to push a prebuilt image instead.

4. Add a database​

Managed services come from the marketplace. Provision one, then bind it:

cf marketplace
cf create-service postgres small orders-db
cf bind-service orders-api orders-db
cf restart orders-api

Binding injects the connection details into your application's environment. Your app reads them the same way it reads any other environment variable.

See Services for what is available and how binding works.

5. Watch it run​

cf logs orders-api           # live logs
cf app orders-api            # instance count, memory, state
cf scale orders-api -i 3     # three instances

The console shows the same information — logs, per-instance CPU and memory, deployment history — because both read the same API.

What is not here yet​

We would rather tell you now than have you discover it later:

  • Custom domains are not self-service yet. Talk to us if you need one.
  • Autoscaling is not available. You set the instance count; it stays where you set it.
  • Region choice is not offered — there is one region today.

Where to go next​