One root process
The panel runs unprivileged. A small Rust daemon holds root, and its contract has no operation that runs a program you hand it.
Source-available hosting panel
Manage websites, PHP versions, SSL, databases, file transfer, backups and the firewall from a browser. Every customer gets a cabinet, and your billing system gets an API.
curl -sSL https://get.maran.innovayse.com | sudo bashOne command on a fresh server. Every check runs before anything changes.


The panel runs unprivileged. A small Rust daemon holds root, and its contract has no operation that runs a program you hand it.
A domain is validated as a domain and never escaped into a command line, so it has no newline that could end one directive and start another.
Every account is a system user with its own home, its own php-fpm pool under its own uid, and its own quota.
A provisioning API creates, suspends and deletes accounts, so a billing system can run hosting without a person in the loop.
Static, PHP and reverse-proxy sites with aliases. The agent validates every rendered vhost with the web server itself and rolls it back if the reload refuses.
ACME with an HTTP-01 challenge, uploads for custom material, renewal thirty days before expiry, and keys in a root-only store outside every home.
A database and a scoped user per account, chrooted SFTP carrying the account's own uid, per-plan limits on both.
Backups of files and databases that restore one at a time, a managed firewall, and monitoring of the server's own state.
An append-only record of every sign-in and every change, on a screen only administrators can open.
The installer verifies a release's signature before it installs anything. A panel backup holds the database, keys and licence in one encrypted archive that restores on a clean server.
Run one command on a fresh server. Preflight checks the distribution, memory, disk and ports, and reports all problems at once instead of one per run.
The installer prints a link and a one-time setup token for creating the first administrator. Nothing else can create one, and the token stops working once an administrator exists.
The panel provisions the account on the host as a real Linux user with its home, its pool and its quota. Then you hand its cabinet to the customer.
This split is the product's main design decision, and everything else on this page follows from it.
maran-apiThe panel
maran-agentThe only root process
has root
thenPostgreSQLThe panel's data
The panel asks the agent for named operations with typed, validated arguments. No operation runs a caller-supplied program, and no shell string passes between them. The list of things the root process can be made to do is finite, written down and open to review.
One command on a fresh server of any of these, on x86_64 or aarch64.
Ubuntu
Debian
AlmaLinux
Rocky Linux
Red Hat Enterprise Linux and Oracle Linux 8, 9 and 10 are accepted too, since all four enterprise rebuilds run the same code path. The installer refuses any other distribution instead of guessing, because it knows the package layout and service names of each supported family.
Maran is published as a beta, and the 1.0 release is still ahead. Here is what exists and what does not.
Everything absent is absent on purpose and named here, rather than discovered after the install.
Maran is published under the Business Source License 1.1 by Innovayse LLC, and converts to Apache 2.0 on 29 August 2030. The date is written into the licence rather than promised.
Four properties of the code. Each is either true or not, and you can check each by reading the source.
A domain is validated as a domain (letters, digits, hyphens and dots) and never escaped into a command line, so it has no newline that could end one directive and start another.
Every write is rendered, renamed into place atomically, then checked by the service itself. If validation or the reload fails, the file is rolled back.
The daemon reads the peer credentials from the socket before it considers an operation, so it knows which process is on the other end instead of trusting what that process says.
A request for another account's resource gets "not found", never "forbidden", because "forbidden" would confirm the resource exists.
If your billing system cannot drive the panel, somebody has to operate it by hand. The account lifecycle is four calls, the same ones the panel's own screens make. Scoped API keys are not built yet.
The account, its Linux user, its home and its plan's quota are all provisioned on the host, not just recorded in a table.
Suspension is a state of its own, not a deletion. The data stays, the sites stop, and reactivating restores everything as it was.
When the plan changes, the server follows: the quota, the worker budget and the limits all move with it.
Databases, logins, the jail and the system user are all removed. If any cleanup step fails, the deletion stops instead of leaving an orphan behind.
Every panel claims to be multi-tenant. What matters is where the separation lives, and here the operating system enforces it, not a condition in a query.
Each account is a system user with its own uid, its own home and its own quota. The kernel enforces the boundary, not the application.
Customers sign in to their own area with their own two-factor authentication. They see their sites, databases and backups, and nothing else.
A request for a neighbour's resource gets "not found", never "forbidden", because "forbidden" would confirm the resource exists.
The audit journal is append-only and records every sign-in and every change, so an administrator can see what happened and when.
Multi-tenancy has been part of the product since the first release, so it suits several kinds of operator.
A cabinet per customer, plans that cap what an account may use, and a provisioning API that lets a billing system create accounts without a person in the loop.
Client sites on one server, each its own Linux user with its own quota and PHP version, and an audit journal that answers who changed what.
Everything a single machine needs, installed with one command from signed release artefacts.
The newest release and the latest post about how Maran is built.
Maran 1.0.0-beta.4: runtime limits, a panel certificate and panel backup
Runtime limits per plan, a free-space floor, a trusted panel certificate, panel backup and restore, backup alert mails and clock-drift warnings.
19 September 2026Why the agent takes no shell commands
The design decision that shaped Maran: a root daemon that accepts typed operations and never a shell string, and what that choice costs.
The short answers. The rest are on the questions page.
The architecture, the contract between the panel and the agent, and what the installer does to a server, all written out in full.