Deploy Laravel

Deploy Laravel with Wodby’s managed Laravel stack. Keep web, queue, cache, and database services organized while giving your team a repeatable way to ship and scale Laravel applications.

Deploy Laravel faster with a managed stack

Start from a Laravel stack designed for Kubernetes instead of assembling runtime services, build steps, and infrastructure settings from scratch.

Run web, workers, and supporting services cleanly

Use a managed stack with clearer service boundaries, predictable environments, and simpler scaling.

Keep releases and operations in one workflow

Use built-in deployment, backups, SSL, and environment management so Laravel teams can spend less time on infrastructure coordination.

Build and release

What a Laravel deployment does on Wodby

A Laravel deployment builds two images from one repository: Nginx receives only the document root, while code, vendor packages, and the environment file stay in the PHP image. Migrations run after every deployment.

Front-end assets go to the docroot

Nothing but the document root, public unless you change it, is copied into the Nginx image. Front-end build output has to land there during the build for Nginx to serve it.

Do not commit an environment file

With no environment file in the repository, the image writes one from the PHP service's variables when the container starts. A committed file is left untouched, and then Wodby generates nothing.

The app key is generated

Wodby creates the application key and lists it among the tokens of the PHP app service. Debug mode is enabled in development environments and disabled in all others.

No storage link in the build

At start, the public storage directories are turned into links to the shared files volume. That stands in for the artisan storage link command, which should stay out of your build.

The boilerplate brings a pipeline

The Laravel boilerplate comes with a Wodby pipeline file and is available only for PHP versions the boilerplate supports. The Laravel PHP service has no development workspace.

Read the Laravel stack guide for setup steps, settings, and limits.

Bring an existing application

Plan your Laravel migration with your agent

Give your coding agent access to your repository and connect Wodby through MCP. Ask it to map your app to maintained services and flag what needs to change before deploying.

Review the plan first, then approve an isolated staging deployment. Production data transfer and cutover need separate approval. MCP access does not itself grant access to your repository.

Laravel migration planning prompt
Load Wodby’s migration guidance. Inspect this Laravel application repository and propose a Wodby deployment plan. Identify the runtime, database, background jobs, persistent files, and required secret names without revealing values. List missing information and plan an isolated staging deployment. Do not create resources, transfer production data, change DNS, or deploy anything yet.

A modern deployment model for Laravel

Laravel teams benefit from a clean way to separate application services, manage scaling, and standardize environments across staging and production.

Wodby turns that into a managed Laravel workflow on top of managed and self-hosted Kubernetes foundations, so you can ship API backends, web applications, and worker-heavy projects without hand-building the stack around them.

A practical fit for Laravel workloads

  • Separate web application, queue workers, cache, and database layers more cleanly.
  • Scale application services for traffic growth and worker capacity independently.
  • Keep environment configuration and deployment flow consistent across projects.
  • Reduce custom work around certificates, backups, releases, and infrastructure updates.

What you get with Wodby

  • Managed Laravel stack for modern container-based deployments
  • Built-in CI/CD with image builds, deployment history, and rollback attempts
  • Controlled automatic updates for stack services, app environments, and infrastructure
  • Automated backups and imports for safer releases and migrations
  • Managed routes, endpoints, and domain setup
  • App service controls for settings, resources, links, volumes, actions, and terminal access
  • Open, portable infrastructure via Wodby’s platform model

How Laravel deployment works on Wodby

  1. 1

    Choose the infrastructure model that fits: managed Kubernetes from your preferred provider or a self-hosted Kubernetes setup on your own servers for budget hosting.

  2. 2

    Create a new app from the Laravel stack and connect your repository.

  3. 3

    Configure services, domains, environment variables, persistent volumes, and databases.

  4. 4

    Deploy changes through the built-in CI/CD workflow and scale application services as needed.


Read more about stack management in our documentation.

Suitable for SaaS teams, agencies, and custom app development

If you build Laravel apps that need predictable deployments, cleaner scaling, and shared operational standards across environments, this setup fits that model well.

Wodby gives Laravel teams a managed stack without forcing them to maintain a custom platform around every application, while still benefiting from Kubernetes as the underlying standard.

Still choosing where to run it? Compare the options on the Laravel hosting page.

Start deploying

Want to launch Laravel with less setup overhead?

Start with Wodby's managed Laravel stack, connect your repo, and handle deployments, environments, and operations in one place.

Stack-specific feature

Keep local Laravel environments consistent with Docker

Use Wodby’s Docker4Laravel project to spin up a consistent local Laravel environment with Docker Compose before you deploy to Wodby. It gives teams a repeatable setup for local development across Linux, macOS, and Windows.

That creates a cleaner path from local builds to managed deployments: develop against a containerized Laravel stack locally, then move to Wodby for production infrastructure, CI/CD, backups, certificates, and scaling.

Hosting options

Run your apps where it suits you

In your own cloud account, on a server you already rent, or on Wodby Cloud. The stacks and the deployment workflow are the same on all three, and Wodby maintains the cluster.

Lowest cost

Kubernetes on your own server

Use a dedicated server or VM you already rent, from Hetzner, OVH, or any other host. Wodby installs Kubernetes on it, keeps it up to date, and deploys your apps.

  • No managed control plane to pay for
  • One command installs Kubernetes on the server
  • Join more servers as worker nodes when you need capacity
  • Operating system updates install when you choose
Explore self-hosted Kubernetes

We handle everything

Wodby Cloud

Deploy without a cloud account or a server of your own. Wodby creates and operates the cluster, and you pay for the nodes and storage you run.

  • Nothing to connect or set up before your first deploy
  • A free demo cluster to try the workflow first
  • Scales between the node counts you set
  • The same stacks and deployment workflow as your own cluster
See Wodby Cloud

Connect the services your apps already use

An integration links Wodby to an account you already have, such as your Git provider, a storage bucket for backups, or an API your app calls.

Connected once
Set up a service once and reuse it across your apps.
Out of your code
Credentials stay out of your repositories and are managed in one place.
Per environment
Override any value for each environment.
Stack preview

Laravel stack preview

Stack serviceBase serviceRole
Nginx
Nginx (Laravel)Primary
Valkey
ValkeyRequired
PHP
PHP (Laravel)Required
MariaDB
MariaDBRequired
Files NFS storage
Ganesha NFS provisionerEnabled by default
Mailpit
MailpitEnabled by default
Gotenberg
GotenbergDisabled by default
Cloud MariaDB
Cloud MariaDBDisabled by default
Cloud MySQL
Cloud MySQLDisabled by default
OpenTelemetry Collector
OpenTelemetry CollectorDisabled by default
OpenSMTPD
OpenSMTPDDisabled by default

Keep moving

Explore the Laravel setup, then start your own deployment

Once you've reviewed the stack structure, create an account to launch Laravel, connect your repository, and keep delivery inside the same workflow.

Trusted by developers and businesses worldwide since 2015

Wodby is a reliable cloud infrastructure partner for your business.
See what our customers say about their experience with Wodby.

  • We moved our Drupal hosting to use Wodby and changed our development workflow to use Docker at the same time. Now we can concentrate on Drupal development and we're not losing time configuring servers etc. When a site needs additional resources or hosting in a different region we can be way more responsive as deploying a new instance takes no time at all.

    Tony Miller
    Eighty Options
    Tony Miller, Eighty Options
  • Wodby’s innovative infrastructure helped us to increase the speed and simplify our app deployment, while also leaving us the freedom of handling our hosting and not locking us on a specific pattern. We are now much more robust for future growth and will be able to innovate faster.

    Martin Normann Lund
    Ramsalt Lab
    Martin Normann Lund, Ramsalt Lab
FAQ

Frequently Asked Questions

Have questions? We've got answers. If you don't see your question here, feel free to reach out.

Get started

Ready to deploy Laravel?

Choose Wodby Cloud, managed Kubernetes, or your own server, then deploy stacks with CI/CD, backups, SSL, integrations, and environment management in the same platform.

  • Run the same stack workflow on Wodby Cloud, managed Kubernetes, or your own server
  • Deploy app environments for production, staging, previews, and development
  • Use Wodby CI or your existing pipeline with the Wodby CLI
  • Keep backups, certificates, integrations, and access control in the platform

Start for free

No credit card required
$0/month
  • 10 app services
  • 30 minutes of integrated CI
  • 5 GB of private registry
  • Stacks & integrations
  • Technical domains with SSL
Create free account
Upgrade when you need more capacity