Onctuo needed a supervision tool that was more useful than a supplier console alone. The platform now connects KPIs, machine states, alerts, history, forecasting, and the access rules the team actually needs inside a foundation designed for day-to-day operations.
We needed a tool able to manage a fleet of self-service machines. Koragence structured a clear, robust platform we can rely on every day.
The cockpit already consolidates KPIs, statuses, alerts, and history for ten machines in the same operational view.
The foundation combines a Next.js frontend, a NestJS API, a PostgreSQL database on a VPS, Docker containers, audit logs, stock forecasting, and the notifications needed for day-to-day operations.
Stack used
Technologies shown in the ticker include Next.js, NestJS, PostgreSQL, Docker, OVHcloud, Cloudflare.
This section highlights the few technologies that carried the project, what they brought, and why they fit this product so well.
Next.js was used to build a clear cockpit where KPIs, machine status, and alerts can be read in one interface.
NestJS carried the business flows, supplier exchanges, and alert logic that give the product its value.
PostgreSQL made it possible to keep orders, events, logs, and access rules in a foundation that stays readable over time.
The same delivery discipline is applied here: scoping, structure, build, rollout, and evolution, with trade-offs adapted to the real project.
Understand the machines, incidents, blind spots, and the decisions the product needed to accelerate.
Define machines, orders, events, errors, alerts, and access rules before building the views.
Build the dashboard, machine detail, forecasting, and support pages inside one product view.
Connect supplier flows, logs, access rules, and sensitive actions inside a foundation that stays readable.
Validate real cases, alert readability, and data quality before daily operations.
Open the tool to day-to-day operations and prepare the next evolutions without breaking the foundation.
Onctuo operates self-service ice cream machines and needed a clearer base than the supplier console alone. The goal was to steer the fleet, understand incidents faster, and make field decisions more reliable.
The need quickly went beyond a dashboard. Machines, orders, alerts, history, forecasting, and access rules all had to be connected in a single product view.
Without a dedicated product, teams spend too much time cross-checking supplier data, stock signals, incidents, and support issues. Diagnosis slows down, priorities get blurred, and the overall view arrives too late.
The product had to connect the right events, statuses, and actions around the machines, orders, and alerts that actually matter to operations.
The delivered foundation connects a Next.js frontend, a NestJS API, a PostgreSQL database on a VPS, Docker containers, and supplier integrations. The scope covers the dashboard, machine details, alerts, logs, forecasting, support, exports, and access management.
The product logs events over time, links error codes to causes and resolutions, and prepares the action layer for operations and field teams.
Onctuo now has a tool aligned with its own operating model, readable by the team, and no longer dependent on a supplier console or manual reprocessing.
Supervision, alerts, support, and forecasting now share the same objects. This reduces friction between incident review and operational decision-making.
The value also comes from the delivered documentation, source code, and included maintenance. The product is deliverable, transferable, and usable.
Onctuo is a concrete case of a business cockpit that connects machine state, alerts, logs, and forecasting.
The project also touches the run side: roles, deployment, notifications, worker jobs, and service continuity.
The supervision, incident, maintenance, and field-data logic matches some of the most common industrial topics.
To see when fleet or maintenance steering needs to move beyond scattered exports and spreadsheets.
The business backend, roles, and supplier integrations follow a structured Node.js approach across the API and worker.
The product relies on a structured database to log statuses, alerts, orders, and audit logs over time.
