Platform handbook · verified 8 Aug 2026

One map for the entire Mivama platform.

Understand how Portal, Frappe, Stripe, the privileged runner, Ansible, migrations, AI Studio and the shared Mivama UI system cooperate.

platform.flow

System map

Choose a surface

Each guide links business behavior to its real source code, data ownership and operational boundary.

Customer-facing Next.js UI, authenticated BFF routes, onboarding, billing, support and service control.

The Frappe control plane: customers, contracts, invoices, desired state, jobs, migrations and audit data.

A root runner applies versioned desired state through strict Ansible playbooks and per-tenant isolation.

A customer connector, upload gateway and privileged import worker perform previewed two-pass WordPress transfers.

An isolated development copy uses the customer's own Codex account, with human approval before deployment.

Schedulers, reconciliation, backups, cancellation retention, decommissioning and incident runbooks.

Open the live Storybook with every real component, variant, theme, density and interactive state from the shared UI repository.

Commercial state, users, legal acceptance, services, migrations and jobs live in Mivama Core.

Privileged processes claim narrow jobs; public applications never receive unrestricted host access.

Versioned desired state, confirmations, backups, health checks, retention and audit events guard changes.