The edge
TLS, caching of static assets, and protection against abusive traffic happen at Cloudflare’s edge before a request reaches Apprail. An edge location is not a place your code runs.
Network
A global front door.
One place for your app.
Visitors reach your domain through Cloudflare’s edge, close to wherever they are. Behind it, your services, workers and databases run side by side in one compute region, so they talk to each other over a short, private path.
348 cities.
One front door.
Every Apprail domain sits behind Cloudflare. Visitors connect to the nearest of these cities, and requests travel on to your application from there. Hover a city to see the path; drag to turn the globe.
348 citiesCloudflare’s edge in 133 countries and territories, in front of every Apprail domain.
City list from Cloudflare’s network page, September 2026. Cloudflare decides which city answers each visitor; Apprail runs your application in Šiauliai, Lithuania.
Your visitors
Cloudflare edge
Apprail computeŠiauliai, Lithuania
The compute region
Apprail’s current region is Šiauliai, Lithuania. Services, workers, jobs, Postgres, caches, queues and buckets for a project all live there, on a private network per environment.
Your domains
Every service gets an apprail.app address. Add your own domain with the DNS records Apprail gives you; HTTPS turns on once ownership and the certificate are verified.
See it
for yourself.
Deploy something small and
watch it go live.