Maurice PaaS
A self-hosted deployment panel for one powerful server, built on rootless Podman.
Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
Self-hosted deployment panel for a single bare-metal server, built on rootless Podman, Quadlet and systemd. Isolated workspaces per Unix user, nothing published by default, plan/apply for every change, Caddy edge, S3 backups, MCP for agents.
Maurice (friends call it Marik) gives you the convenience of Coolify on a single bare-metal server where blockchain nodes, ClickHouse, databases and application services live side by side. It is not Docker with a different runtime underneath. It is built around what Podman does well: rootless isolation by Unix user, Quadlet and systemd as the lifecycle engine, auto-update with rollback, native secrets.
Status: Alpha. Workspaces, services from images or Dockerfiles, secrets, plans with apply, logs, live stats and a web UI work end to end on a real Podman host. Not for production yet: no proxy, TLS, auth or backups before MVP. The Alpha guide shows everything that works; progress is on the task board.

systemd --user; deleting one leaves nothing behind.podman secret, never written to units or logs.127.0.0.1 unless told otherwise, and host port clashes across workspaces are refused.marik / maurice CLI with the same capabilities.
sudo install -m 0755 maurice /usr/local/bin/maurice # from `cargo build --release`
sudo ln -sf maurice /usr/local/bin/marik
sudo maurice host prepare # PostgreSQL, keys, journald, maurice.service
sudo systemctl enable --now maurice # panel on 127.0.0.1:7700
marik workspace create shop && marik plan apply <plan-id>
Full walkthrough, CLI reference and known limits: the Alpha guide.
User / Claude Code / Telegram
│
▼
UI + API + MCP tokens scoped read / plan / apply
│
▼
Control plane generates Quadlet units, change plans, Caddy config
│
▼
Agent ── machinectl ──▶ ws-<project> rootless Podman + systemd --user
│ ├─ [email protected] stateless, blue-green
│ ├─ postgres.service stateful, restart + backups
│ └─ <project>.network DNS by service name
▼
Caddy admin API domain ──▶ 127.0.0.1:<port>, TLS, graceful switch
Files on disk stay the source of truth: every unit the panel writes can be read,
diffed and applied with plain systemctl. The panel is a convenience layer, not
a runtime dependency.
Scope, done criteria and risks for every stage are in the Roadmap.
Rust for the control plane and agent, one static binary · Podman 5 with crun,
netavark and aardvark-dns · systemd + Quadlet · PostgreSQL · ConnectRPC API ·
SolidJS SPA embedded in the binary · Caddy · VictoriaMetrics and VictoriaLogs ·
restic + rclone · Ubuntu 26.04 LTS host, Fedora and Debian 13 as secondary targets. Every choice
has a record in docs/decisions/ and the reasoning in the
Technology Stack.
docs/: architecture decision records and working notes, versioned with the code. Opens as an Obsidian vault.Apache 2.0. Maurice stands on the shoulders of Coolify, Rookery, Podman, Caddy and systemd.
Self-hosted deployment panel for a single bare-metal server, built on rootless Podman, Quadlet and systemd. Isolated workspaces per Unix user, nothing published by default, plan/apply for every change
Visão geral
Self-hosted deployment panel for a single bare-metal server, built on rootless Podman, Quadlet and systemd. Isolated workspaces per Unix user, nothing published by default, plan/apply for every change, Caddy edge, S3 backups, MCP for agents.
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Maurice PaaS roda localmente via stdio.
Última verificação: 2026-10-27. Self-hosted deployment panel for a single bare-metal server, built on rootless Podman, Quadlet and systemd. Isolated workspaces per Unix user, nothing published by default, plan/apply for every change, Caddy edge, S3 backups, MCP for agents.