First startup
The Initial Setup screen every self-hoster meets in the first minute: when it appears, what the one form creates, why the project name you type becomes permanent, and why a fresh installation must not sit exposed before you fill it in.
Docker
Run MFE Orchestrator Hub from the official Docker image — the all-in-one image for a single container installation, or the standard image against your own MongoDB and Redis.
Docker Compose
Install MFE Orchestrator Hub with Docker Compose, bringing up MongoDB, Redis and the application together from the official image on Docker Hub.
Terraform
Install MFE Orchestrator Hub with Terraform against Docker infrastructure as code, including the prerequisites and the variables the configuration expects.
Helm (Kubernetes)
Install MFE Orchestrator Hub on Kubernetes with the official Helm chart — configuration, secrets, persistence of the uploaded microfrontends, ingress and probes.
Enable SSO
3 items
Environment variables
Every environment variable that configures the MFE Orchestrator container: database connections, authentication providers, email services and more.
External resources
Point a self-hosted MFE Orchestrator at a MongoDB and a Redis you already run — the variables involved, the replica set requirement, and the encryption key that matters once the database is not yours.
Encryption at rest
What SECRETS_ENCRYPTION_KEY encrypts and what it deliberately does not: the threat model, the covered fields, why global variables stay in the clear, and what losing the key costs.
Telemetry
The one anonymous ping a day a self-hosted installation sends: the exact payload, when and where it goes, the full precedence of the switches that turn it off, and the endpoint that shows you what your own installation would send.