Introduction
Overview of Fusion Framework, FMA, and cross-platform backend docs for Node.js, Python, and C# by Cipher Unit
What is Fusion?
Fusion Framework is a cross-platform backend framework built on a shared Rust core and FMA (Fusion Module Architecture).
You write class-based HTTP APIs in your preferred language. Routing, request parsing, response serialization, settings, and header helpers run in the Rust engine — language bindings stay thin and focused on developer experience.
Current framework package version in the open-source repository: 1.2.6.
Why Fusion exists
Teams often need the same HTTP semantics in more than one language. Fusion keeps one core for routing and serialization while exposing idiomatic APIs in Python, TypeScript/Node.js, and C#. Applications are composed from route modules and optional reusable packages instead of a single unstructured script.
Fusion is developed by Cipher Unit.
Language support
| Language | Status |
|---|---|
| Python | Available — pip install fusion-framework |
| TypeScript / Node.js | Available — npm i fusion-framework |
| C# | Available — NuGet Fusion-Framework (namespace FusionFramework) + fusion-ffi |
Recommended learning path
Read in this order — architecture first, then the CLI, then your language:
- Architecture overview — mental model of the stack
- Workspace and crates — core vs bindings
- FMA — how modules and packages fit together
- What Fusion is not — scope boundaries
- Fusion Tool — scaffold projects and manage environments
- Language guide: Python · TypeScript · C#
- Settings and configuration —
fusion.<env>.json,FUSION_ENV, overlays - Router · Middleware · language Config
- Reusable packages
- Best practices · Troubleshooting
Tooling
- Fusion Tool — the official CLI for scaffolding projects, managing environments, and running project commands
- Fusion Desktop — a graphical interface for managing Fusion backends on Windows and Linux
Fusion is open source under the BSD License. Learn more about the team at cipherunit.xyz.
Versioning
Fusion is a young framework, so we use a deliberate versioning strategy while the core stabilizes.
The goal is continuous improvement toward a reliable foundation for production backends.