About Fractal Forge

Fractal Forge started around 2020 as a reaction to a common frustration: Django's lack of a proper controller layer, leading to "fat views."

You know the pattern. Without a clear place for business logic, it gets tangled into views, serializers, and model methods. Files become thousand-line monsters. Testing becomes impossible. Every change risks breaking something unexpected.

Worse: junior developers learn to code by working in these production environments. They absorb the anti-patterns as "how things are done." The codebase teaches them the wrong lessons.

After learning about Domain-Driven Design and CQRS, the question became: what if the codebase could teach the right patterns instead? That's the insight behind Fractal Forge: generate a codebase that embodies good architecture, then let developers learn by working within it. Commands, events, specifications, repositories: these aren't academic concepts when they're the actual code you're writing every day.

We call this approach pro-code: the generated code is human-readable, follows standard patterns, and is fully yours. Unlike low-code platforms that hide complexity behind proprietary abstractions, pro-code means you can read, debug, and extend everything. No black boxes, no lock-in.