Skip to main content
Documentation

The control plane for your microfrontends

MFE Orchestrator keeps versions, environments, deployments and rollbacks of a microfrontend architecture in one place — and generates the Module Federation configuration your host application needs. These pages cover both the hosted console and the self-hosted platform.

Quick start →Core conceptsOpen the console ↗
  • Hosted console or self-hosted
  • GitHub, GitLab and Azure DevOps
  • Vite and Webpack
Integration
// vite.config.js — generated by MFE Orchestrator
import { defineConfig } from 'vite';
import federation from '@originjs/vite-plugin-federation';

export default defineConfig({
  plugins: [
    federation({
      name: 'shell',
      filename: 'remoteEntry.js',
      remotes: {
        catalog: {
          external: `import('@mfe-orchestrator-hub/client').then(m => m.remoteUrl('catalog'))`,
          externalType: 'promise'
        },
        cart: {
          external: `import('@mfe-orchestrator-hub/client').then(m => m.remoteUrl('cart'))`,
          externalType: 'promise'
        }
      },
      shared: ['react', 'react-dom']
    })
  ]
});
3Git providers
3Cloud storages
2Bundlers
∞Environments
1 clickRollback
Start here

Three ways in

Depending on whether you want to try the platform, understand it, or run it on your own infrastructure.

Quick start

From zero to a deployed microfrontend — and a one-click rollback — on the free hosted console. About ten minutes, nothing to install.

Start the quick start →

Core concepts

Projects, environments, microfrontends, deployments and how they relate. The ten minutes that save you an hour later.

Read the model →

Run it yourself

Install the platform on your own infrastructure with Docker, Docker Compose, Terraform or Helm.

Installation guides →
What the platform does

Everything a microfrontend needs after npm run build

Not a bundler and not a framework — the layer that decides what is live, where, and for whom.

Generated Module Federation config

Declare which host loads which remotes and the console produces the Vite or Webpack configuration, with URLs pointing at what is deployed.

Read the docs →

Immutable deployments

A deployment is a snapshot of every microfrontend, variable and storage setting. Editing is not deploying: drafts stay drafts until you deploy.

Read the docs →

Rollback and redeploy

Reactivate a previous snapshot without rebuilding or re-tagging. The version that was live yesterday is still there.

Read the docs →

Environments and domains

As many stages as you need. Allowed domains resolve the environment per request, so one artifact can serve all of them.

Read the docs →

Runtime configuration

Per-environment variables served to the browser at boot, so the same build talks to the right API without a rebuild.

Read the docs →

Hosting options

Keep artifacts on the hub, in your own S3, Azure Blob or Google Cloud Storage bucket, or on a CDN you already run.

Read the docs →
The short path

From empty project to live microfrontend

Four steps, each with a guide. The console handles the plumbing in between.

  1. 1

    Connect a repository

    GitHub, GitLab or Azure DevOps. Your code stays with your provider.

    Read the guide →
  2. 2

    Create a microfrontend

    Pick a template and the platform creates the repository, the configuration and the pipeline.

    Read the guide →
  3. 3

    Publish a version

    Push a tag. The pipeline builds and uploads the artifact where you configured it.

    Read the guide →
  4. 4

    Deploy and integrate

    Snapshot the environment, then copy the generated configuration into your host.

    Read the guide →
Reference

Browse the documentation

Every section of the manual, one click away.

Getting started

Microfrontends

Environments

Deployments

Integration

Storage

Repositories

CI/CD

Project settings

Self-hosting

Templates ship for Vite, Webpack and Web Components. The platform itself serves whatever your build produces.

ViteWebpackWeb Components
See the templates library →
Two ways to run it

Hosted console or your own infrastructure

Hosted console

Nothing to install, always up to date

  • Sign in with email or Google SSO
  • Artifacts on the hub, or in your own bucket
  • Used throughout the tutorial
Open the console ↗

Self-hosted

Your infrastructure, your data

  • Docker, Docker Compose, Terraform or Helm
  • Bring your own MongoDB and object storage
  • SSO with Auth0, Microsoft Entra or Google
Installation guides →

Not sure where to start?

The quick start takes you from an empty account to a deployed microfrontend — and back with a rollback. If something is missing or wrong in these pages, open an issue — every page has an “Edit this page” link at the bottom.

Quick start →GitHub ↗