Business M

Scale progressively from a modular business monolith to fully decoupled macroservices with plug-and-play micro-frontends.

Get Started Explore Architecture

Why Business M?

Monolith to Macroservices

Build your applications with clear boundary separation. Keep domain logic highly organized in self-contained Python modules that run inside a unified monolith or decompose seamlessly into autonomous macroservices.

Plug-and-Play MFEs

Leverage Vite Module Federation. Remotes like wms and finance build independently and compose dynamically into a premium React Host Shell (business-m).

Zero-Cliff Progression

Start simple (Level 0) using default Desk views, scale to Custom Shells (Level 2), and graduate to complex CDNs and microservices without rewriting code.

Indie vs. Enterprise Modes

Deploy on a single-node PostgreSQL instance for lightweight indie needs, or split into fully decoupled microservices behind a proxy for enterprise scale.

Dynamic Multi-Tenant Locales

Fully support per-tenant translations, local vocabulary preferences, and region-specific attributes with robust row-level security (RLS).

State of the Art Theming

A theme system built on Tamagui styled components and modern UI tokens. Automatically detects dark/light system settings with instant local storage persistence.

Architectural Philosophy

Deployment Modes

graph TD
    subgraph monolith ["Monolith Deployment (Indie Mode)"]
        direction TB
        subgraph mfe_monolith ["MFE Monolith"]
            Shell[Desk Host MFE] <--> WMS_FE[WMS Remote MFE]
            Shell <--> Fin_FE[Finance MFE]
        end
        subgraph backend_inprocess ["Backend Layer (In-Process)"]
            Unified_BE[Unified Python Monolith Backend] <--> Postgres[("Single PostgreSQL Database")]
        end
        mfe_monolith <-->|"Direct IPC / REST"| backend_inprocess
    end

    subgraph macroservice ["Macroservice Deployment (Enterprise Mode)"]
        direction TB
        subgraph mfe_shell ["MFE Shell"]
            Shell_E[Desk Host MFE]
        end
        subgraph proxy_gateway ["Proxy Router Gateway"]
            Proxy[Proxy Router]
        end
        subgraph microservice_mesh ["Microservice Mesh"]
            WMS_BE[WMS Macroservice] <--> WMS_DB[("WMS Database")]
            Fin_BE[Finance Macroservice] <--> Fin_DB[("Finance Database")]
            WMS_BE <-->|"NATS PubSub / RPC"| Fin_BE
        end

        mfe_shell <-->|"Federated Assets"| microservice_mesh
        mfe_shell -->|"API Queries"| Proxy
        Proxy -->|"Path Routing"| microservice_mesh
    end

The Progressive Framework for Business Software

Business M is powered by Framework M, which acts as a powerful orchestrator of best practices rather than a proprietary, siloed framework.

Framework M makes the progressive transition from a modular monolith to macroservices or independent microservices completely seamless by cleanly integrating industry-leading upstream foundations:

🚀 Litestar: High-throughput, modern, and asynchronous Python API framework for rapid service delivery.
🗄️ SQLAlchemy: Robust, production-grade database ORM supporting dedicated PostgreSQL architectures from day one.
🎨 Tamagui: Unified, high-performance styling and compile-time optimizations for the frontend Desk UI.
⚙️ Taskiq & NATS: Decoupled asynchronous task queue processing and microservice event-bus communication mesh.

Instead of locking engineers into proprietary silos, Framework M provides the structural blueprint, dependency-injection container, and plugin adapter patterns that enable teams to start simple and scale infinitely without rewriting core business logic.