A Nuclet is the building block where your business ERP application lives on Nuclos 5 as pure configuration. Data model, masks, state models, rules, and menu structure belong in the nuclet. The Nuclos core stays separate. For decision-makers that is the architecture behind individual ERP: you extend processes without forking the core and without building a second system beside the ERP. In short: the nuclet carries your application. Nuclos provides the platform.

Why nuclets matter for individual ERP

Classic ERP suites often mix core and customer extension so that updates and exit become expensive. Nuclets separate deliberately: what belongs to your business sits in the configuration layer. What is platform stays Nuclos. That makes releases more plannable and keeps business logic portable.

For executives this is vendor independence in practice: the application is documentable, exportable, and not tied to an undocumented fork. For IT it is a clear deploy model: configuration as an artefact, not a patch jungle in the core. More on the platform: What makes Nuclos 5 a platform?.

What sits in a nuclet

A nuclet typically bundles:

• Businessobjekte with attributes and references
• Masks and layouts for entry and overview
• Subforms for 1:n relationships on the same mask
• State models with transitions and rights
• Rules, where low-code mechanisms are not enough
• Menu paths and further configuration objects of the business application

All of that is metadata and configuration, not a parallel codebase beside Nuclos. Anyone working with Businessobjekt, mask and layout, or state model is working in the nuclet.

Export, import, and master nuclet

Nuclets can be exported and imported between instances. That matters for development, test, and production: the same business application travels as a configuration package, not as a manual rebuild exercise. The master nuclet flag marks the leading business application in an instance. It clarifies which nuclet carries the main role when several nuclets sit side by side.

For teams that build themselves, that is the difference between “we have configuration somewhere” and “we have a transportable application artefact”. For guided delivery the same model applies: scope lands in the nuclet, not in the core.

Nuclosian and the nuclet

Nuclosian builds into the nuclet. Business instructions in the client (config mode) write configuration directly into the instance: Businessobjekte, masks, state models, rules. There is no diff before the write. A line compare with Undo appears only after a change to an existing mask or rule. No separate dev stack for day-to-day configuration. Entry points and function names are in Nuclosian: first steps.

Technical depth in the wiki: Nuclet. The wiki is the reference for configurators. This lexicon article answers the buyer question: what is the package where your individual ERP application lives?

What nuclets do not replace

A nuclet does not replace process clarification or a role model. It stores the configuration of your application. Unclear flows do not get better through clean nuclets. Equally wrong: confuse nuclets with the product offer. Nuclosian AI is the offer for business and IT. The nuclet is the configuration package inside it. Anyone who only expects chat on legacy systems does not need a nuclet. Anyone who builds ERP around processes and wants it transportable does.