Nuclos 5 is the platform for individual ERP: it maps your processes instead of pressing your business into ready-made module packages. For executives and IT that means three concrete things. First, you steer scope and expansion by process, not by license boundaries. Second, source code and data stay in your hands (AGPL, no per-user licenses). Third, AI supports modeling and configuration under governance, not as a loose chat layer on running operations. Anyone evaluating Nuclos 5 is not checking feature lists. They are checking whether architecture and delivery model fit process ownership, planability, and vendor independence.

What “platform for individual ERP” means in practice

Individual ERP means: the system follows the real process, not the other way around. Standard suites organise work by modules (inventory, finance, CRM), often with breaks at module boundaries. Nuclos 5 models records end to end: data model, screens, rules, and workflows hang on the same business object. Changes to the process change the configuration, not the module invoice.

That is the architecture decision behind Process structure instead of module structure. For decision-makers the benefit counts: less parallel maintenance in spreadsheets, fewer media breaks, earlier usable partial results. Productive entries run through guided delivery (Nuclos Enterprise) or through the self-build path (Nuclos Workspace). Both use the same platform.

Low-code as a way of working, not a marketing label

The low-code layer maps processes, data model, workflows, and screens onto metadata. Core business logic can be adapted without developing every feature as a classic large project. Business-near roles can co-design. IT keeps governance, approvals, and operations.

Low-code does not replace requirements clarification. Unclear processes are only digitized as chaos. Anyone who clarifies scope before the build (prototype, Spec Workshops, or a precise requirements document) keeps fixed price and timeline reliable. More context: Low-code in ERP.

Open source and data ownership

Nuclos is under AGPL: full source insight, no per-user licenses, no module lock-in through proprietary extensions. Code and data belong to the customer. Maintenance by own teams or partners remains possible. Exit options stay open.

That distinguishes the platform from proprietary suites and from open-source offers that effectively force an enterprise license at the first real customization need. Deeper reading: Open-source ERP without vendor lock-in. For executives this is the vendor-independence pillar: decision freedom stays with you after go-live as well.

AI under governance: Nuclos Workspace, Nuclosian, and MCP

AI in Nuclos 5 runs through Nuclos Workspace. The lead story for business and configuration is Nuclosian in the client (config mode, superuser): sparring, validation, and governed writes with diff and confirmation. Nuclos MCP is the tool layer for developers and for custom clients, apps, and integrations. The same tool layer, two entry points. No uncontrolled chat over operational records without approval.

Reads and writes happen under governance: no LLM keys in the browser, act as the logged-in person, audit. That is deliberately not an AI chat layer on arbitrary legacy systems. Protocol details: What is MCP?. Offer: Nuclos Workspace.

Operations: cloud and on-premise on the same platform

Both operating models are possible: managed hosting in Germany or on-premise on your own infrastructure. Same platform, different operating form. Cloud fits a fast start with little server effort. On-premise when local data residency or industry requirements demand it.

Prices and packages are on the offer pages. Entry paths and funnel framing: Which Nuclos entry path fits?. Guided first delivery with fixed price and agreed scope: Nuclos Enterprise.

How decision-makers check fit

Four check questions are enough for the first decision:

1. Process first: Does the platform map your core process without module force?
2. Planability: Are scope, price, and date fixed before start (for example via prototype or Spec)?
3. Independence: Do source code, data, and exit stay with you?
4. AI governance: Does AI act in configuration and development with diff and approval, or as uncontrolled runtime access?

If these four points fit, Nuclos 5 is a solid candidate as a platform for individual ERP. Detail depth then comes in prototype, specification, or Workspace pilot, not in a feature brochure.