Managing an application
The application dashboard — what each card tells you, the actions in the header, and the sidebar that holds every other screen.
Once an application exists, everything you do to it happens under its own sidebar. Open Applications and pick one, and the panel swaps the server navigation for that application's: the same list of screens for every application, minus the ones its type cannot use.
The dashboard
The first screen is a summary. Nothing here is a setting — each card is a window onto a screen in the sidebar, and says enough to tell you whether you need to open it.
| Card | What it answers |
|---|---|
| Application | Type, system user, web root, PHP version, size on disk, age. The web root and the size have their own edit and re-measure buttons. |
| Security | A five-line summary — password protection, web firewall, brute-force protection, AI bots, site folder — with the count of what is on. |
| Domains and SSL | Every name that reaches the application, which one is primary, and when the certificate renews. |
| Backups | Whether this application could be restored, and when it last was backed up. |
| Database | The databases attached to the application, and what a backup would therefore contain. |
The Needs attention strip above the cards appears only when something is genuinely unprotected — an application with no backup schedule, for example.
Attaching a database does not connect it
The Database card is about backups. As the panel puts it: "What this application's backups will contain. Attaching does not change how your application connects." Your application still connects with whatever credentials are in its own configuration.
The header actions
Visit application opens the site in a new tab.
Magic Login appears for the application types that ship with an admin area — WordPress and the other one-click apps. It signs you straight into that admin area as an administrator, without you having to know or store the application's own password. It is a one-time link: it logs you in and is spent.
The … button holds the rest:
- Open files, Manage domains and Backups are shortcuts to those screens.
- Change web root sets the directory inside the application folder that the
web server serves.
/serves the folder itself;/publicand/distare the usual alternatives for framework and build output. - Pause application stops serving it without deleting anything.
- Delete application removes the application, its files and its system user.
The sidebar
Which screens appear depends on the application's type:
| Screen | Shown for |
|---|---|
| Domains & SSL | Every application |
| Deployments | Git applications only |
| Environment | Git applications only |
| Workers | Git applications only |
| Files | Every application |
| Logs | Every application |
| Backups | Every application |
| PHP Settings | Applications served through PHP |
| Password Protection | Every application |
| Web Firewall | Every application |
| AI Bot Blocker | Every application |
| Fail2ban | Every application |
| Staging Area | Every application |
| Site Clone | Every application |
| Container · Compose file | Container applications only |
A one-click application such as WordPress has no Deployments, Environment or Workers screen — there is no repository to deploy and no process to keep running. A Git application has all three, and keeps everything else.