Skip to content
Maran

What it manages

Everything below is built. The releases so far are betas and 1.0 is still ahead. See the releases for what each one contains.

Hosting accounts

Accounts are real Linux users. Creating one provisions its system user, home directory and the plan's disk quota on the host; suspending, reactivating and deleting reach the host too. Deleting an account also removes its databases, its file-transfer logins and its site configuration.

Websites

Static, PHP and reverse-proxy sites, with domain aliases and a document root inside the account's home. The agent renders the virtual host, writes it beside the running configuration and has the web server validate it. If validation or the reload fails, the agent rolls the file back, so one bad render cannot take down the server's other sites.

PHP, several versions at once

One php-fpm pool per account per version, each running as that account's Linux user, with the worker budget taken from the plan. Customers may change a whitelisted subset of settings. A name outside the list is refused, not silently dropped, and no customer setting can override the hardening lines above them.

SSL

Certificates ordered over ACME with an HTTP-01 challenge served from the site's own document root, custom material an operator can upload, and a renewal pass thirty days before expiry. Key material lives in a root-only store outside every account's home, because a site's PHP runs as that customer and could read a key kept inside the home.

Databases

Databases with a dedicated user each, per-plan limits, a size reading and a password reset. The panel generates the password, shows it once and never stores it, so a lost password is reset, not retrieved. Every name is prefixed with the account and every grant is scoped to one database.

File transfer

Per-account SFTP credentials served by the host's own OpenSSH, chrooted into a root-owned jail with the account's real home bind-mounted inside it. The login carries the account's own uid, gets no shell, and cannot forward ports.

FTPS is there too, for clients that need it: installed switched off, turned on by an administrator from the panel, TLS-only, with every login chrooted into its own jail.

Backups, firewall, monitoring and the journal

Backups of an account's files and databases, each restorable individually. Scheduled tasks per account, which can also be run on demand. A firewall the panel manages. Monitoring of the server's state. And an append-only audit journal of every sign-in and every change, with a screen for administrators only.

Not here yet

There is no web database manager and no browser file manager yet. Certificates are HTTP-01 only, so wildcard certificates arrive with DNS management. Mail, DNS, reseller accounts, central management of several servers and scoped API keys for billing systems are not built yet either.