Cloud app hosting in Detroit and Los Angeles
Most hosting companies answer "where does my app run?" with a map of cities they keep no equipment in. We'd rather answer it plainly: your apps run in one of two US locations — Detroit, Michigan or Los Angeles, California — and you pick which one at checkout.
Two coasts, stated honestly, is the whole story. Here's what that gets you.
Detroit: the middle of the map is not a compromise
Our Detroit host sits where the big networks already are. Cloudflare answers our pings from there in about a fifth of a millisecond — which, in practice, means their gear and ours are effectively in the same building. A central location serves Chicago, Toronto, New York and both coasts more evenly than either coast serves the other, which is exactly what you want for a US audience that isn't all in one place.
Los Angeles: the West Coast and the Pacific
Our Los Angeles host is the counterweight — a genuine coastal presence for the traffic Detroit is furthest from. From LA, Google answers in about a third of a millisecond. If your users are on the West Coast, or across the Pacific, this is the side of the country to put your app on.
You choose the region
Picking a location is a choice at deploy time, not a support ticket. Deploying a photo library for a family in California? Los Angeles. Running a team wiki for a company in the Midwest or on the East Coast? Detroit. Same catalog, same one-click deploy — you just tell us which coast.
Measured, not claimed
Every latency figure we publish is a real ping taken from the app host itself, not copied from a datacenter brochure — and we publish the actual IP addresses so you can run ping or mtr against them from wherever your users are and check our homework before you spend a cent. A location page is exactly where hosting companies invent numbers; we'd rather you measured ours.
IPv6 on every app, both coasts
Every app gets a real public IPv6 address alongside IPv4, in both locations, with no add-on and nothing to ask for. A surprising number of hosts still treat IPv6 as a feature; we treat it as table stakes.
The panel isn't in the same place — on purpose
The control panel and billing run on separate infrastructure from the hosts they manage, so a problem with one doesn't take the other down. Your apps are in Detroit or Los Angeles; the thing you log into is on neither. And because apps are reached by hostname — yours under our domain, or a custom domain you point at us — a hardware or provider change underneath never changes how your app is reached.
See exactly where it runs
We put the full picture — the measured latencies, the pingable addresses, and the honest limits — on one page. If you're evaluating where to host, that's the page to read before you buy.
See the network and the measured numbers → — or browse the app catalog and pick your coast at deploy time.