Muppy Enterprise · self-hosted

The whole platform on your premises. We stay outside.

Muppy Enterprise is the edition of Muppy deployed in your own infrastructure. Your applications, databases and secrets never leave your perimeter. We only come in at your request, and access expires on its own.

Muppy Enterprise contract · installation and updates carried out remotely by our teams

Standard
1

server or VM

High availability
2

servers in 2 availability zones

Minimum per server

4 CPU · 12 GB RAM · 75 GB SSD · Ubuntu LTS

What you get

The same tools, inside your perimeter.

Odoo

Odizy, from dev to prod

Odoo servers from demo to production, each with its own Traefik, backups and monitoring.

Self-service

Manganese for your teams

Your users create their own App Servers, on your hosts, within the rules you set.

Kubernetes

MicroK8s or your clusters

MicroK8s installed and operated on your hosts, or your existing managed clusters, driven through their API.

Anywhere

Any datacentre

Managed workloads can live with any hosting provider or in your datacentre, across several sites.

Extensible

Your own addons

Write your own Muppy tasks and applications. Your addons’ secrets are encrypted by Muppy Vault with a single declaration.

Portable

Local, as an option

With the dedicated option, the whole platform also runs locally from the Docker images, all features included.

For your CISO

Every flow, its port, its direction. Published.

All flows between hosts are encrypted (TLS or SSH), and all start from inside your perimeter, with three exceptions: your users’ access, the load balancer’s health check and on-demand support.

FlowProtocol / portDirection
Users → your load balancerHTTPS :443inbound
PostgreSQL standby → primaryTCP :5432, TLSinternal, opened by the standby
Muppy Bootstrap → your serversSSH :22, keyinternal
Muppy Bootstrap → exportersHTTP :9100 / :9187internal, every minute
Backups → S3 storageHTTPS :443outbound, scheduled
Telemetry → oursbl.euHTTPS :443outbound only, no application content
oursbl.eu support → BootstrapSSH :22, allow-listed IPat your request, rule that expires
Failover

The load balancer polls /inouk_health_check on both servers and only sends traffic to the primary. After a promotion, the responses swap and traffic follows, with no DNS change.

oursbl.eu

No permanent connection, no permanently open access, no application data. The support firewall rule carries an expiry date and disappears on its own.

full diagram and draw.io file: docs.muppy.io/muppy_enterprise/data-flows

Security

Three locks we recommend from day one.

Sunray in front of the instance

Every name served by the platform asks who the visitor is before responding.

Muppy Vault enabled

SSH keys, tokens and passwords encrypted in the database. A stolen backup no longer gives away your access.

Patches tracked

Security fixes are published with their severity. For a critical fix, your contact is notified as soon as it is published.

Next step

Your CISO has questions. We have the diagrams.

Book 30 minutes to size your installation: number of hosts, availability zones, network constraints.

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.

Prefer to try first? Try Manganese, free beta

Your project