Zerops x Laravel

Developer-first cloud platform
for Laravel apps and ecosystem

Zerops is a cloud platform committed to creating the ideal mix of affordability, developer experience, flexibility and scalability. No matter the type of environment or size and complexity of the app. And it turns out this mix works beautifully with the Laravel ecosystem!

How would we define a solid developer-first foundation
for Laravel apps, regardless of infrastructure provider?

Infrastructure setup that can handle applications small and simple as well as large and complex, with environment parity from local/devel to production environment

Scales resources seamlessly with changing loads

Resource allocation should respond dynamically in both directions - scaling up for traffic spikes and down during quiet periods. Fine-grained adjustment capabilities prevent resource waste while ensuring consistent performance throughout load variations.

Evolves with architectural complexity

Evolving architecture brings new services, data stores, and communication patterns. The foundation must accommodate this growing complexity without sacrificing operational efficiency or developer experience.

Manages stateful services with care

Stateful components require sophisticated orchestration - from scaling and replication to backup and recovery strategies. Their management demands a careful balance between automation and granular control.

Ensures system resilience automatically

High availability requires running services across multiple physical machines with automated failover. Combined with encrypted backups and rapid recovery capabilities, this ensures both operational continuity and data protection.

Enables consistency across different environments

Development infrastructure must eliminate environment-specific behavior by design. Resource allocation should be the only variable between environments, making production behavior predictable from day one, eliminating the "it works on my machine" problem.

Avoids becoming a vendor-locked blackbox

Infrastructure foundations must maintain transparency and modifiability, built on proven practices and open technologies. This ensures both operational independence and architectural freedom.

Developer Experience & tools that make your
life easier and supports your environments throughout the whole development process,
from the first line of code to production

Build and deploy automation that adapts to your setup

Pipeline complexity should follow application needs, not infrastructure limitations. From straightforward git workflows to sophisticated build stages, deployment automation must maintain full control while eliminating maintenance burden.

Effortless system observability

Developers need immediate insight into system behavior without additional instrumentation work. Structured logs, metrics, and traces should be collected automatically from all services, aggregated centrally, and forwarded to existing monitoring tools.

Built-in environment variables & secrets management

Environment variables and secrets must be centrally managed and securely distributed across development stages. Values should be protected from unauthorized access, automatically propagated to services that need them, and support dynamic configuration between connected services.

Production-mirroring local development

Local development environments must mirror production behavior while maintaining development speed. Developers need direct access to live services and data without wrestling with complex local infrastructure setups or environment synchronization.

Secure and developer-friendly internal & public networking

Services should feel like they're running right next to each other while maintaining strict isolation underneath. Developers need seamless service discovery and communication locally, with straightforward domain and routing management for public access - all without having to think about the underlying networking complexity.

Complete development toolkit

Modern development workflows demand more than interfaces - they require programmatic control at every level. Infrastructure should provide native APIs, CLI tools, and templating capabilities that integrate naturally with existing development patterns while maintaining consistent behavior across all interaction points.

Zerops is built on developer-first foundations.
Deploy ready-to-use Laravel stacks from local to prod.
Free credits, no CC needed, ready to explore in minutes.

Implements environment variables & secrets Provides automated build & deploy pipeline Enables high availability setup Ensures idempotent seeding and migrations Maintains automated backups Integrates object storage solution Manages SSL certificates automatically Monitors health & readiness states

Laravel minimal

This recipe showcases a production-ready integration of basic Laravel apps to Zerops. The fact this environment is called development comes just from its minimal, cost-efficient resource allocation, selection of the Lightweight core package.

laravel-minimal-devel

Lightweight project core
Single dedicated container with balancers (L3/L7), logger and statistics services
app:80
PHP+Nginx v8.3
db:5432
PostgreSQL v16

2Shared Cores

GBRAM

GBDisk (SSD)

$4.80

Per month for
Resources cost
add
$0.00Per month for
Lightweight pkg.

Laravel Jetstream

This recipe showcases a production-ready integration of Jetstream apps to Zerops. The fact this environment is called development comes just from its minimal, cost-efficient resource allocation, selection of the Lightweight core package.

laravel-jetstream-devel

Lightweight project core
Single dedicated container with balancers (L3/L7), logger and statistics services
app:80
PHP+Nginx v8.3
db:5432
PostgreSQL v16
mailpit:8025
Go v1.2
Dev only
redis:6379
Valkey v7.2
storage
Object storage

4Shared Cores

2.25 GBRAM

GBDisk (SSD)

GBObject storage

$10.0

Per month for
Resources cost
add
$0.00Per month for
Lightweight pkg.

FilamentPHP

This recipe showcases a production-ready integration of Filament with Zerops. The fact this environment is called development comes just from its minimal, cost-efficient resource allocation, selection of the Lightweight core package.

filament-devel

Lightweight project core
Single dedicated container with balancers (L3/L7), logger and statistics services
app:80
PHP+Nginx v8.3
db:5432
PostgreSQL v16
mailpit:8025
Go v1.2
Dev only
redis:6379
Valkey v7.2
storage
Object storage

4Shared Cores

2.25 GBRAM

GBDisk (SSD)

GBObject storage

$10.0

Per month for
Resources cost
add
$0.00Per month for
Lightweight pkg.

TwillCMS

This recipe showcases a production-ready integration of TwillCMS with Zerops. The fact this environment is called development comes just from its minimal, cost-efficient resource allocation, selection of the Lightweight core package.

twillcms-devel

Lightweight project core
Single dedicated container with balancers (L3/L7), logger and statistics services
app:80
PHP+Nginx v8.3
db:5432
PostgreSQL v16
mailpit:8025
Go v1.2
Dev only
redis:6379
Valkey v7.2
storage
Object storage

4Shared Cores

2.25 GBRAM

GBDisk (SSD)

GBObject storage

$10.0

Per month for
Resources cost
add
$0.00Per month for
Lightweight pkg.

Custom-built from the ground up and running on bare-metal
in top-tier datacenters to deliver an ideal mix of flexibility,
scalability, developer experience, and affordability

Dedicated core infrastructure
deployed with each Zerops project

Project e.g. laravel-jetstream-prod
fully managed by Zerops
added by user

Project core services
  • A secure, private network (VXLAN, cgroups)
  • L3 balancer with a built-in firewall
  • Logger container with log forwarding
  • Unique IPv6 and IPv4 address support
Routing service
  • Highly available L7 balancer with HTTP routing
  • Unique Zerops subdomain for previews
  • SSL termination and automatic SSL certificates

Services w/ Containers & VMs

  • Native support for all popular runtimes on full OS Linux Containers, no Docker needed
  • Support for VMs and VMs with Docker
  • Managed backups, failovers, healthchecks, repairs, scaling, configration and optimizations for relational, vector, key-value databases, search and queue/messaging engines and storages
  • Optional high availability for all services with internally handled load balancing
  • Fully automatic horizontal and vertical scaling
  • Application Version backups with re-activations
  • Health and readiness checks
app:80PHP+Nginx
node-id-1.runtime.app.zerops
v2.0.2
node-id-2.runtime.app.zerops
v2.0.2
node-id-3.runtime.app.zerops
v2.0.2
db:5432PostgreSQL
node-id-1.proxy.db.zerops
Proxy balancer
node-id-2.proxy.db.zerops
Proxy balancer
node-id-1.db.db.zerops
Primary / Write
node-id-2.db.db.zerops
Secondary / Read
node-id-3.db.db.zerops
Secondary / Read
cache:6379Valkey
node-id-1.db.cache.zerops
Primary
node-id-2.db.cache.zerops
Primary
node-id-3.db.cache.zerops
Primary

Projects can be imported
using a simple YAML structure or added through the GUI

project:
  name: laravel-jetstream-prod
  corePackage: SERIOUS

services:
  - hostname: db
    type: postgresql@14
    mode: HA

  - hostname: app
    type: php-nginx@8.3
    envSecrets:
      API_KEY: uODWOe/gCX+wE...
    minContainers: 3

  - hostname: mailpit
    type: go@1
    maxContainers: 1

  - hostname: cache
    type: valkey@7.2
    mode: HA

  - hostname: storage
    type: object-storage
    objectStorageSize: 2

Project can be imported
using a simple YAML structure
or added through the GUI

A Flexible, build, prepare, deploy and run
pipeline with zero-downtime deployments

1

Trigger the pipeline

Automatically, with each commit or release, by connecting the service with your GitHub or GitLab repository

Manually, by using Zerops CLI to trigger the pipeline from your existing CI/CD pipeline or from your local terminal

# install zcli, see docs
# for more install options
~ npm i -g @zerops/zcli
# login using token that can be
# obtained at the token management page
# (needs to be done only once)
~ zcli login PLACE_TOKEN_HERE
# navigate to the root of your project
# (where zerops.yml is) and use push
# command to trigger the pipeline
~ cd ./my-project
my-project zcli push
2

zerops.yml in your repo tells Zerops
how to build and run your app

zerops:
  - setup: app
    build:
      base: php@8.3
      builCommands:
        - composer i -o --no-dev
      deployFiles: ./
      cache: vendor
    run:
      base: php-nginx@8.3
      siteConfigPath: site.conf.tmpl
      envVariables:
        DB_CONNECTION: pgsql
        DB_DATABASE: ${db_dbName}
        DB_HOST: ${db_hostname}
        DB_PASSWORD: ${db_password}
        DB_PORT: ${db_port}
        DB_USERNAME: ${db_user}
      initCommands:
        - php artisan view:cache
        - php artisan config:cache
        - php artisan route:cache
        - php artisan migrate -i -f
        - php artisan optimize
Pipeline NfcOVw...PPUZDA for service laravel-jetstream-prod/app using source from release v2.0.2 of repository zeropsio/laravel-jetstream
2 minutes 28 seconds elapsed
Initialized build container
Build commands from zerops.yml ran successfully
Creating app version v2.0.2 and upgrading PHP+Nginx service app
3

Containers with the new image
and the new app version are created,
old containers are then removed

app:80 PHP+Nginx
node-id-4.runtime.app.zerops
v3.0.0
node-id-5.runtime.app.zerops
v3.0.0
node-id-6.runtime.app.zerops
v3.0.0
node-id-1.runtime.app.zerops
v2.0.2
node-id-2.runtime.app.zerops
v2.0.2
node-id-3.runtime.app.zerops
v2.0.2

Pricing model that doesn't get in the way
of good development practices

Simple, affordable
and consistent pricing

Lightweight project package

$0.00 
/
per 30 days
per project

Serious project package

$10.00
/
per 30 days
per project

Resources used by services inside

1x Shared CPU

$0.60/ 30 days
$0.000014/ minute

0.25 GB RAM

$0.75/ 30 days
$0.000017/ minute

0.5 GB Disc

$0.05/ 30 days
$0.00000116/ minute

Along with a granular configurable autoscaling
for each service

Containers
Start with1
Scale Up To6
CPU Cores (shared or dedicated)
Start with1 core
Scale Up To5 cores
RAM
Start with0.25 GB
Scale Up To32 GB
DISK
Start with1 GB
Scale Up To100 GB

How does Zerops pricing compare
with other popular hosting options?

We've configured a medium-sized production setup and compared similar configurations across providers. Where possible, we use dedicated CPU cores to help normalize performance levels, since shared CPU offerings can vary between providers. While this example represents a specific configuration, similar pricing patterns tend to appear across different project sizes.

Reference setup

Services6
CPU20 cores
RAM40 GB
Backend
2 nodesLoad balanced, highly available
CPU1 core
RAM2 GB
Disk10 GB
Frontend
2 nodesLoad balanced, highly available
CPU1 core
RAM2 GB
Disk10 GB
Worker
1 node
CPU2 cores
RAM4 GB
Disk10 GB
Database
3 nodesPrimary + Read + Read nodes
CPU4 cores
RAM8 GB
Disk50 GB
Cache
2 nodesRead/write replicas
CPU2 cores
RAM4 GB
Disk10 GB
Storage
Object Storage50 GB
$ 177per mth.
Coolify+Hetzner
$ 330per mth.
Zerops
$ 486per mth.
Fly
$ 593per mth.
DigitalOcean
$ 606per mth.
Railway
$ 661per mth.
AWS (Flightcontrol)
$ 1023per mth.
Render
$ 2105per mth.
Heroku