Most ERP systems in the mid-market have grown over two decades: one block, one database, one update date where everything grinds to a halt at once. fabular is built differently – as a set of services on Kubernetes, with open interfaces, separate storage for different tasks, and its own security service in front.
From a few workstations to enterprise architecture
structure
The platform in five layers
Each layer can be operated, scaled, and replaced independently. This is the real difference compared to a monolith: it is not the list of functions that is different, but what happens when a part needs to grow, fails, or needs to be replaced.
Access
Everything that connects to the platform
Web interface
Angular application, the same in the office as in the customer's browser.
Mobile and scanners
Apps for warehouse, delivery, and inspection, offline-capable.
Webshop and portal
Included or connected, running on the same data foundation.
AI assistants
fabAI built in, external assistants connect via the MCP server.
Security
One gate, one permissions model
OAuth 2.1 and OIDC
fabular is its own identity provider – even for adjacent applications.
Microsoft 365 and Entra ID
Sign in with the company account, no second password.
LDAP and directory services
Existing user management stays authoritative.
Roles instead of full access
Every interface and every agent gets the same kind of permission.
Services
Functional building blocks, scaled individually
Service-oriented modules
Purchasing, warehouse, production, invoicing, CRM, and more.
fabular.API
REST over HTTPS. Whatever the interface can do, the API can too.
Pre-aggregated metrics, no overnight processing needed.
Replication
Dedicated instances per branch or shop.
Operations
Where and how it runs
Kubernetes with SUSE Rancher
In our data center or on Microsoft Azure – your choice.
Containers, not server upkeep
Roll out and scale without maintenance windows for the whole system.
New Relic
Runtime monitoring down to the individual request.
Separate environments
Test, staging, and production per customer.
foundation
Eighty percent is already in place before the project even begins
The technical foundation is only half the story. The other half is the functional side: fabular consists of a CORE with specialized solutions built on top. The CORE provides the processes that must function the same way in every business, while the specialized solution provides industry-specific expertise. Together, they cover around eighty percent of the requirements in our projects – without any custom development needed.
✓
Robust financial processes, audited according to IDW PS 880 – fabular 4.0.0 with certification from May 2026
✓
Scale communication with WELMEC conformity certification – legal-for-trade weighing including audit trail
✓
Optional operation in an ISO 27001 certified data center
✓
Specialized solutions from 25 years of project experience – batches, recipes, certificates, branch operations
✓
Quickly available because it is configured rather than built
✓
Companies adopt processes that are already proven to work elsewhere
~0%
from CORE and industry solution, no development needed
~0%
custom, via fabAI or vibecoding
0+
years of industry expertise built into the standard
0
shadow systems next to the platform
the difference
Where the features come from
With a custom-built solution, almost everything is created during the project – and must be maintained afterward. With fabular, the vast majority is already there and simply needs to be configured. These percentages are based on our project experience and are not a guarantee.
Custom-built
Custom-built
Every requirement becomes a development request – including maintenance for the entire lifetime of the system.
Built in the project0%
From the standard0%
fabular
fabular
CORE and the industry solution carry most of the load. Development only covers what actually sets your business apart.
From CORE and industry solution0%
Custom-added0%
The final 20 percent
Here – and only here – vibecoding comes into play
What truly sets a business apart isn't found in any standard. There are two ways to achieve this, both of which remain within the platform: configured fabAI assistants or extensions created directly in fabAI.
01
Dynamically configurable fabAI assistants
An assistant is given a task, the right data sources, and the permissions of a role. It then handles what would otherwise require a small add-on program – without a separate program, its own user management, or its own copy of the data.
02
Vibecoding directly in fabAI
Extensions are built through dialogue instead of a requirements document and run in the platform immediately. They access real data through existing services, with the same permissions and the same logging as any other function.
03
Built on tested ground
What matters is what this is built on: audited financial processes, a central permissions model, traceable logs. Whatever is created quickly still can't bypass the security or process layer.
04
What proves itself becomes the standard
An extension that proves generally useful is moved into the CORE or the industry solution. From there it's maintained and kept up to date – instead of remaining a one-off that nobody feels responsible for three years later.
Contact us
Ready to truly simplify your processes?
In 30 minutes, we will show you how we can solve your specific challenges—free of charge and with no obligation.
