Skip to main content

Planned region → the United States

Django Hosting in 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.

Django on Hostim is a Docker container, a managed PostgreSQL, and a persistent volume for /media — migrations run on deploy. That stack runs in Germany today. We are planning a US East region in New Jersey for teams whose users are in North America. It is not built yet. Join the waitlist if you would move a Django app there.

Region status
# docker-compose.yml
services:
  web:
    image: my-django-app
    environment:
      - DJANGO_SETTINGS_MODULE=config.settings.prod
  db:
    image: postgres:16
    volumes:
      - db_data:/var/lib/postgresql/data
  • 🇪🇺 Hosted in Germany, GDPR by default
  • 🐳 Run Docker apps (Compose supported)
  • 🗄️ Built-in MySQL, Postgres, Redis & volumes
  • 🔐 HTTPS, metrics, and isolation per project
  • 💳 Per-project cost tracking · from €2.5/month

Why a US region for Django

US Django teams mostly land on Heroku, on Render, or on a hand-rolled EC2 box with an RDS instance next to it. Heroku works and costs more every year. The EC2 path is cheap until you count the hours you spend on it — you become the person who owns the deploy script, the certificate renewal, and the 2 a.m. disk-full page. Hostim is the middle option: a managed platform on bare metal, where Django runs under Gunicorn or Uvicorn in a container you can read the Dockerfile for, PostgreSQL is managed, and /media sits on a volume that survives restarts. That is available in Germany now. A New Jersey region would make it a reasonable choice for a US-facing app, where a 100 ms transatlantic round-trip currently rules it out. Tell us on the waitlist what you would move and how big it is.

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.

CityExpected 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 Django

Modern Django deployment is container-based. The app runs under Gunicorn or Uvicorn, with PostgreSQL on a separate service and persistent storage for media uploads. Hostim mirrors this layout one to one.

Deploy model

You bring a Dockerfile or a Git repo. We build, run migrations on deploy, and attach managed PostgreSQL plus a volume for /media. ASGI works the same as WSGI — Channels and async views run without extra config.

Common pitfalls

Two common failure points: media files lost on container restart, and DATABASE_URL hardcoded for local dev. Hostim provides persistent volumes for /media and injects DATABASE_URL at runtime.

Typical env vars

DJANGO_SETTINGS_MODULE, SECRET_KEY, DEBUG, ALLOWED_HOSTS, DATABASE_URL

FAQ

Is the US region available now?

No — it is planned, not running. The one live Hostim region is Falkenstein, Germany. Everything described on this page works there today; what is missing is a US location, which is what the waitlist decides.

Why does the region matter for Django specifically?

Django apps are usually chatty with the database and render server-side. If the app and the database are both in Germany and the user is in Texas, every page load pays one transatlantic round-trip of roughly 100 ms. Moving both to New Jersey removes it.

Do media uploads survive deploys?

Yes. Mount a persistent volume at /media. It is attached to the app across rebuilds and restarts, so uploaded files are not lost when a container is replaced. Same behaviour in any region.

How does US East pricing compare to Heroku?

We do not have a US figure to give you yet — regional pricing is set per region and will be published before launch. What we can say is the model: flat monthly cost for reserved CPU, RAM and disk, with managed PostgreSQL on a real free tier rather than a trial.

Who operates Hostim?

HOSTIM.DEV UG, a German company. A US East region would put your servers in New Jersey but would not change who operates the platform. If that distinction matters for a customer contract you have, raise it on the waitlist form and we will answer honestly.

Related pages

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.

Deploy to the EU region

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

  1. Hostim.dev price list — Hostim.dev (checked 2026-08-06)
  2. Pricing model — plan-based billing, no metering — Hostim.dev docs (checked 2026-08-06)
  3. Managed PostgreSQL — high availability and failover — Hostim.dev docs (checked 2026-08-06)
  4. PostgreSQL benchmark: AWS RDS vs Hostim vs self-hosted on Hetzner — Hostim.dev blog, July 2026 (checked 2026-08-06)