Planned region → the United States
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.
Hostim runs Next.js as a long-lived Docker container: a real Node process, no cold starts, no per-invocation billing. Today that runs in Germany, which is too far for a US user base. We are planning a US East region in New Jersey — around 2 ms from New York and 20 ms from Chicago. It is not live yet. If you would move a Next.js app to it, join the waitlist and tell us what you are running.
# docker-compose.yml
services:
web:
image: my-nextjs-app
environment:
- NODE_ENV=production
- DATABASE_URL=postgres://...
db:
image: postgres:16The usual Next.js path in the US is Vercel, and for a marketing site that is a good deal. It gets expensive in a specific place: an app with heavy SSR, long-running API routes, or large image transforms, where the bill scales with traffic instead of with the size of the box. Hostim charges for reserved CPU, RAM and storage, flat per month, and runs the Next.js standalone server as a normal container — so ISR keeps its in-memory cache, image optimization runs in-process, and a 90-second API route is just a request that takes 90 seconds. Everything in that description works today in our German region. What US teams do not have yet is a nearby one. A New Jersey region would put the same setup inside single-digit milliseconds of the East Coast, and that is the gap the waitlist is measuring.
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.
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. The region is in planning. Hostim currently runs one region, in Falkenstein, Germany, and you can deploy there today. The waitlist is how we decide whether to build the US East region and how big to make it at launch.
The expected site is Secaucus, New Jersey, though the exact facility is not fixed yet. Typical round-trip for that metro is about 2 ms to New York, 6 ms to Washington DC and 20 ms to Chicago. These are normal figures for the location, not measurements from our hardware — we have not installed any there yet.
We cannot give you a US number yet, because US East pricing will be set separately from EU pricing and published before launch. The structure will not change: you pay for a reserved container and reserved database, flat per month, not per request or per bandwidth unit.
Yes, and it works better. The Next.js standalone server runs as one long-lived process, so the ISR cache stays warm between requests, and a persistent volume keeps the .next directory across deploys. This is how our German region works today.
Your project stays in the region you picked. We are not moving anyone. If US East launches and you want to move, that would be a migration you choose to run, not something applied to you.
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