Everything you need to know about Blossom.
Blossom lets you deploy apps into your own Cloud Provider Account with a Heroku-like workflow, managed reliability, and clear infrastructure ownership.
You connect your Cloud Provider like Digital Ocean, Hetzner, AWS, etc, and we’ll handle building and deploying the app.
Yes, but with a key difference: Blossom gives you more control over your infrastructure while maintaining the ease of use of these platforms.
Unlike platforms where infrastructure ownership is hidden, Blossom BYOC runs Product-managed infrastructure in your Cloud Provider Account. This means:
Yes, you’ll need to connect your own cloud provider account (like Digital Ocean, Hetzner, AWS, etc). This is what allows us to give you more control and lower costs.
We’ll guide you through the process of connecting your account, and you can use any of our supported providers.
We support major cloud providers including AWS, Digital Ocean, Hetzner, Linode, Vultr, Azure, and Google Cloud Platform. Each provider is integrated with our platform for seamless release and management.
Security is our top priority. We follow industry-standard practices, including encrypted TLS/SSL connections and secure credential management. For Blossom-managed VPC networks, we take a security-by-default approach—provisioning managed firewalls even when the cloud provider defaults to more permissive settings.
Blossom charges for the provisioned CPU and memory used by running workloads, not per Server. Scaling an App Service to zero ends that Service’s Blossom charge. BYOC persistent storage, network egress, and object storage currently have no separate Blossom charge.
Your cloud provider bills its infrastructure separately. Blossom previews the charge that will appear on your Blossom bill and clearly identifies provider-billed capacity without estimating that separate bill. See the current rates and examples on our pricing page.
Your cloud provider supplies and bills the infrastructure in your account. Blossom operates the application platform across it: releases, monitoring, automatic recovery, autoscaling, managed data workflows, and infrastructure automation without requiring a Kubernetes control plane in your cloud account.
Keeping the bills separate makes each one easier to audit. Blossom previews only the charge that will appear on your Blossom bill. For BYOC infrastructure, Blossom clearly states when your cloud provider will bill capacity directly without presenting an estimate that could be mistaken for part of the Blossom invoice.
Blossom uses standard pricing from the start. Your Organization’s billing cycle begins when you subscribe, and active allocations are prorated by time.
Blossom shows the capacity and published rate before approval. Returning eligible capacity to zero stops its allocation charge without deleting your configuration or billing history.