Hosting architectures
The three ways to run an application on your account, direct serving, app servers, and containers, how to choose between them, and how the reverse proxy connects an app to your website.
Direct sites
Serve an application straight from a website's document root. Put PHP and assets under it and the web server runs them in place, with no process to start, supervise, or keep running.
Applications and updates
The panel finds the WordPress, Drupal, and other applications in your home directory, tells you when a newer version exists, and can apply the update for you, plugins and themes included.
App Servers
Run your own long-running web applications, in Node, Python, or any other language, behind the panel's reverse proxy. The panel starts them on demand and stops them when idle.
Containers
Run container images and stacks in compose format on your account. Ports, volumes, environment files, health checks, restart policies, and the Podman workspace.
Mounts
Map a URL path on your website to an app server, a port, or a directory. Path matching, path rewriting, and the three mount types.
Restrict access
Put part of a website behind a sign-in, with OpenID Connect by default or HTTP basic authentication, using your domain users and groups as the audience.
Bot challenge
Make a visitor's browser solve a short puzzle before a path of your website loads, so that scripts and simple bots sending requests in bulk stop at the edge. Always and Adaptive, gated paths, who Adaptive lets through, the three settings, what not to gate, and what a visitor sees.
The user security model
The three system users behind your account, why the web, mail, and login identities are separate, which architectures the split applies to, and the directory layout.