Developer hosting
Git Deployment on SteboHost
Repository-driven deployment workflow — push to deploy, with build logs and rollback.
- Git push to deploy
- Build & deploy logs
- Health checks
- One-click rollback
Git Deployment
Git deployment is a repository-driven workflow where every push to your configured branch triggers an automated build and release. Instead of manually uploading files or running deploy scripts, you push code to GitHub, GitLab or Bitbucket, and SteboHost handles the build, test and release pipeline. Every release is versioned, build logs stream in real time, and one-click rollback returns you to any previous release without a rebuild. This deployment method is for any team that uses Git for version control — which is essentially every modern development team. It supports continuous deployment where pushes to main go straight to production, staging workflows where feature branches create isolated test environments, and team collaboration where multiple developers share deployment history and logs. What makes SteboHost different is the transparency and safety of the pipeline. Build logs show every step — dependency install, compilation, migrations, asset processing — with errors highlighted and actionable. If a build fails, production is untouched; the previous release keeps serving. Before every migration, an automatic snapshot of your database is taken, so a bad migration is a restore, not a recovery project. Staging environments get their own database — a clone of production with personally identifiable information sanitised by configurable rules. Deploy hooks let you notify Slack, trigger external services or run post-deploy tasks, and deployment history includes commit messages, diffs and the exact build output, so you always know what changed and why.
What is included
Everything you need to run and deploy
Each feature is part of the product — not an add-on or an upsell.
GitHub-connected deployment (GitHub, GitLab, Bitbucket)
Push-to-deploy workflow on your configured branch
Build and deploy logs in real time
One-click rollback to any previous release
Staging environments with their own database
Automatic database snapshot before every migration
Environment variables per environment
Deploy hooks for notifications and integrations
Deployment history with diff and commit messages
Manual deploy trigger via portal or webhook
Build failure protection — production stays on previous release
Atomic releases with zero-downtime switch
Why Git Deployment
Why developers choose SteboHost for git deployment
Specific reasons — not generic marketing claims.
Zero-downtime atomic releases
The new release is built and tested before traffic switches over. The reverse proxy switches in a single atomic operation, so no request hits a half-deployed application. If the new release fails, the proxy switches back instantly.
Build failure protection
If a build fails, the deployment stops and production continues running the previous release. No partial deploys, no downtime, no broken state. The build log shows the exact error so you can fix and push again.
Branch-based staging with real data
Push to a staging branch and get an isolated preview environment with its own database — a clone of the parent database with personally identifiable information sanitised by configurable rules. You can test changes end-to-end against realistic data without exposing customer records. Preview environments are created and cleaned up automatically.
Transparent deployment history
Every deployment is recorded with the commit hash, commit message, author, build log and diff. You can see exactly what changed in each release and who pushed it, making incident response and audit trails straightforward.
Deploy hooks and notifications
Configure webhooks to notify Slack, trigger external services or run post-deploy tasks. Deploy notifications keep your team informed without anyone checking the portal manually. Manual deploys can be triggered from the portal or via webhook URL.
How it works
From repository to production in five steps
The deployment workflow, end to end — visible, automated and reversible.
Connect your repository
Link your GitHub, GitLab or Bitbucket repository from the portal. We install a webhook on your repository so every push to the configured branch notifies SteboHost and triggers a build. No manual deploy steps are needed.
Build runs automatically
On every push, the build pipeline runs: dependency install, compilation, migrations, asset processing. A snapshot of your database is taken before migrations run, so a failed migration is a one-click restore. Build logs stream in real time in the portal with errors highlighted for quick diagnosis.
Release is versioned
A successful build creates a versioned release with the commit hash, commit message, author and timestamp. The release is stored on disk alongside previous releases, ready for instant rollback if needed.
Traffic switches atomically
The reverse proxy switches traffic to the new release in a single atomic operation. No request hits a half-deployed application. The switch is instant and zero-downtime, and the old release is retained for rollback.
Rollback if needed
If the new release causes errors, click rollback in the portal. The proxy switches back to the previous release immediately — no rebuild, no waiting. The rollback is logged in the deployment history with the reason and timestamp.
Use cases
What people build with Git Deployment
Common workloads our customers run on this stack.
Continuous deployment
Push to main triggers a build and release to production — no manual steps. Every commit that passes the build goes live automatically, reducing the gap between development and deployment. Deploy hooks can notify your team or trigger smoke tests after each release.
Staging workflows
Push to a staging branch to create an isolated preview environment with its own database — a clone of production with personally identifiable information sanitised by configurable rules. Test changes end-to-end against realistic data before merging to production. Preview environments are created automatically and cleaned up when the branch is deleted.
Team collaboration
Multiple developers pushing to the same repository share a single deployment history and log stream. Every deployment records who pushed, what changed and whether the build succeeded, making it easy to trace releases back to specific commits and authors.
Rollback safety
Every deployment is versioned and retained on disk. Roll back instantly to any previous release if a deploy breaks production — no rebuild, no waiting. The rollback is logged with the reason, so your team has a full audit trail of every change.
Developer plans
Transparent pricing, honest limits
Every plan publishes its exact resources. No burst limits buried in a footnote.
Dev Launch
For side projects and portfolios
KES 19,188 /year
- 3 applications
- 10 GB storage
- 500 build minutes
- 2 environments
- Git deploy
- SSL included
Dev Build
For production apps with CI/CD
KES 35,988 /year
- 10 applications
- 30 GB storage
- 2,000 build minutes
- 5 environments
- Git deploy
- SSL included
- Staging + production
- Priority support
Dev Team
For teams and agencies
KES 71,988 /year
- 50 applications
- 100 GB storage
- 10,000 build minutes
- 20 environments
- Git deploy
- SSL included
- Staging + production
- Priority support
- Team collaboration
Performance
Built for speed, not benchmarks
Concrete performance guarantees — not vague promises.
Pre-migration snapshots
An automatic snapshot of your database is taken before every migration runs. If a migration corrupts data or the release misbehaves, restoring the snapshot is a one-click operation in the portal — no backup archaeology, no downtime beyond the restore itself.
Parallel build pipeline
Build steps that can run in parallel — dependency install, asset compilation, test suites — are executed concurrently where possible. This reduces total build time and gets your code to production faster, especially for large projects.
Instant rollback
Rollback switches the proxy back to a previous release that is already built and on disk. There is no rebuild, no re-install and no waiting. The previous release starts serving immediately, minimising downtime during incident response.
Build cache reuse
Dependency caches from previous builds are reused when lockfiles have not changed. This skips redundant dependency downloads and installations, reducing build time significantly for projects with large dependency trees.
Security
Security is included, not optional
SSL, isolation, backups and monitoring — on every plan.
Read-only repository access
We request read-only access to your repository — we can pull code but cannot push changes or modify your repository. The webhook we install only receives push events, and no other repository permissions are required.
Encrypted environment variables
Environment variables for the build and runtime are encrypted at rest and injected at the appropriate stage. Build-time secrets and runtime secrets are separated, and neither is written to disk in plaintext or exposed in logs.
Build isolation
Each build runs in an isolated environment with its own filesystem and process space. One build cannot access another build's files, environment variables or artefacts. Build containers are destroyed after the build completes.
Webhook signature verification
Webhook payloads from GitHub, GitLab and Bitbucket are verified using the provider's signature mechanism. This prevents unauthorised deploy triggers from spoofed webhook requests, ensuring only legitimate pushes trigger builds.
Migration
Migrating to SteboHost
Move your existing application without downtime or data loss.
From any CI/CD pipeline
If you are using GitHub Actions, GitLab CI or Jenkins for deployment, you can switch to SteboHost's built-in Git deployment. Connect your repository, configure your build commands and environment variables, and push to trigger the first deploy.
From manual FTP or SSH deploys
If you are deploying by uploading files via FTP or running scripts over SSH, Git deployment replaces that workflow entirely. Push to deploy, with build logs, versioning and rollback — no more manual file transfers or guessing what is in production.
Repository reconnection
If your repository is already connected to another deployment service, connecting it to SteboHost does not interfere. You can run both in parallel during migration, then switch DNS when you are confident the SteboHost deployment works.
Free migration support
Contact support@stebohost.com or call +254 703 610 464 for migration help at no extra cost. We assist with repository connection, build configuration, environment variable setup and DNS cutover, and verify your first deploy works end-to-end.
Git Deployment FAQ
Git Deployment questions, answered
The details that matter when choosing a hosting provider.
Other stacks
Explore more deployment targets
One workflow, six deployment targets. Connect your repo and ship.
Ready to deploy your git deployment app?
Tell us your stack and we will get you from repository to production — usually within a day.