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 Canadian region for Laravel
Most Canadian Laravel work runs through agencies and small product teams, where the deciding factor is the total cost of running twenty small client apps rather than the architecture of one large one. That is a case Hostim is genuinely good at: each client gets a project with its own app, database and domain, all apps are priced as reserved containers, and there is no per-seat charge that grows with your client list. The obstacle right now is distance. A German region serving a Vancouver client is roughly 150 ms away, and that shows up in every admin panel page load. New Jersey would bring the east of the country inside 15 ms and Vancouver to about 70 ms, which is the same ballpark as most US platforms serving Vancouver anyway. Whether we build it is what the waitlist is for. If you run client apps and would move them, that is the strongest signal you can give us.
Expected latency, Canadian 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 |
|---|---|
| Montreal | ~12 ms |
| Toronto | ~15 ms |
| Ottawa | ~16 ms |
| Halifax | ~25 ms |
| Winnipeg | ~40 ms |
| Calgary | ~55 ms |
| Vancouver | ~70 ms |
Privacy law. PIPEDA at the federal level, Quebec Law 25 (the strictest of the set, with transfer assessments and breach reporting), and Nova Scotia's PIIDPA, which still requires public-sector data to be stored and accessed only in Canada. British Columbia dropped its blanket residency rule in November 2021, so BC public bodies now decide foreign storage by their own policy rather than by statute.
Who enforces it. the Office of the Privacy Commissioner of Canada (OPC), and the Commission d'accès à l'information for Quebec.
Data residency — read this before you plan a migration. US East is in New Jersey, not Canada. If your contract or your provincial rules require Canadian storage, this region will not meet that requirement — tell us on the waitlist form and we will count it as demand for a separate Canadian region rather than pretending US East solves it.
Market context. Toronto and Montreal are 12–15 ms from New Jersey, so a US East region serves most Canadian users well. The exception is public-sector and health work: Nova Scotia requires storage inside Canada by statute, parts of the Quebec public sector do too, and many BC public bodies still require it by internal policy even though the statutory rule was removed in 2021. A New Jersey region does not satisfy any of those. Private-sector SaaS under PIPEDA generally can use a US region with the right contract terms.
What you are probably comparing us against: Heroku, Render, Railway, DigitalOcean, OVHcloud Canada, Vultr Toronto.
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 the region live?
No. US East is in planning and this page describes what it would be. The one running Hostim region is in Falkenstein, Germany.
What would latency look like across Canada?
From the planned New Jersey site: about 12 ms to Montreal, 15 ms to Toronto, 55 ms to Calgary and 70 ms to Vancouver. Western Canada is served roughly as well as it is by most US East platforms.
Can I host multiple client apps in one account?
Yes. Each client is a project with its own apps, databases, volumes and custom domains, billed on one consolidated invoice with per-project usage visible. That works the same in any region.
Does storing client data in the US create a problem?
It depends on your client contracts and on the province. Under PIPEDA a foreign processor is generally allowed with comparable protection in place. Nova Scotia public-sector clients require Canadian storage by statute, and some BC public bodies still require it by policy even though the law changed in 2021. New Jersey would not provide it.
What if I need a Canadian region instead?
Say so on the waitlist form. We count Canadian-residency demand separately from US East demand, because they are different builds with different costs, and pretending otherwise would just give us bad data.
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)