For Laravel

Laravel hosting
without the markup

Production VMs with proper CPU, S3-compatible storage for the filesystem driver, and a global CDN with zero egress fees. The full Laravel stack, on infrastructure you actually control.

Start your trial Read the deploy guide

# Provision a VM and bootstrap PHP/Nginx

$ edge compute create \

--image ubuntu-24-04 --plan small \

--script ./bootstrap-laravel.sh

# Configure the s3 disk in config/filesystems.php

'edge' => [

'driver' => 's3',

'endpoint' => env('EDGE_ENDPOINT'),

'bucket' => env('EDGE_BUCKET'),

# Front it with the CDN

$ edge cdn create app.example.com \

--origin https://<vm-ip>

Why Laravel teams pick Edge

The DigitalOcean-style simplicity you love, with the global edge network and storage you'd otherwise glue together yourself.

Real VMs, not shared hosting

Dedicated vCPU, NVMe storage and 10Gbps networking. Sized from a small VM up to multi-core monsters as you grow.

S3-compatible Filesystem

Plug Edge Storage into Laravel's `s3` filesystem driver. Uploads, exports and backups offloaded to durable object storage.

Global CDN, zero egress

Front public/ assets, Mix/Vite output and Storage URLs through the Edge CDN. No egress fees, no per-request gotchas.

Bring your DB

Run MySQL, MariaDB, PostgreSQL or Redis on the same VM, a separate VM, or your existing managed provider. Your call.

On-the-fly image transforms

Skip Intervention/Image queues — point Edge Image Optimization at your bucket and resize/convert via URL.

Forge-style automation

Use the Edge CLI or agentic API to provision VMs, set firewall rules, and roll out releases — scriptable end-to-end.

Reference architecture

How Laravel maps to Edge

A typical Laravel app maps cleanly onto our four core products. Same mental model as your dev box, but with global delivery and zero egress for everything users actually download.

Compute

Runs PHP-FPM + Nginx (or Octane) on a sized-to-fit VM

Storage

S3-compatible bucket for the `public` and `s3` Laravel disks

CDN

Caches static assets, Vite output, and public Storage URLs

Image Optimization

On-the-fly resize, crop and AVIF/WebP conversion of media

DNS

Anycast DNS for your apex, subdomains and email records

# app/Http/Controllers/UploadController.php

$path = $request->file('avatar')

->store('avatars', 'edge');

# Generate a CDN-fronted URL

$url = 'https://cdn.example.com/' . $path;

# Resize on the fly

$thumb = $url . '?w=300&fit=cover&fm=webp';

Common questions

Does Laravel Octane work?

Yes. Run Octane with Swoole or RoadRunner on an Edge VM exactly as you would on any other Linux box. We have no Lambda-style cold starts to worry about.

Can I use Forge-style provisioning?

You can keep using Forge if you want — point it at an Edge VM by IP. Or use the Edge CLI / agentic API to bootstrap an equivalent stack with a single script.

How do queues and scheduled tasks work?

Run `queue:work` and `schedule:run` as systemd services on the same VM, or split workers onto a dedicated VM. Use Redis on the same VM for cheap, fast queues.

Where do I store user uploads?

Use the standard `s3` filesystem driver pointing at an Edge Storage bucket. The AWS SDK works unchanged — just set the endpoint to the Edge Storage endpoint.

By Stack