Real cases
Custom apps on Business Central
We don't just build extensions inside Business Central: we build the apps around it too - tablet clients on the shop floor and in the warehouse, a desktop console that governs licensing, cloud services that tie them together - and, when it calls for it, whole products beyond BC too. Four real examples, one way of working.
Rieco: a bespoke shop-floor app, on top of MES and Processing Charge
A Flutter client we developed for the shop floor, sitting on two standard Business Central products that talk to each other on their own.
The setting. Rieco System makes precision tools. Some orders are simple machining jobs: few operations, but they still need real-time shop-floor tracking and correct costing - and the operator, at the machine, must not waste time or get it wrong.
The app we developed. For Rieco's shop floor we built Working Phases, a Flutter tablet app: the operator picks their machine and from there sees only that machine's operations (with only the allowed actions): no long lists, no wrong choices. They can keep several phases open on the same machine, and with a tap does Start / Pause / Finish and declares pieces and scrap. It is bespoke development in full - the client is ours - but it sits on a clean contract: the standard AL MES Web APIs (Azure AD, applibra/Mes namespace), which support both models - by machine or by operation, even per user. At Rieco we chose by-machine because that's how they work: no needless complication, no fragile integrations.
The two products underneath. The heavy lifting is done by two standard products: AL MES (in AppSource certification) posts progress, output and capacity to Business Central's standard journals; AL Processing Charge takes MES's real time and cost and turns them into the machining charge, automatically. Configured for Rieco, not rewritten.
The point. The right boundary at work: the tablet is just the shop-floor face (the rules live in BC); MES measures, Processing Charge charges; each does its own job and they exchange data over the bus. A bespoke app on top of products that compose - neither a monolith nor a throwaway project.
The result. Shop floor and ERP that talk to each other: real progress, times and costs straight into Business Central, in real time and without back-office re-keying.
Discover AL MES Discover AL Processing Charge
Zanin 1895: bulk spirits, and a bespoke warehouse app
For the Zanin 1895 distillery (grappa and liqueurs), a Flutter tablet app on a stack of BC products - from weight that depends on the alcohol degree to shipping with GS1 and SSCC.
The problem (specific). Zanin 1895 handles bulk product: the weight - and the quantity that counts for excise - depends on the alcohol degree. It is not food variable-weight: it is grappa and spirits, where volume, weight and degree must be kept together, through to lot shipment.
The app we developed. A Flutter tablet app (plus bespoke BC code, AL-custom-code): the operator picks the order, scans, weighs and confirms the shipment; or prepares picking missions with pallets. Azure AD auth, applibra/barcode API, works offline.
The products underneath. Standard products compose: AL Catch Weight Management keeps volume and weight together when they depend on the degree; AL Excise handles excise; AL Tracking lots and serials; AL GS1 + AL Barcode the codes and SSCC; AL Zebra ZPL Label Manager + AL Bridge print labels and pallets locally. Plus bespoke code for Zanin's rules.
The point. A bespoke app orchestrates a stack of products - each does its own job (weight/degree, excise, tracking, codes, printing) and they compose over the bus, no fragile integrations. (Underneath, Zanin runs ~30 platform apps: this is the warehouse window.)
The result. Bulk handled correctly through to excise, fast mismatch-free shipping, native lot/SSCC traceability, labels automatically.
Discover AL GS1 Discover AL Catch Weight
The invisible backbone: licensing our platform
A desktop console, a cloud service, a check inside BC: the infrastructure that makes our apps run.
Every AppLibra app, inside Business Central, verifies its licence before it works. Behind that check is an infrastructure we built end to end: a desktop console (Electron) to issue and govern our products' licences, a cloud service that distributes and validates them, and the check inside Business Central that every app runs. It is not a product for sale: it is proof that AppLibra builds across the whole stack - desktop, cloud and BC - and holds it together.
Relantia: clinical reports written with AI, on the right rails
A web product we designed and built end to end - outside Business Central: the professional fills in a structured questionnaire, the AI writes the report. And personal data never leaves.
The problem. After an assessment, a developmental therapist spends hours writing the clinical report: the content is already clear in their head, the writing is slow and repetitive.
What we built. Relantia (relantia.com), a complete, live web app: a structured clinical questionnaire - templates with conditional logic, age-appropriate phrasing, a catalog of standardized tests - and AI that rewrites the template's canonical sentences into fluent clinical prose, streamed. Underneath: Vue 3, Fastify, PostgreSQL. A real product: accounts, a patient registry, an in-app guide, subscriptions.
The point. The AI runs on architectural guardrails, not promises: it invents no clinical content - it connects and rephrases what the professional assessed, who reviews and signs with a recorded confirmation - and personal data never reaches the model: pseudonymized before the call, rehydrated after. EU hosting, no trackers.
The result. Reports in a fraction of the time, field-validated on real cases - and a public product you can try.