From commit to deployment
Connect a repository and choose a framework preset. GitHub-connected services can deploy automatically on pushes to the configured branch. Pro also supports Dockerfile builds and prebuilt container images.
Cloud Apps
Deploy apps from Git
Cloud Apps turns a source repository into a running service. Unbroker builds your code, rolls out a revision and checks its health, with deployment history and runtime logs in the same project.
For teams shipping web applications, APIs and background workers who want to operate services without maintaining their own deployment platform.
What you can do
Operate each revision
Follow queued, building, deploying and live states. Inspect runtime logs and deployment history; Pro adds resource metrics and configurable capacity.
Preview and publish
Pro supports isolated GitHub pull request previews, custom domains and managed TLS. Closing a pull request removes its preview.
How to get started
- Create a project and add a service from your Git repository.
- Select the framework and configure the build, runtime settings and environment variables your application needs.
- Deploy, inspect the build output and wait for the health check before sending users to the service.
Pricing and plan requirements
Free supports static HTML and managed Node.js, with 2 services in 1 project and 3 deploy requests per UTC day. Each service has up to 250m CPU and 256 MiB RAM. Pro has a $25 monthly commitment and $25 of eligible usage credit per billing cycle. Prices are in USD, excluding applicable taxes. Paid app CPU and memory are billed by configured capacity while running.
See current prices and billing examples →Questions about Cloud Apps
Can I use Cloud Apps for free?
Yes, within the Free plan limits. Free applications pause after 7 days without qualifying traffic and can be resumed from Cloud. Dockerfile builds, workers, private repository credentials and custom domains require Pro.
What happens when a deployment fails its health check?
An unhealthy revision is not treated as live. Inspect build and runtime logs, correct the failure and retry the deployment.
When should I choose a server instead?
Choose a Cloud Server when your software needs operating-system packages, host-level control or a custom daemon layout. You then take responsibility for operating the machine.
Technical documentation
Use these guides for configuration details, supported options and operational limits.
Walk through a deployment with the CLI →