Automation & CI/CD: Deploy from GitHub, GitLab, or Your Pipeline
Push code, trigger deploys, and roll back to an earlier release from your existing toolchain or the platform API.
Push to GitHub, GitLab, or Bitbucket. The platform auto-deploys on commit or on a schedule you set.
Duplicate your full topology — app nodes, databases, load balancers, and config — to staging for safe testing.
Switch runtime versions from the dashboard. The platform updates container layers without rebuilding from scratch, and your custom files survive the redeploy.
Deployment Manager tracks every release by name, date, and settings so you can redeploy or roll back any version.
Deploy from the CI/CD platform you already use
Deploy to App Hosting from any pipeline that can call an API or run an SSH command. Use personal access tokens with scoped permissions and expiration dates instead of hard-coding passwords into scripts.
Push code and let the platform handle the rest
Branch-to-environment mapping
Map main to production and staging to pre-production. Trigger deploys by webhook or scheduled repo checks. Your CI system handles builds, and App Hosting handles the rollout. If a release fails, redeploy a previous version from Deployment Manager.
Archive and artifact uploads
Upload a local archive (ZIP, WAR, JAR) or point the platform at a remote URL when your CI pipeline publishes artifacts to S3 or Artifactory. Build nodes compile and package the artifact before deployment. Traffic switches to the new build atomically with no downtime, and Deployment Manager keeps a versioned inventory so you can redeploy an earlier release.
Pre/post-deploy hooks
Run custom steps before and after each deployment, including database schema migrations, smoke tests, cache warming, or team notifications.
Need a starting point? Browse the Marketplace for ready-made stacks, then size your environment with the Pricing Calculator.
Define your stack as code and automate every lifecycle event
Define environments in JSON manifests and automate deploys, scaling events, and recovery steps with Cloud Scripting.
Ship your stack as code
Declare your environment’s architecture, scaling triggers, and resource limits in a JSON manifest, then deploy the same setup to staging and production from one file. Set environment variables and edit config files from the dashboard or API without SSH. Package the manifest as a one-click installer when you want repeatable provisioning.
Event-driven lifecycle automation
Run event hooks on deploy, scale-out, or node failure to update config, run health checks, or send alerts. Write rules in Cloud Scripting and attach them to scaling events, deployments, or other environment changes.
Platform API and CLI
- Create environments, trigger deployments, and clone staging from production via API or CLI
- SSH into running containers for live debugging
- Authenticate with personal access tokens scoped to specific API methods, with configurable expiry
- Issue separate tokens per workflow or team member — grant deploy-only access without sharing account credentials
Connect your repo and deploy today
14 days free with no credit card required.
Common Questions
Can I roll back to a previous deployment?
Yes. The Deployment Manager keeps a versioned inventory of every release. Select any previous build from the dashboard or API and redeploy it — no git reset or manual rollback required. The old environment stays live until the new version is ready.
How do webhooks trigger automatic deployments?
Add a platform-generated webhook URL to your GitHub, GitLab, or Bitbucket repository. Every push to the mapped branch fires the webhook and queues a deploy. You can also configure scheduled repo checks that pull and deploy whenever the source changes — no webhook required.
How are API tokens scoped?
Personal access tokens can be restricted to specific API methods (for example, deploy-only) and given a configurable expiry. Issue a separate token per workflow or team member — no need to share account credentials or grant permissions beyond what the task requires.
Does App Hosting deploy with zero downtime?
Yes. App Hosting uses atomic deploys: the new build is prepared on platform build nodes, then traffic switches to the new version. The previous environment stays live until the cutover completes. Pre- and post-deploy hooks run inside the container before traffic switches, so migrations and smoke tests run before any user sees the new release.
No matching questions found.
Start your 14-day free trial
Deploy in minutes with managed autoscaling and clustering built in.
No credit card required.