Planned region → Canada
Not available yet. US East (New Jersey) is a region we are planning, not one you can deploy to. Hostim runs one live region today, in Falkenstein, Germany.
Toronto and Montreal are 12 to 15 ms from northern New Jersey, so a US East region would serve most Canadian Next.js traffic well. That region is planned, not built. Hostim runs one region today, in Germany. If you run a Next.js app for Canadian users, join the waitlist and tell us whether US East would work for you or whether you need storage inside Canada.
# docker-compose.yml
services:
web:
image: my-nextjs-app
environment:
- NODE_ENV=production
- DATABASE_URL=postgres://...
db:
image: postgres:16For a Canadian SaaS the interesting question is not latency — 12 ms to Montreal is fine — it is whether your obligations let you host outside the country. Under PIPEDA, private-sector organisations generally can use a foreign processor, provided the contract keeps the protection comparable and you are transparent about it. Quebec Law 25 is stricter and asks you to assess the transfer before you make it. Nova Scotia public-sector work is stricter again: PIIDPA requires the data to stay in Canada, which a New Jersey region does not satisfy. British Columbia removed its statutory residency rule in 2021, but many BC public bodies still keep the requirement in their own policy, so check before you assume. We would rather say that plainly on this page than have you find out after migrating. Setting the legal question aside, the platform is the usual Hostim shape: Next.js standalone server as a long-lived container, warm ISR cache, image optimization in-process, managed PostgreSQL, flat monthly price.
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.
Next.js hosting today means running a Node.js process behind HTTPS, with a build step that produces static and server bundles. Most teams either run the standalone server output in Docker or use a platform-specific runtime. Hostim runs the standalone server in a normal Docker container, so you stay portable.
Push a Dockerfile or connect a Git repo. We build the image, attach a managed PostgreSQL, and serve traffic on a subdomain or your custom domain with automatic HTTPS. ISR and image optimization work because we run a real long-lived Node process — not a serverless function.
Two things often break on serverless platforms: long background jobs and large file uploads. Hostim avoids both by running stateful containers with persistent volumes for cache, uploads, and the .next directory.
NODE_ENV, DATABASE_URL, NEXTAUTH_SECRET, NEXTAUTH_URL
No, and none is currently planned. The region under consideration is US East, in New Jersey, which is 12 to 15 ms from Toronto and Montreal. If you specifically need data stored inside Canada, tell us on the waitlist form — we count that separately from US East demand.
PIPEDA does not require Canadian storage for private-sector organisations. It requires comparable protection through your contract with the processor and transparency with your users. That is a question about your agreements, not only about server location, and you should confirm it with your own counsel.
Law 25 requires a privacy impact assessment before transferring personal information outside Quebec. It does not ban the transfer. It does mean a New Jersey region needs paperwork that a Quebec region would not, and that cost is yours to weigh.
Nova Scotia, no — PIIDPA requires storage and access inside Canada, and New Jersey does not meet that. British Columbia repealed its statutory residency rule in November 2021, so it is now a policy question for the specific public body rather than an automatic no. We would rather tell you that than sell you a migration that fails a procurement review.
Our German region, which is live. For a Canadian user base that means roughly 90 to 100 ms of round-trip, which is workable for internal tools and poor for consumer-facing apps.
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.
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