Deploy model
Push your Dockerfile. We run php artisan migrate on deploy, attach managed MySQL, and start a separate queue worker container that shares the same image. Storage is on a persistent volume — uploads survive deploys.
Why a US region for Laravel
The US Laravel stack usually means Forge plus a DigitalOcean droplet, or Vapor on top of AWS Lambda. Forge is a provisioning tool, so you still own the server underneath it — patching, disk, and the day the queue worker dies quietly. Vapor removes the server and hands you Lambda's constraints instead: cold starts, execution limits, and a bill shaped like traffic. Hostim is neither. Your app is a container built from your own Dockerfile, the queue worker is a second container from the same image, MySQL is managed, and storage/ is a real persistent volume rather than a symlink you have to recreate on every rebuild. It all works in Falkenstein today. A New Jersey region is what would make it sensible for an agency in Chicago or a SaaS in Austin, and the waitlist is how we find out how many of those there are.
Expected latency, US privacy law, and what we will not claim
Expected latency. The expected site is Secaucus, New Jersey; the exact facility is not fixed and any northern New Jersey site gives similar figures. The figures below are typical round-trip times for that metro — they are estimates for the location, not measurements from Hostim hardware, because there is none there yet.
| City | Expected RTT to US East |
|---|---|
| New York | ~2 ms |
| Washington DC | ~6 ms |
| Boston | ~8 ms |
| Chicago | ~20 ms |
| Atlanta | ~20 ms |
| Dallas | ~35 ms |
| Denver | ~45 ms |
| Seattle | ~65 ms |
| San Francisco | ~70 ms |
Privacy law. CCPA and CPRA in California, plus state acts in Virginia, Colorado, Connecticut, Utah and a growing list of others. There is no single federal privacy law, so the obligations follow your users, not your servers.
Who enforces it. the California Privacy Protection Agency (CPPA) and state attorneys general — there is no federal data protection authority.
Data residency — read this before you plan a migration. A US East region means your app, your database and your volumes run on hardware in New Jersey. It does not make Hostim a US company: HOSTIM.DEV UG is German, and that is a real consideration if you have a customer contract that restricts foreign processors. Ask us before you assume either way.
Market context. US teams rarely pick a host for data residency. They pick it for price, for not being on-call for a Kubernetes cluster, and for latency to users on the East Coast. The pitch that works in Frankfurt does not work in Brooklyn — what works is a flat bill and a container that stays running.
What you are probably comparing us against: Heroku, Render, Railway, Fly.io, DigitalOcean App Platform, AWS App Runner.
How Hostim runs Laravel
Laravel hosting was traditionally shared LAMP with FTP uploads. Modern Laravel deploys are container-based: PHP-FPM plus Nginx in one image, MySQL or PostgreSQL on a separate service, and a queue worker as a second container. Hostim runs this layout natively.
Common pitfalls
Two things often break: queue workers running as the same container as the web server (they should be separate), and the storage symlink not surviving a rebuild. Hostim solves both with explicit worker apps and persistent volumes.
Typical env vars
APP_KEY, APP_ENV, DB_CONNECTION, DB_HOST, QUEUE_CONNECTION
FAQ
Is US East live?
No. It is a planned region. Hostim runs one region today, in Germany. This page exists so US and Canadian teams can register interest before we commit to building.
How are queue workers handled?
As a separate app in the same project, built from the same image with php artisan queue:work as the command. Scaling the worker does not scale the web container, and a crashed worker restarts on its own.
Does the storage symlink survive a rebuild?
Yes, when storage/ is on a persistent volume. This is the failure people hit most often when moving Laravel to containers, so it is worth setting up on day one regardless of which platform you choose.
Would billing be in USD?
We bill in EUR today. Currency and pricing for a US region are open questions we will settle before launch — if invoicing in USD is a requirement for you, say so on the waitlist form, because that is exactly the kind of thing the list is for.
Can I run FrankenPHP or Octane?
Yes. You control the Dockerfile and the start command, so FrankenPHP, Octane with Swoole, or plain PHP-FPM behind Nginx all work. Hostim does not impose a buildpack.
Would you use US East (New Jersey)?
We are deciding how much capacity to build. Add your name and what you would run — that is the whole input. You can also deploy to our live German region today if that works for you.
The numbers behind this
Platform figures from the published price list, docs and our own benchmark.
€2.50/month
Hostim entry app plan
Plan sa-1-1: 1 vCPU, 1 GB RAM. Flat price, billed hourly, no usage meter.
€0
Managed database free tier
PostgreSQL 256 MB, MySQL 256 MB, Redis 128 MB, volume 1 GB. No cap on how many free instances you create.
Included on every plan
Database high availability
PostgreSQL and MySQL run as a primary plus hot standby with automatic failover, shared plans included.
2,708 TPS
Managed PostgreSQL write throughput
pgbench, 4 clients, 300 s, plan drp-50 (2 vCPU / 4 GB). AWS RDS db.t4g.medium scored 1,080 TPS on the same test.
€0/GB
Traffic charges
No ingress fees and no per-GB egress line on app plans.
1 today (Falkenstein, Germany)
Regions
Bare metal, EU only, with more regions planned. No AWS, GCP or Azure underneath.
“Managed PostgreSQL runs as a replicated cluster with automatic failover on every plan, shared and dedicated alike.”
— Hostim.dev docs, managed PostgreSQL
Sources
- Hostim.dev price list — Hostim.dev (checked 2026-08-06)
- Pricing model — plan-based billing, no metering — Hostim.dev docs (checked 2026-08-06)
- Managed PostgreSQL — high availability and failover — Hostim.dev docs (checked 2026-08-06)
- PostgreSQL benchmark: AWS RDS vs Hostim vs self-hosted on Hetzner — Hostim.dev blog, July 2026 (checked 2026-08-06)