Did you outsource and want to repatriate? Do you manage a heterogeneous fleet with no unified control tool? Muppy Enterprise installs on-premise, centralises ops and compliance, and depends on no hyperscaler in the critical path.
8 interchangeable S3 backends, 4 DNS providers, LXD or K8s compute at your choice. Changing datacentre requires no rewrite.
Every Fabric action captures Python log + subprocess stdout/stderr in IMQ. Native traceability for compliance and post-mortem.
Muppy Enterprise installs on your infrastructure. No AWS, Azure or GCP dependency in the critical path.
Auto-maintained UFW, Sunray Zero Trust (WebAuthn passkey), Letβs Encrypt TLS, ephemeral rules with TTL for contractors.
Addon mechanism: your internal developers extend the platform without forking the core. First-class audits.
Muppy is built on an open-source framework. Your contract is solely with Muppy. β¬490/month, thatβs all.
Temporary rules for contractors and auditors become ephemeral rules with TTL that expire automatically. CIDRs from SaaS providers (Cloudflare, GitLab, Azure DevOps) refresh themselves from their official source.
Result: your UFW does not rot. No more forgotten rules. No more silent security drift.
No SSH needed to find out what happened
Logger name, level, message per entry. Visible from the interface without grep on a worker.
Raw output of remote shell commands (Fabric via SSH). Captured and stored in IMQ.
requesting_user_id + timestamp on every IMQ message. Native traceability for compliance.
Deployments, upgrades, network changes: every operation produces its journal entry.
One contract. No hidden licence.
Demo in your context. One-hour exchange to assess fit with your current fleet.