Speed and control.
At the same time.

For quality, production and review teams, and for the people who authorize release in industrial operations that work in batches and need to coordinate controls, evidence and decisions.

Operations that manufacture in batches or discrete orders and need traceability between raw materials, process, controls and finished product. The demonstration includes ten profiles: oils and fats, paints and coatings, biscuits and baked goods, meat deboning and derivatives, aquaculture feed, animal nutrition ingredients, fresh fruit and packing, semi-solid bulk pharmaceuticals, plastic packaging and a configurable generic core.

Five guided tours with fictitious data: unblocking a batch by completing its evidence, resolving a deviation, preparing an audit by reviewing the history and the batch record, finding a pattern by asking the copilot, and releasing for a customer by comparing the batch against two specifications. You can pause, resume and restart each guided tour.

Nothing to install: it runs in the browser and registration takes less than a minute. Each guided tour lasts between three and eight minutes, and you can explore on your own without following any of them.

The guided tour lets you investigate an out-of-range result, record the correction, review the balance and verify the closure. Closing the deviation does not automatically authorize the release: that decision belongs to the authorized approver.

Not yet. The demonstration works with fictitious data and is not connected to production systems. Integrations are part of the scope defined when a pilot is planned, and they are best reviewed in the discovery conversation.

Rigo One organizes quality and food safety evidence the way ISO 9001 and FSSC 22000 ask for it: identification and traceability by batch, control of nonconforming outputs, and recording of nonconformities with their corrective action. Against 21 CFR Part 11 and Annex 11 of the EU GMP, the demo already covers the audit trail with author, time and grounds, the separation of actions by role, keeping the original measurement when a value is corrected, and a versioned workflow configuration; corporate authentication, electronic signature and computerized systems validation are defined within the pilot scope. No software certifies anything by itself: certification depends on your management system.

Questions about the batches loaded in the demo: which ones share a raw material, which ones went through a given piece of equipment or line, or which ones have a parameter above a threshold. Every answer shows the batches behind it, and you can open them to check it. It is not connected to an external model by default, nor to real data, and it does not decide for anyone: it points to where to look.

In the demo, yes: the same batch is compared against two customer specifications, and you can see which one it conforms to and which one it does not. Every specification keeps its versions with the date, the reason for the change and who published it, and accepted concessions sit in a catalogue with their reference and validity. Formal approval by your own customer and the electronic signature are defined within the pilot scope; the internal release rule does not change.

Yes. The demo lets you attach up to three files per action, of up to 5 MB each: PDF, PNG, JPG, Word, Excel, CSV or TXT. The files are linked to your registration session and are not accessible to other visitors. Use test files only.

It is used to enable your access to the demo and to respond to your interest in the product. It is not sold or transferred for commercial purposes. You can request its review or deletion by writing to hola@lilab.io. The details are in the Privacy policy.

No. The batches and the guided tours use fictitious data. The actions of the exercise are saved in this browser; restarting a guided tour does not delete the attachments already saved. Decisions stay in the hands of the authorized people.

Rigo One is a product of LILAB S.A.C., a technology company based in Lima, Perú that designs custom software, digital products and automation for industrial and service operations.

It starts with a two-week discovery to map your release workflow, your controls and where the data will come from, and that is where we set the capability criteria. A two-week pilot follows, running in parallel with your operation, with one plant and one or two lines. One month in total, from signature to decision. The pilot is paid in two halves of USD 2,900: the first up front and the second at closing, only if the criteria are met. Everything paid is credited in full towards the annual license, which is charged per plant with unlimited users.

The second half is not charged. What was paid up front covers the two weeks of discovery and the two weeks of pilot support; if you decide to continue later, it is credited in full towards the license all the same.

The discovery together with the pilot, one month in total, costs USD 2,900 up front and USD 2,900 at closing, conditioned on meeting the agreed capability criteria; everything paid is credited in full towards the first-year license. After that, the license is charged per plant and billed annually: from USD 990 per month for one production line, and USD 1,490 per month for up to three lines, always with unlimited users, with a joint results review at six months against the discovery baseline. Additional plants of the same company get a 30 % discount, and connectors with ERP, LIMS or instruments are quoted per system. Prices are in US dollars and do not include taxes.

Rigo One is not an ISO document manager: it runs the release of every batch with its controls against specification, its evidence, its mass balance, its deviations and the decision with an owner. For that to work, Quality, Production, the Laboratory and whoever authorizes all work on the same batch record, so charging per seat would penalize exactly what makes the product useful. That is why the price is per plant and users are unlimited.

You can explore the demo through a simple registration, or schedule a discovery conversation with someone from the team. In that meeting we review the workflows, the control points and the needs of your operation. After that conversation, the standard path is a two-week discovery and a two-week pilot running in parallel with your operation.