Deploy Laravel to production, workers and queues included
A Laravel app in production means PHP, a database, a cache, queues and a scheduler. All five are placed as blocks on the canvas and deployed from your Git repository, without YAML.
No credit card, no commitment.
Your Laravel repository
- PHP application
- Database
- Redis
- Workers
- Scheduler
- Object storage
Kubernetes, built and run by Fransys
The European cloud you chose Scaleway · OVHcloud · Hetzner · Outscale
What you have to build between the local project and production
On a developer's laptop, Laravel fits in one command. In production it needs a tuned PHP server, a backed-up database, Redis for cache and sessions, workers for the queues and a cron for the scheduler. The canvas describes this whole architecture, code included, and the platform operates it.
- 5blocks for a complete Laravel app
- 1deployment gesture: git push
- 0lines of YAML to write
The typical Laravel architecture, block by block
-
The application
Your Git repository, built and served. Domains, TLS and environment variables set inside the block.
-
The database
Managed PostgreSQL or MySQL, automatic backups. Credentials are injected into the application.
-
Redis
Cache, sessions and queues on a dedicated block, sized independently of the application.
-
The workers
Your queues run on their own resources, scaled with queue depth.
-
The scheduler
The Laravel cron runs as a scheduled task, with its own logs.
-
Storage
Files and media on S3-compatible object storage, at the same European provider.
From push to release
-
git pushThe commit lands on the main branch.
-
buildThe image is built with your Composer dependencies and compiled assets.
-
migrateMigrations run before traffic is switched over.
-
liveThe new version receives traffic. On failure, automatic rollback to the previous one.
With your agent, or by hand
With your agentexample
Deploy my Laravel app: PostgreSQL, Redis, the workers and the scheduler.
- The agent reads your repository and prepares the plan: the blocks, each with its price.
- Someone on the team approves the plan.
- The engine executes; migrations run before traffic is switched over.
By hand
- Place the blocks on the canvas: application, database, Redis, workers, scheduler.
- Connect your Git repository, set the variables in the application block.
- Push to the main branch: the release goes live.
What people ask about Laravel
How are database migrations handled?
They run automatically before traffic switches to the new version. If a migration fails, the deploy stops and the live version is untouched.
Can I use Horizon for my queues?
Yes, Horizon runs as a worker with its interface. The Redis queues sit on their own block, sized separately.
What happens to my .env file?
Its values are set in the application block, outside the repository and outside the image. Each environment has its own values.
What about Octane, or a long-running Laravel?
Supported: the application declares itself with its start command and its resources. Tell us about your setup, we look at your case together.
Your Laravel app on Fransys: where to start
See the console in demo, in your name. To cost your app, the infra plan does it line by line, machines included.
No credit card, no commitment.
Read on the blog
Heroku and Vercel too expensive: where to migrate in 2026?
Heroku with no free tier, Vercel bills spiralling: a comparison of European alternatives for startups. Migrate to managed Kubernetes without DevOps.
What does a DevOps engineer really cost in 2026? (and how to keep that spend down)
Salary, social contributions, recruitment, turnover: the real cost of a DevOps engineer in France exceeds €90,000/year. Full breakdown and alternatives for startups without DevOps.
AWS vs Fransys: what does your cloud infrastructure really cost in 2026?
A detailed AWS vs Fransys comparison on European hosting. Prices line by line, and three costed startup scenarios.