⎈ Manganese

Your application online, without managing infrastructure.

An App Server is a complete server: your code, its runtime, a PostgreSQL database, a public HTTPS URL and an in-browser IDE. You create it from the Manganese interface or let your AI agent do it, without ever seeing the plumbing.

Free beta · a short call with the team to prepare your environment

The Molecule concept PaaS

A complete, self-contained application unit.

A Manganese molecule (“mgx” in the documentation) is a complete, self-contained application unit. It runs in an isolated LXC container, or a VM when needed, on bare metal, with its own compute resources, PostgreSQL database and S3 bucket.

Provisioned in 2 to 10 min from a Git repository. Each molecule contains:

  • Compute: Ubuntu LTS in an LXC container or a VM on bare metal, language-agnostic by design (Node, Python, Java, Go, PHP…)
  • Database: dedicated PostgreSQL with credentials injected as environment variables
  • Storage: S3 bucket on the provider of your choice (8 sovereign backends)
  • Built-in IDE: VS Code Server (Code Server) available from the browser
  • Automatic HTTPS: Traefik reverse proxy + public TLS certificate included
  • Git connection: token validated and repository cloned at provisioning
The App Server

Everything an application needs to run, already wired up.

Code

Your repository, cloned and built

The repository itself describes how it is built (mpy_setup.sh) and its processes (services.yml), which Manganese turns into systemd services.

Data

A PostgreSQL database

Connection variables are injected: psql connects with no parameters. A database can also be shared between several App Servers.

Network

An HTTPS URL, or your own

TLS is terminated upstream by Traefik. Your process serves plain HTTP on a single port. Add your own domain name and, if you like, Cloudflare in front.

Tools

An IDE in the browser

Code-Server on every environment, with Claude Code built in, ready to read the documentation and work on your code.

Access

Sunray Zero Trust in front

Every name served by the App Server can require passkey sign-in. You manage the addresses allowed through yourself.

Isolation

Everyone sees only their own

Each user sees only their own servers. A billing account groups the users of a company or a department.

Stacks

Generic Ubuntu, or a ready-to-use stack.

Generic templates provide a clean Ubuntu LTS (26.04 recommended, 24.04 supported), a database, a URL and the IDE, and your repository does the rest. Stack templates add the runtime, already wired up.

Node.jsPythonGoRuby on RailsStatic siteOdoo 18 / 19MuppySunray
Node.jsPythonGoJavaPHPRustRuby.NETDockerKubernetes
Good practice

One application per App Server

Install on the App Server the application and everything only it uses: Redis, Mailpit, an exporter. A service that another App Server needs goes on its own server. One test is enough: “does another server need to talk to it?”

docs.muppy.io/muppy_manganese/designing-your-mgx
Sizes

A container by default, a VM when you need one.

An LXC container starts in seconds, uses less memory, and its CPU and RAM can be resized without rebuilding. A VM has its own kernel, for kernel modules, nested virtualisation or stricter isolation.

PlanMachinevCPURAMFor
XSLXC0.51 GBa light API, a worker, a lightly used staging
MLXC or VM24 GBthe default plan
M+LXC or VM36 GBmore headroom under load or when compiling
UnlimitedLXCno capno capmeasure before choosing, or a dedicated host

Plans shipped with the generic Ubuntu 26.04 template, 40 GB disk. For your own catalogue, a full range (up to 32 vCPU, intermediate sizes included) can be generated in one go, so you never pay for eight cores when five will do. server-plans

AI agents

“Create a test server for this branch.”

The Manganese MCP server gives your agent the mgx_* methods on your own App Servers: create, deploy, resize, read and write files, run a command, drive services. On a server created by a human, destructive operations wait for your approval.

⎈ Manganese DevFleet

Development environments for a whole team, without drift.

DevFleet is Manganese for large teams: your developers, human or agent, create their dev and test environments self-service, within the rules you set.

  • Controlled catalogue: your users only see the App Definitions you publish, in the resource pools you reserve for them.
  • Role-based access: only company administrators and a server’s owner can connect to it, and Sunray enforces this in front of every URL.
  • Traceability: every command run by an agent is logged with its output and exit code.
  • On your infrastructure if you wish, with Muppy Enterprise.
Administrator setup

A host

An existing server enrolled, or an OVH instance created and enrolled in a single task.

LXD, PostgreSQL, Traefik

Installed by a single wizard on Ubuntu 24.04 or later.

The catalogue

The App Definitions your users can see.

The default pool

Where servers land when nobody chooses.

The billing account

Personal or company, with its first administrator invited by email.

⎈ Manganese ProdFleet HA

The same application, on several sites, ready to take over.

ProdFleet HA is highly available production: a pack of App Servers spread across several sites. The primary serves users and writes to the database; the standbys run the same code on an up-to-date copy, ready to take over.

Layer 1

PostgreSQL replication

A Replicated Cluster Set: the primary on site A, a synchronised standby on every other site. Each standby reads the replica on its own site.

Layer 2

The pack

A wizard declares the primary, adds the members and configures their health checks. Candidates are suggested automatically.

Kubernetes

Pack8s, multi-cloud

For your Kubernetes applications, Pack8s handles redundant deployment of your releases across several clusters and several clouds.

What Manganese does

The whole lifecycle of an App Server, from the interface or through MCP.

ProvisioningDeprovisioningResizingdev / test / staging / prod qualifiersCode-Server web IDETailscale VPNAutomatic Traefik reverse proxyCustom domainsMulti-provider git cloningCredentials vaultSSH key managementMulti-stage build scriptReusable templatesCode deploymentRemote shellFile read and writeDeclarative systemd servicesService control and logsDedicated PostgreSQLDatabases shared between serversPostgreSQL backupsS3 bucketsEnvironment variablesAsynchronous task queueMCP governance and approvalsUser management
🏛️ Manganese for the public sector

A PaaS deployed on your premises, driven by an AI you host.

With Muppy Enterprise, Manganese runs on your hardware. Its MCP interface works with any agent, including a model self-hosted in your datacentre (Mistral, Llama…): the agent provisions, deploys and reads logs without any data leaving your infrastructure.

  • Native traceability: every agent command is logged, every sensitive action waits for human approval.
  • Reversibility: standard building blocks (Ubuntu, PostgreSQL, Traefik, LXD) your teams know how to take over.
  • Swappable model: changing AI changes nothing in the infrastructure.
Real case · agent · mcp://manganese

Asalae deployed by an AI agent

Libriciel’s electronic archiving solution installed on Manganese by an agent, without a human typing a single shell command.

Real case · development environment

A Publik portal built by AI

A citizen-assistance process built by an agent on the real Publik stack (w.c.s. + combo), from infrastructure to form.

Next step

Your next application already runs somewhere. Why not here?

Show us your repository and your constraints. In 30 minutes we’ll tell you what it takes to make it an App Server, or a whole fleet.

You describe your project

Four fields, no phone number required.

We talk it through for 30 minutes

Architecture, hosting constraints, security, taking over what you already run.

You receive a written proposal

Scope, timeline and a quote, backed by the public documentation.

Prefer to try first? Try Manganese, free beta

Your project