Fleet

Backend deployment, minus the detour

From repository to running backend.

Fleet builds your container, verifies the release, and gives it a stable URL. Push again whenever you are ready.

Connect GitHubSee the three steps
Abstract light and movement behind a Fleet deployment interface
fleet-api / main
Deploying

Deployment 1842

Production release

Healthy
1

Build

42s

2

Health check

Passed

3

Release

Live

A deployment, end to end

One push. Four visible stages.

0100:00

Push received

0200:42

Image built

0300:50

Health verified

0400:51

Traffic moved

How Fleet works

Three steps. Nothing hiding between them.

The interface stays close to the deployment: repository in, verified release out.

Blue abstract texture behind the repository connection flow

GitHub connected

Repository

mondeep31/fleet

Branchmain
Environment ready

Step 1: Connect

Authorize GitHub once, choose the repository and branch, then add the environment your service needs.

Amber abstract texture behind the Fleet build sequence

Building release

commit a83f9c2

Dockerfile detected01
Image created02
Port 3000 responding03

Build completed in 42s

Step 2: Build

Fleet detects the Dockerfile, streams every build step, and checks the container before release.

Green light behind the live release routing diagram
GitHub push
Custom domain

Production is healthy

Verified before traffic moved

api.fleet.run

Step 3: Go live

Traffic moves only after the health check passes. Your stable URL remains unchanged on the next push.

Continuous delivery

Push code. Keep serving.

Fleet builds every push in isolation. The existing release stays online until its replacement passes the health check.

0s

planned downtime

1

stable production URL

Release history

main

#1840

a8d109f

Live

12:42
#1841

45c2a11

Superseded

14:06
#1842

a83f9c2

Live

14:31

Push-to-deploy

GitHub webhooks start the build. Commit and release stay linked.

Your domain

Verify DNS in Fleet and keep the same route through every release.

After launch

The controls you actually need.

01

Build output

Watch every build step as it happens, from dependency install to image creation.

02

Runtime logs

Inspect live application output without reaching for a separate logging service.

03

Configuration

Keep environment variables and deployment settings with the service they belong to.

04

Stable routing

Preserve one production URL across releases, then attach your own domain.

Pricing

Start free. Scale when the service does.

GitHub deployment, logs, environment variables, stable URLs, CI/CD, and custom domains are included on every plan.

Free

256 MB RAM · 0.25 core · 1 PROJECT

$0forever
Deploy free

Pro

1 GB RAM · 1 core · 5 PROJECTS

$9per month
Coming soon

Team

4 GB RAM · 4 cores · Unlimited PROJECTS

$29per month
Coming soon
No credit cardCustom domainsZero-downtime rollouts