Skip to content
Maran

Source-available hosting panel

A hosting control panel that keeps root to itself

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 bash

One command on a fresh server. Every check runs before anything changes.

The system status page of a running Maran panelThe system status page of a running Maran panel
The system status page of a running panel, in your theme.

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.

No shell strings

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.

Real Linux users

Every account is a system user with its own home, its own php-fpm pool under its own uid, and its own quota.

Built for billing

A provisioning API creates, suspends and deletes accounts, so a billing system can run hosting without a person in the loop.

What it manages

Websites and PHP

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.

SSL that renews itself

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.

Databases and transfer

A database and a scoped user per account, chrooted SFTP carrying the account's own uid, per-plan limits on both.

Backups and firewall

Backups of files and databases that restore one at a time, a managed firewall, and monitoring of the server's own state.

An audit journal

An append-only record of every sign-in and every change, on a screen only administrators can open.

Signed releases

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.

From a bare server to a hosting account

The installer runs its checks on the distribution, ports, memory and disk before it writes anything, and a refused check stops it untouchedThe installer runs its checks on the distribution, ports, memory and disk before it writes anything, and a refused check stops it untouched
  1. Install

    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.

  2. Open the one-time link

    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.

  3. Create an account

    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.

Three processes, and root belongs to one of them

This split is the product's main design decision, and everything else on this page follows from it.

  1. maran-api

    The panel

    Runs as
    an unprivileged system user
    Holds
    every piece of business logic, and the only database connection
    then
  2. maran-agent

    The only root process

    Runs as
    root
    Holds
    no business logic and no database, only the files it renders for the host

    has root

    then
  3. PostgreSQL

    The panel's data

    Runs as
    its own user
    Holds
    accounts, sites and the audit journal, reached over a unix socket with no TCP port

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.

Runs where your servers already run

One command on a fresh server of any of these, on x86_64 or aarch64.

See the requirements
  • Ubuntu

    • 22.04 LTS
    • 24.04 LTS
    • 26.04 LTS
    • x86_64
    • aarch64
  • Debian

    • 12
    • 13
    • x86_64
    • aarch64
  • AlmaLinux

    • 8
    • 9
    • 10
    • x86_64
    • aarch64
  • Rocky Linux

    • 8
    • 9
    • 10
    • x86_64
    • aarch64

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.

Where it is today

Maran is published as a beta, and the 1.0 release is still ahead. Here is what exists and what does not.

Built and running

6
  • Accounts as real Linux users, with quotas, suspend and delete that reach the host
  • Static, PHP and reverse-proxy websites, with validated configuration that rolls back on failure
  • Several PHP versions side by side, one pool per account per version
  • SSL over ACME, renewed thirty days before expiry, keys outside every home directory
  • Databases and SFTP logins with per-plan limits and one-time passwords
  • Backups, scheduled tasks, a managed firewall, monitoring, and an append-only audit journal

Not in it yet

4
  • No web database manager and no browser file manager yet
  • Certificates use HTTP-01 only, and wildcards will arrive with DNS management
  • Mail, DNS, reseller accounts and multi-server management are not built yet. The panel's menu already shows their place, marked Coming soon
  • Scoped API keys for billing systems are not built yet

Everything absent is absent on purpose and named here, rather than discovered after the install.

Source-available, and yours to run

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.

Read the licence
A timeline: Business Source License 1.1 today, converting to Apache 2.0 on 29 August 2030, when every restriction endsA timeline: Business Source License 1.1 today, converting to Apache 2.0 on 29 August 2030, when every restriction ends
  • Install it and host your own customers on it, in production, at no cost
  • Read, modify and contribute. The source is available, and contributors keep their copyright
  • You may not offer Maran itself as a managed control panel service to third parties
  • You may not resell or relicense it as your own commercial product

Safe by construction

Four properties of the code. Each is either true or not, and you can check each by reading the source.

  • No shell strings

    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.

  • The server validates its own configuration

    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 agent checks who is asking

    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 missing row answers 404

    A request for another account's resource gets "not found", never "forbidden", because "forbidden" would confirm the resource exists.

Three hosting accounts on one server, each with its own Linux user, php-fpm pool, home directory and quota, and none able to see the othersThree hosting accounts on one server, each with its own Linux user, php-fpm pool, home directory and quota, and none able to see the others
How a configuration file is written: rendered to a temporary file, renamed into place, validated by the server itself, then reloaded or rolled backHow a configuration file is written: rendered to a temporary file, renamed into place, validated by the server itself, then reloaded or rolled back

Built to be sold hosting on

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.

A billing system calls the Maran API to create, suspend, resize and terminate accounts without a person in the loopA billing system calls the Maran API to create, suspend, resize and terminate accounts without a person in the loop
  • Create

    The account, its Linux user, its home and its plan's quota are all provisioned on the host, not just recorded in a table.

  • Suspend

    Suspension is a state of its own, not a deletion. The data stays, the sites stop, and reactivating restores everything as it was.

  • Resize

    When the plan changes, the server follows: the quota, the worker budget and the limits all move with it.

  • Terminate

    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 customer gets their own login

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.

  • A real Linux user

    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.

  • A cabinet of their own

    Customers sign in to their own area with their own two-factor authentication. They see their sites, databases and backups, and nothing else.

  • Asking for more answers 404

    A request for a neighbour's resource gets "not found", never "forbidden", because "forbidden" would confirm the resource exists.

  • Every action is recorded

    The audit journal is append-only and records every sign-in and every change, so an administrator can see what happened and when.

One administrator sees every account, while each of three customers has their own login, sites and databases and sees nothing elseOne administrator sees every account, while each of three customers has their own login, sites and databases and sees nothing else

Who it is built for

Multi-tenancy has been part of the product since the first release, so it suits several kinds of operator.

  • Hosting businesses

    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.

  • Agencies and studios

    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.

  • One server, one owner

    Everything a single machine needs, installed with one command from signed release artefacts.

What is new

The newest release and the latest post about how Maran is built.

Questions people ask first

The short answers. The rest are on the questions page.

What is Maran?
A web hosting control panel for Linux servers. You install it on a server and manage websites, PHP versions, SSL certificates, databases, files, backups and the firewall from a browser, with a separate cabinet for every hosting customer and an API a billing system can drive.
Is it free?
The panel is source-available under the Business Source License 1.1 and free to self-host, including hosting your own paying customers on it. The licence forbids offering Maran itself as a hosted control panel service and reselling it as your own product. Commercial modules are planned to be distributed separately with a licence key; none ships yet and no prices are published.
Can I use it in my hosting business?
Yes. Running it to host your own customers is explicitly allowed by the licence, and multi-tenancy has been part of the product since the first release.
Which distributions does it support?
Ubuntu 22.04, 24.04 and 26.04 LTS, Debian 12 and 13, and AlmaLinux, Rocky Linux, Red Hat Enterprise Linux and Oracle Linux 8, 9 and 10, on x86_64 and aarch64. The installer refuses any other system instead of guessing at its package layout. AlmaLinux 8 is the oldest supported release, because its glibc is the oldest the agent is built against.

Read how it is built before you trust it with root

The architecture, the contract between the panel and the agent, and what the installer does to a server, all written out in full.

Open the documentation