---
title: About Blossom
url: "/docs/intro/about/"
canonical_url: https://docs.blossom88.com/docs/intro/about/
markdown_url: https://docs.blossom88.com/docs/intro/about.md
summary: Why teams run production Apps on Blossom, and what makes it different
categories:
- introduction
- about
---

# About Blossom

## Production Apps Without A Platform Team

[Blossom](https://app.blossom88.com) gives a small team what a platform team
gives a large one. Your Apps deploy safely, scale with demand, recover on their
own, and show you what happened. You keep your attention on the App.

## Why Teams Choose Blossom

| You want | Blossom gives you |
|---|---|
| Deploys you can trust | Every Release passes its health checks before it takes traffic; one step rolls it back |
| Apps that stay up | Blossom restarts what fails, replaces lost Servers and moves your data with them |
| Room to grow, no surprise bills | Set one capacity limit for the Account. Capacity grows with your Apps inside it and shrinks when demand drops |
| Clear answers | Logs, metrics, health and Activity sit on the App they explain |
| An AI agent that can operate it | One CLI and an MCP server let your agent deploy, diagnose and fix |
| Your cloud or ours | Blossom Cloud, or Blossom BYOC (bring your own cloud) in your own provider account, with the same workflow |

## What Makes It Different

**It stays responsible after the deploy.** Blossom remembers what you asked
for and keeps working until what runs matches it, even after an interruption.
It does not deploy an App and walk away.

**Your Servers are yours alone.** Every Server runs one Account's workloads,
never a neighbor's. Isolation comes from the infrastructure, not just from
software boundaries.

**People and agents use the same product.** The web UI, the
[CLI](/docs/blossom-cli/) and your
[AI agent](/docs/ai-agents/) run the same commands with the same
safeguards. Destructive changes always ask first.

**Simple to start, deep when you need it.** The UI covers the common path. The
CLI and API reach every setting.

**No Kubernetes underneath.** Blossom runs a lightweight Blossom Agent on each
Server it manages. The Agent starts your Containers, checks their health and
reports back. Blossom decides what should run where. There is no cluster for
you to operate, upgrade or debug.

## Who It's For

Blossom fits teams running production web Apps, workers, scheduled Jobs and
their databases. Teams that need custom schedulers or low-level cluster
control may prefer Kubernetes; see [Comparisons](/docs/comparisons/).

## Who Builds It

Blossom is built by Tung Nguyen, a former AWS Container Hero whose deployment
tools are used by thousands of developers. Read [the founder's story](/docs/intro/founder/).

## Next Steps

- **[Deploy with the CLI](/learn/prompt-and-deploy/)**: deploy from your repository
- **[How Blossom Works](/docs/intro/how-it-works/)**: releases, scaling and recovery
- **[Quickstarts](/docs/quickstarts/)**: a working example in minutes