Developer hosting
Laravel Hosting on SteboHost
PHP with Composer, queues, cron and database — the full Laravel stack, configured and ready.
- Git push to deploy
- Build & deploy logs
- Health checks
- One-click rollback
Laravel Hosting
Laravel hosting is purpose-built infrastructure for applications running the Laravel PHP framework. Unlike generic PHP hosting, a Laravel-optimised environment includes the full toolchain the framework expects: Composer for dependency management, a queue worker process for background jobs, a cron entry for the Laravel Scheduler, and a properly configured web server for bytecode caching. SteboHost provisions all of this automatically when you create a Laravel environment, so you do not spend your first hour installing extensions or editing php.ini files. This hosting is for teams and solo developers building SaaS platforms, e-commerce sites, API backends and internal tools on Laravel 10, 11 or 12. Whether you are running a multi-tenant application with queue-backed jobs or a straightforward content site, the environment scales vertically with your plan as your traffic grows. What makes SteboHost different is that the Laravel stack is configured by engineers who run Laravel in production, not by a generic control panel. A managed MySQL or PostgreSQL database is provisioned per environment — credentials are generated, stored in the secrets vault and injected as encrypted environment variables — and Redis is provisioned alongside with a per-deployment ACL user and key prefix. Queue workers run as systemd-supervised processes that restart within one second of a crash, database migrations run as part of the build pipeline after every Git push, and an automatic database snapshot is taken before every migration. You get a Forge-like workflow without managing the underlying server yourself.
What is included
Everything you need to run and deploy
Each feature is part of the product — not an add-on or an upsell.
PHP 8.5 with Composer dependency management
Managed MySQL or PostgreSQL database provisioned per environment
Redis provisioned per deployment with ACL user and key prefix isolation
Daily automated database backups retained for 30 days
Queue workers (Redis or database) as systemd-supervised processes
Cron scheduling for Laravel Scheduler
Automatic SSL on custom domains
Git-based deployment with build logs
Environment variables encrypted at rest
One-click rollback to any previous release
Laravel Horizon and Octane (Swoole or RoadRunner) managed runtimes
Zero-downtime blue-green deployments
Why Laravel Hosting
Why developers choose SteboHost for laravel hosting
Specific reasons — not generic marketing claims.
Framework-aware configuration
We do not hand you a blank PHP server. Every Laravel environment ships with the Scheduler, systemd-supervised queue workers, a managed database and a web server already wired to the framework conventions. You deploy code, not infrastructure.
Migrations with a safety net
Database migrations run automatically after a successful build, before traffic switches to the new release — and an automatic snapshot of your database is taken before every migration. If a migration fails, the deploy halts and your previous release keeps serving requests.
Managed database and Redis
A MySQL or PostgreSQL database and a Redis ACL user are provisioned per deployment. Credentials are generated, stored in the secrets vault and injected as encrypted environment variables — no manual CREATE USER, no credentials in your repository. Redis runs as a shared instance isolated by per-deployment ACL user and key prefix, not a dedicated server.
Version flexibility
Select PHP 8.2, 8.3 or 8.5 per environment and switch without downtime. OPcache is tuned to your plan — memory, interned strings and accelerated-file limits are generated per release into a .stebohost/php.ini shipped with your code. This lets you run legacy Laravel 10 apps and new Laravel 12 projects side by side on the same account.
Honest resource limits
Every plan lists concrete CPU, memory and worker limits — no vague "unlimited" claims. cgroup memory limits are enforced per systemd unit from your plan, and you can scale workers up to your plan's memory budget with live budget usage and scaling history in the portal. Scaling is multi-worker within one server; multi-server load balancing is on the roadmap.
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 read your composer.json to detect the Laravel version and set the PHP runtime automatically. No manual buildpack configuration is needed.
Configure environment
Set your environment variables in the portal — queue connections, cache driver, mail driver and third-party API keys. Database and Redis credentials are generated and injected automatically as encrypted environment variables, and all secrets are stored in the vault, never written to disk in plaintext.
Push to deploy
Every push to your configured branch triggers a build: Composer install, asset compilation, then database migrations. Build logs stream in real time so you can watch each step or debug failures immediately.
Traffic switches over
Once the build and migrations complete, the reverse proxy switches traffic to the new release with zero downtime. The old release stays on disk for instant rollback if you spot a problem after deploy.
Rollback if needed
If a release misbehaves, click rollback in the portal. The previous release starts serving immediately — no rebuild, no waiting. The rollback is recorded in the deployment history with the reason and timestamp, and auto-rollback triggers if health checks fail after the switch.
Use cases
What people build with Laravel Hosting
Common workloads our customers run on this stack.
SaaS applications
Multi-tenant Laravel apps with queue workers, scheduled jobs and database-heavy workloads. Each tenant can have isolated databases or shared tables with tenant scoping, and queue workers handle background tasks like billing, notifications and report generation.
E-commerce
Laravel Forge-style deployment for Magento, WooCommerce or custom Laravel shops. The queue system handles order processing, payment webhooks and email confirmations, while PHP bytecode caching keeps page rendering fast under traffic spikes.
API backends
RESTful and GraphQL APIs with CORS and rate limiting. Laravel Sanctum or Passport handles authentication, and the queue workers process webhook deliveries and background data syncs without blocking request responses.
Internal tools
Admin dashboards, reporting tools and internal business applications. Filament and Nova panels run natively, and the cron scheduler handles nightly report generation, data imports and cleanup tasks without a separate job runner.
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.
Blue-green deployments
Every release is built and health-checked before traffic switches over in a single atomic operation. If the new release fails its health checks, the proxy switches back automatically — your visitors never see a half-deployed application.
OPcache tuned to your plan
PHP OPcache settings — memory, interned strings buffer and accelerated-file limits — are scaled to your plan and generated per release into a .stebohost/php.ini that ships with your code. Larger plans get proportionally more opcode cache, so bytecode caching never becomes your bottleneck under traffic spikes.
CDN caching for static assets
Fingerprinted static assets — compiled CSS, JavaScript and images — are served through the built-in CDN cache with immutable headers, so browsers cache them long-term without revalidation. The cache is purged automatically on every deploy, so new asset hashes are never served stale. For DDoS absorption at the network edge, put Cloudflare in front of your domain.
Logs and metrics in the portal
Application logs stream from journald with level filters and keyword search, and CPU and memory metrics are collected every minute and charted in the portal. A health endpoint is polled every 60 seconds, and auto-rollback can restore the previous release if health checks fail after the switch.
Security
Security is included, not optional
SSL, isolation, backups and monitoring — on every plan.
Automatic SSL renewal
Let's Encrypt certificates are provisioned on every custom domain and renewed automatically before expiry. No manual renewal steps, no expired certificate outages. Wildcard certificates are available on Pro plans.
Web application firewall with the OWASP Core Rule Set
The built-in web application firewall runs the OWASP Core Rule Set with SQL injection, XSS and brute-force protection, in detection or prevention mode as you choose. Add per-deployment custom rules from the portal and review every blocked request in the firewall log. For DDoS absorption at the network edge, route your domain through Cloudflare in front of the platform firewall.
Dependency scanning and SBOM
During the build, your Composer dependencies are scanned against known vulnerability databases, and a CycloneDX software bill of materials is generated for every release so you always know exactly what ships to production.
Environment isolation
Each environment runs in its own container with isolated filesystem and process space. Environment variables are encrypted at rest and never exposed in logs, error pages or support tickets, and database credentials live only in the secrets vault.
Migration
Migrating to SteboHost
Move your existing application without downtime or data loss.
From Forge or Vapor
If you are moving from Laravel Forge or Vapor, point your Git repository at SteboHost and re-enter your environment variables. Your composer.json, migrations and queue configuration work without changes — database and Redis credentials are regenerated and injected for you.
Import your existing database
Bring your current database with you: upload MySQL dump files (.sql or .sql.gz) or PostgreSQL custom-format dumps (.dump) through the portal, up to your plan's import size limit. The import job restores into your managed database, so your data is live before the DNS cutover.
Preview deployments with real data
Before cutting over, push a feature branch to get an isolated preview deployment with its own URL and its own database — a clone of the parent database with personally identifiable information sanitised by configurable rules. Validate the migration against realistic data without exposing customer records.
Free migration support
Contact support@stebohost.com or call +254 703 610 464 and our team will assist with your migration at no extra cost. We handle the technical steps and verify everything works before you cancel your old provider.
Laravel Hosting FAQ
Laravel Hosting 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 laravel hosting app?
Tell us your stack and we will get you from repository to production — usually within a day.