Start a project →

Laravel and Symfony on AWS ECS.

We move your PHP app into containers on AWS and run it the way we run our own product. One image serves the web, the queue workers and the scheduler. Every deploy is zero-downtime.

Tell us about your app See how we run Vision

What the setup includes.

  • One image, several services. A production image for your Laravel or Symfony app. The web server, the queue workers and the scheduler run from the same build.
  • A closed network. Cloudflare sits in front, and the load balancer accepts traffic from Cloudflare only. The servers accept traffic from the load balancer only, with no SSH port open and no NAT gateway to pay for.
  • Managed database and cache. RDS for Postgres or MySQL in private subnets with automated backups. A Redis-compatible cache sits next to it.
  • Zero-downtime deploys. CI builds the image and rolls the services onto it. Migrations run as a one-off task after the rollout, never at container start.
  • Infrastructure as code. OpenTofu describes every part, and dev and prod come from the same modules. The repository is yours.
  • Secrets out of the code. Secrets Manager hands credentials to each task at start. Task roles replace long-lived cloud keys wherever the provider supports it.

Proven on our own app.

Our AI product photography app Vision runs on this stack. In the last 60 days a healthy target served traffic 99.98% of the time.

The Vision case study covers the services, the network and the deploy order, including the incident that shaped our migration rules.

How the move works.

01

Review

You tell us about the app: framework, queues, database and traffic. We reply with a plan and a quote.

02

Build

We write the infrastructure in OpenTofu and run the app on a dev environment first.

03

Move

We move the database to RDS and uploaded files to S3, then switch DNS in Cloudflare. The containers start fresh from the registry. The old host stays until you sign off.

04

Run or hand over

We run deploys and monitoring for you. Or your team takes the setup with documentation.

Who this fits.

This fits Laravel and Symfony apps with queues and scheduled jobs that have outgrown one server. It suits teams that want AWS without hiring a DevOps engineer.

Magento runs on AWS too, with more moving parts. Our Magento support and hosting service covers it.

Questions, answered.

Why ECS and not Kubernetes?
ECS runs containers with no cluster control plane to manage or pay for. One app with a few services needs a load balancer, rolling deploys, workers and scheduled tasks. ECS covers all four with less to operate.
Does this work for Symfony?
Yes. A Symfony app with Messenger workers fits the same pattern: one image, a web service, worker services and scheduled tasks.
How much does it cost to run on AWS?
The bill depends on traffic, the number of workers and the size of the database. We size the setup with you and show the expected monthly AWS cost before the move.
Can our team deploy on its own?
Yes. Deploys run from CI, and the infrastructure and pipelines live in your repository. We can run the setup for you or hand it over with documentation.

Run your app on AWS.

Tell us about your app.
We’ll reply with a plan and a quote.

Tell us about your app All services

Reply within 1 business day · Taipei, Taiwan · UTC+08:00