Two weeks ago, we introduced the concept of Zero-Cliff UI Composition. We shared our vision for a progressive architecture where your code remains the same whether it's a monolith or a distributed suite.

Today, we are taking the next step: UI Macroservice Decomposition.

A question I keep running into when talking to developers:

"Can we deploy modules separately and manage them independently—like microservices?"

My answer is always: "Yes—if designed that way."

But that answer deserves a much longer conversation. So here it is.

In enterprise software, the transition from a "local prototype" to a "distributed global deployment" is usually where things get messy. At Framework M, we’ve spent a lot of time thinking about how to make that transition invisible. We call it Zero-Cliff UI Composition.

Over the course of the past week, we completed a major sprint dedicated entirely to Enterprise Trust & Governance. While building cool features is fun, laying a robust legal and organizational foundation is what transforms a side project into a viable open-source ecosystem that enterprises can rely on.

Here is a look at what we've established to bootstrap the Framework M community.

We are excited to announce the pre-alpha release of Framework M, a modular, metadata-driven full-stack framework designed for building scalable enterprise applications.