A self-hosted business suite built on
asd. 12+ integrated services — ticketing, project management, ERP, communication, BI, automation, monitoring — with shared SSO, atomic releases, and an AI-friendly operator surface. Manifest-driven, English-first documentation.
Status: documentation rewrite in progress under ticket #3932. The pages under
/pma/*are being built fresh in English with the proven scenario-format pattern. Legacy Dutch docs still live at/projects/asd-pmauntil the rewrite lands. See/structurefor the full map.
You describe each service in a manifest.yaml. The framework reads
those manifests and stands the whole stack up — containers running,
routes configured, SSO wired, backups taken, health checks live. One
just release-run TICKET deploys + verifies + can roll back atomically.
The MCP gateway exposes every operation to AI agents the same way it
exposes them to humans.
Replace the SaaS stack — Salesforce / Atlassian / Slack / SAP cost
€1,800-5,000 per month for a small team. PMA's 12+ services cover
the same surface for €0 in licensing (you bring infrastructure).
Operate without a vendor support ticket — every incident leaves
a machine-readable recovery playbook. The next incident is shorter.
just release-run and just release-revert are the only deploy
verbs — everything else is a sub-script.
Run with AI agents as first-class operators — the MCP gateway
gives an agent a real Redmine login, a Zammad seat, write access to
every service. Every operation has a just recipe; every command
emits structured output. The AI era didn't catch PMA by surprise —
it was designed for it.
| Section | What it covers |
|---|---|
| Learn | The simple-to-complex ladder. Install → multi-service stack → SSO → backup → release → multi-environment prod. |
| Cookbook | Single-problem recipes — install a new service, migrate from a SaaS, integrate existing Authentik, debug a failed release, run PMA as a cooperative. |
| Compared | Honest head-to-head with Cloudron, Yunohost, and the SaaS stacks PMA replaces. |
| Services | Per-service docs — what each of the 12+ services is, how it's configured, how to use it within PMA. |
| Reference | Schemas (manifest, services.yaml), CLI command reference, glossary. |
| Internals | How PMA works — architecture, package system, bootstrap, MCP gateway, recovery playbooks, install skill, release orchestrator, contract system. |
asdPMA's networking, tunnels, reverse proxy, and dev-time tools all
come from asd. PMA adds the service layer (manifests for
12+ services), the integration layer (SSO + n8n flows + Superset
aggregating BI), and the operations layer (atomic releases, recovery
playbooks, MCP gateway). For the underlying tooling: see the
/asd section.
While this rewrite is in progress (ticket #3932), the original
Dutch PMA documentation stays live at
/projects/asd-pma. It has a lot of accumulated
operational knowledge; nothing's deleted yet. Once /pma/* ships
complete, the legacy paths get redirected and the original content
archives to pma-docs-archive per Rule 15.