Laravel hosting on your own server
Start from the official Laravel skeleton in one click, or deploy your own repository as a Git release. The environment file, database, scheduler and queue worker are set up, so the app is ready for production.
- One-click Laravel on the current major version
- Scheduler every minute and a queue worker from the first day
- Artisan commands run from the site's Deploy pane
On your own server
You pay your provider for the server, as before. Zefily keeps PHP, the database, the queue, the scheduler and the certificates in order. Your Laravel app keeps running on the server if you stop using Zefily.
Runs the stacks you already use
- WordPress
- PHP
- Laravel
- Node.js
- Python
- Docker
- Supabase
- Ghost
- Nextcloud
- n8n
- Uptime Kuma
- Grafana
- Gitea
- Metabase
- PocketBase
- Meilisearch
- Vaultwarden
- Adminer
- Joomla
- Moodle
- PrestaShop
- Mautic
- Craft CMS
- Statamic
- Static sites
- CakePHP
- CodeIgniter
- Symfony
- Yii
- Drupal
- WooCommerce
- Express
- NestJS
- Nuxt
- Next.js
- Strapi
- Django
- Flask
- FastAPI
- Hetzner
- DigitalOcean
- Vultr
- Linode
What you get
Releases with migrations
Each deploy becomes a release. Set php artisan migrate as the release command, and the new code goes live only after it has run.
Production environment file
A production .env with a fresh APP_KEY, debug off, daily logs, and database-backed sessions, cache and queues.
Scheduler and queue worker
The scheduler runs every minute and one queue worker processes jobs. Both are managed background processes, so you write no cron or supervisor files.
Octane on FrankenPHP
Run Laravel Octane on FrankenPHP to keep the application booted between requests.
Valkey object cache
Turn on the object cache to use Valkey for cache and sessions, with CACHE_STORE set to redis.
Reverb WebSockets
Add a location for Laravel Reverb on the nginx pane and run Reverb as a daemon for live features.
How it works
-
1
Connect a server
Add a server with the installer, or create one at a cloud provider from the panel.
-
2
Create the Laravel site
Choose the one-click Laravel app or a Git repository, then pick the database and the domain.
-
3
Go live
The first release is served from public/ over HTTPS on your domain. Later pushes deploy on their own.
Pricing
Plans, limits and prices are on the pricing page. Start with the plan that fits your sites and change it later.
See plans →Questions
Which database can Laravel use?
MariaDB or PostgreSQL when the server has one installed. For small apps, SQLite in the shared directory is an option.
Can I run Artisan commands from the panel?
Yes. Run them from the Deploy pane, for example cache:clear or migrate:status, and read storage/logs in the Logs pane.
How do pushes deploy?
Connect the repository. A push from GitHub or GitLab triggers a deploy through a webhook. Repositories connected through the GitHub App need no webhook.
Do I need Octane?
Not for most apps. Octane keeps the framework booted between requests, which helps busy applications. The standard PHP setup works for most sites.
Can I run Reverb for WebSockets?
Yes. Add a location for Reverb on the nginx pane and run it as a daemon.