Server installation profiles
A profile prepares a software stack on an existing server. It differs from the template used when creating a VPS: choose it later in the server interface.
Available profiles
The application stack in the table means Nginx, the selected PHP branch (CLI and FPM), Composer, Node.js 24, npm for Node.js 24, Redis and Supervisor.
| Profile | Installed software | Default database |
|---|---|---|
| Application server · MySQL | Application stack + MySQL | MySQL 8.4 |
| Application server · MariaDB | Application stack + MariaDB | MariaDB from Ubuntu repositories |
| Application server · PostgreSQL | Application stack + PostgreSQL | PostgreSQL 18 |
| Application server · MongoDB | Application stack + MongoDB | MongoDB 8.0 |
| Web server | Application stack without a database | None |
| MySQL server | MySQL only | MySQL 8.4 |
| MariaDB server | MariaDB only | MariaDB from Ubuntu repositories |
| PostgreSQL server | PostgreSQL only | PostgreSQL 18 |
| MongoDB server | MongoDB only | MongoDB 8.0 |
| Nginx | Nginx only | None |
| Redis | Redis only | None |
The Web server profile also includes PHP, project tools, Redis and Supervisor. For just the web server without this stack, select Nginx. Install Apache, Memcached and other runtimes individually through services; they are not included in these stacks.
Version options
- PHP for application profiles: 8.2, 8.3, 8.4, 8.5 or 8.6 preview. The form starts with PHP 8.5; preview requires explicit permission. This choice also applies to the Web server profile.
- MySQL: 8.0, 8.4 or 9.7; selecting the profile defaults to 8.4.
- PostgreSQL: 16, 17 or 18; defaults to 18.
- MariaDB: the version available in the server's Ubuntu repositories.
- MongoDB: 8.0 for supported Ubuntu 24.04 amd64.
The database form only offers versions of the selected profile's engine. The application stack fixes Node.js to branch 24; this form does not switch it to 22 or 26. Exact patch releases are resolved during installation according to availability.
Install a profile
- Open the profile card in the server interface and choose profile configuration.
- For an application stack, select PHP and allow its repository or preview if needed.
- Select a profile.
- For database profiles, choose the database version and allow the official repository if needed.
- Enter an application database user and password; the default database is optional.
- Confirm installation and follow individual steps. Check both the profile and service inventory when complete.
Database usernames use lowercase letters, digits and underscores, start with a letter and have at most 32 characters. Passwords contain 12–255 characters without control characters. Optional database names follow the same format with at most 63 characters. Reserved system names cannot be used.
New database credentials are stored encrypted. You can reveal verified stored credentials for the corresponding database service when authorized. This workflow does not automatically overwrite existing accounts.
Progress and retry
Installation processes services individually. Follow waiting, running and verification states; also review any adopted existing services. For failure, check service state before continuing. For an unverified outcome, verify the original operation first.
Prepared software is not yet a deployed application: configure a project, its environment, web server and HTTPS afterwards.
Remove or change a profile
A server can have one active managed profile. Review dependencies and prepare a backup before changing it.
Removal uninstalls only services created by that profile. Data files and adopted services remain; this is not an operating system reset. If the server has recorded projects and potentially removable services, bulk profile removal is blocked and services must be addressed individually.
For historical profiles, the interface may offer record conversion after refreshing detection and verifying database credentials. Conversion itself installs no packages. User-added servers may also offer discovery of already installed services.