Solutions
Why Fuuz
Industries
Resources
Partners
Company
Accelerators
An accelerator is a pre-built, configurable starting point that covers the bulk of the common needs in its domain, such as manufacturing execution or warehouse management. Install it into Fuuz, see a working operating model from day one, and shape it to how your plants actually run.
Every accelerator, with its version, release notes and code, is published at accelerators.fuuz.com.
A jump start, not a finished answer
Understanding the difference up front is what makes an accelerator succeed. If your requirements go beyond what one covers, that is expected, not a shortcoming.
What it is not
What it is
Application accelerators
Complete applications with data models, flows, screens and documents working together. Several are also published as modular packages, so you can read them module by module and install only the parts you need.
Manufacturing execution
Shop-floor production execution, published modular, exploded to module and component, so you can read it module by module and install only the parts you need. Browse the code.
Warehouse management
A complete warehouse management application, from the dock to the shipment. Browse the code.
Warehouse management
Warehouse management as an installable package, also published modular, so you can install only the modules you need. Browse the code.
Machine monitoring
Workcenter state, downtime and OEE from connected equipment. Browse the code.
Building blocks and run-it-now
Utility
The complete SI and Imperial unit library with conversions, or either set on its own.
View in catalogRun it now
An OPC UA plant, a time-series historian and a Fuuz-shaped GraphQL API in one docker compose up.
View in catalogRun it now
A one-command Docker deployment of the Fuuz Device Gateway for evaluation.
View in catalogLooking for ERP, carrier or other integration packages? They are on the Connectors page.
How they are made
An accelerator is Fuuz platform components, packaged. Nothing in it is hidden or proprietary to the package.
The records the application keeps, such as work orders, containers, inventory and quality specifications. The shape of the domain.
The logic. A request arrives from a button, queries fetch supporting records, rules branch, a mutation writes and a response returns.
What operators and administrators use: control panels, tables, forms, dialogs and management screens.
Printable output such as labels, manifests and reports. The paper the floor still runs on.
Components grouped by function, such as receiving, picking or quality. A module is the unit you reason about.
All of it ships as one .fuuz archive. Modular versions unpack it module by module, so it can be read and compared before anything is installed.
Why accelerators work this way
Every Fuuz accelerator, from MES to WMS, is built on the platform with the same tools our customers and partners use. That changes what happens after go-live.
Rigid packaged software
Fuuz accelerators
Why it matters
Give business users the tools to build functional solutions for themselves, inside the roles, reviews and release path IT sets.
When plants extend the platform instead of working around it, the business stays aligned with the enterprise operating model, plant by plant and acquisition by acquisition.
Processes, data and the applications themselves stay in one platform, so AI works from the full picture of how the company runs and helps it pull ahead of competitors.
Who makes them
Accelerators are published by MFGx, the Fuuz platform team, by certified partners, by customers, and by anyone with access to a Fuuz environment. They are all built with the same low-code and pro-code tools every Fuuz customer gets.
That is the difference from packaged software. Your team or a partner can extend any accelerator, or package what you built and publish it as an accelerator of your own. Support, warranty and maintenance terms differ by publisher, and each accelerator's guide states which apply.
Three tiers of scope
How they are deployed
1
Read the technical overview and build reference. Where an accelerator is published modular, read the modules themselves, or run it locally with Docker.
2
Each guide carries a discovery questionnaire. A no is not a defect: it marks where standard scope ends and what to scope as custom work.
3
Import the package into your build tenant. Its flows, models and screens become your own configurable copies.
4
Add site structure, products, processes and access. Walk one real transaction through end to end, then release through QA to production.
How they are governed
Every published accelerator carries a version, release notes and its source code, so you know exactly what you are installing.
Beta marks an accelerator that is still pre-production. Use it to evaluate and plan, not to run production.
Installed copies never change under you. Later versions are applied deliberately, through the same versioned, tested and packaged release path as everything else.
Nothing published carries a service level agreement on its own. An accelerator becomes a supported deliverable once Fuuz services or an approved partner implements it.
No accelerator for your exact need?
Start from the accelerator that covers the most of what you need, and configure or extend the rest on the platform.
Build from scratch with low-code, pro-code or your own IDE and AI tools, on the same data model and governance.
How building worksCertified partners and Fuuz services scope and build what sits outside an accelerator's standard scope.
Find a partnerPackage what you built and reuse it across your plants, or share it with the community as an accelerator.
See the catalogQuestions
Accelerators are starting points for building on the Fuuz platform, published openly with their code. Talk to us about which ones fit your plan.
No. Installation forks the accelerator into your environment as your own copies. When a new version is published, you choose whether and when to apply it, through your own release process.
Yes. That is the point. Configure and extend it on the platform, and your changes go through the same versioned lifecycle as everything else.
No. Some customers prefer to define their own operating model from scratch. The accelerator is there to make that an informed choice.
Yes. Read the code and modules in the catalog, run the Docker-based simulators, or download the Fuuz In-House trial and run the whole platform on your own machine.
On accelerators.fuuz.com. Each accelerator lists its current version and links to its release and code.
Get started
Tell us what you need to run. We will recommend the accelerators that fit and what to build around them.
Prefer to talk? Call 1-877-801-FUUZ (3889)