How Blossom Works
Where your Apps run, how Blossom deploys them, and how it keeps them running
Blossom Cloud or Your Cloud
- Blossom Cloud: pick a Location in one of Blossom’s regions and deploy. Blossom runs the servers; you get one bill.
- Blossom BYOC (bring your own cloud): connect your cloud provider account, add a Location in one of its regions, and deploy. Your provider bills the servers; Blossom bills the platform.
Either way, your Apps deploy, scale and recover the same way.
Deploy
Blossom builds your source into an image with Buildpacks, your Dockerfile or its Static builder, or uses a prebuilt image. See Build types.
Each deploy rolls out gradually. New Containers start, pass their health checks, and only then take traffic; the old version keeps serving until they are ready. If the new version never gets healthy, the deploy stops there, the old one keeps running, and Blossom tells you why.
Keep Running
Blossom remembers what you asked to run and keeps it that way. When a Container crashes, a server fails or an operation is interrupted, Blossom notices the difference and puts it back, without you repeating the request.
- Scaling: Services scale between the minimum and maximum you set, based on CPU and memory.
- Capacity: Blossom adds Capacity when your Apps need it and retires it when they don’t, within your capacity limit.
- Problems only you can fix, like a failing health check or an expired cloud provider credential, are shown where you fix them.
See What Happened
The Web UI and CLI show the same things: health, Releases, logs, metrics, Containers, and Activity, a history of every change and recovery. Your AI agent uses the same CLI and permissions you do, and its changes appear in the same Activity.