Your home realm
Your account has a home realm. New sites, apps and databases run there.
Every site and app is reached through the edge, the load balancer in front of your realm. It serves HTTPS and blocks common attacks before they reach your code.
Always on
a set for each kind of resource
HTTP/2
plain HTTP redirected to HTTPS
Your realm
one home realm per account
The platform runs in realms. A realm is a group of machines in one place, with an edge in front, a private network and database servers of its own.
Your account has a home realm. New sites, apps and databases run there.
Each realm has one active load balancer on its public addresses. It serves every hostname of the sites and apps in that realm.
Apps and database servers on one network reach each other by name, on every machine of the realm. A database server has no public port unless you open one.
A domain answers from the realm it points at. On managed DNS the records follow when a site or app moves to another realm.
Set for each site and each app hostname, and changed at any time.
With HTTPS on, plain HTTP is redirected to HTTPS and HTTP/2 is used. HSTS is one switch.
gzip and long-lived caching of static assets are switches on each site.
Static files, a single-page app or clean URLs, a not-found page of your own, and files that are never served.
Each visitor’s address is limited on app routes. Past the limit the edge answers 429 before the request reaches your app.
Add response headers and other load balancer directives to a site or app, on paid plans. The platform rules always run first.
Keep a proxy such as Cloudflare in front of your domain. The domain is verified by its TXT record and the proxy holds the certificate.
Many accounts share the machines of a realm, so every container is treated as untrusted.
Every app runs in its own container with every Linux capability dropped and limits on processes, open files and disk IO.
Containers cannot reach the platform, the machine’s management ports or outgoing port 25. Apps send mail through an SMTP server instead.
Patterns that look like mining, spam or scanning are flagged and looked at, so one tenant cannot slow the rest down.
WordPress and PHP sites protected without a security plugin.
HTTPS, HTTP/2 and headers without writing load balancer config.
The same rules on every client site, updated for all of them at once.
The exploit rules are part of the platform, not of your app, and there is no switch to turn them off. Each kind of resource gets its own set, so nothing legitimate is refused. A new rule reaches every site and app within minutes. /.well-known/ is never blocked, so certificates keep working.
HTTPS for every site, app and mail host on your domains. Certificates come from Let’s Encrypt and are issued, installed and renewed for you.
A WordPress site of its own with its own MySQL or MariaDB database, installed fresh or moved in from an archive, with SSH, SFTP and wp-cli.
Run any Docker image with a private network, persistent volumes and a port on your domain.