Shop operating system for manufacturers

Run the whole plant on one record.

Rivlet keeps one record of the plant. A web order, the work it needs, each report from the station that makes it and the shipment that closes it are events in one hash-chained log, each saying who did it. Every decision keeps its reason: a person's in their own words, a rule's by naming the rule.

Meet each role

The live demo opens soon at demo.rivlet.io, with an account for each role.

Real footage from the demo plant: the office shell beside the ASM-1 and FG station tablets.

01 One order

One web order, through the whole plant.

Shopify #1001 is 60 motors. Follow it from the checkout to the shipping dock in six steps. Every picture is a frame of the same filmed run.

  1. A checkout becomes a sales order.

    The Shopify app records the order in Rivlet as itself: one sales order per line, shipping from finished goods. Rivlet works out what covers it: 35 from stock, 25 not covered yet.

    Shopify app · 05 Supply

    The sales order Shopify #1001 in the shell: channel io.rivlet.shopify, 60 MTR-500 motors shipping from FG, due 2026-01-08, confirmed. What covers it: 60 to ship, 35 from stock, 25 not covered yet. (open full size)
  2. The demand planner proposes the rest.

    An agent proposes a work order for the other 25, made for Shopify #1001 and worth $2,875 at standard cost. That is over the $2,000 it may spend on its own, so it waits for a person, and the card says why.

    demand-planner · 00 Overview

    Pat's overview: a pending proposal, Create work order, Make 25 × MTR-500 for Shopify #1001, due 2026-01-08, $2,875. Waits: over the $2,000 demand-planner may spend on its own. (open full size)
  3. A person approves it, with a reason.

    Pat, the planner, approves up to $10,000. Pat types why and approves, and the work order is released at once, labelled with the order it is for. Pat's name and reason stay with the decision.

    Pat · planner

  4. The job reaches the station, labelled.

    Assembly 1's tablet shows WO-1011 with its Shopify #1001 label. Olivia presses the 25 motors and reports them. Through the day they are wired at ASM-2 and tested at TEST, each step on the record.

    Olivia · ASM-1 tablet

  5. Finished goods ships it.

    At FG the Ship tab lists the order as ready. Sam ships all 60 with the tracking number from the label. Shipping more than FG holds is refused, in plain words.

    Sam · FG tablet

  6. The order closes, and the shop is told.

    Shopify #1001 reads shipped in full, with the work made for it and the shipment's tracking. The Shopify app turns each shipment into one fulfilment, and the stock Shopify shows matches Rivlet's.

    Shopify app · fulfilment

    Shopify #1001 again, now done: shipped in full, 60 of 60. Work made for it: WO-1011, 25 made, done. Shipment: 60 MTR-500 from FG with tracking 1Z999AA10123456790, shipped by Sam, with every serial. (open full size)

Ordered on the web, made and shipped the same day. Recorded by the app, approved by Pat, made by Olivia, shipped by Sam.

02 On the floor

A tablet at every station. A board above it.

The Station app is where work is done and recorded: the next job and its instructions, good and scrap, stoppages and readings. It keeps working offline, refuses in plain words, and does only what its station may.

The queue, one job at a time.

The next job on top with its instructions and due date, later ones below. Start, report good and scrap, say why the station stopped, complete. Each report is an event on the record, naming the person and the tablet.

Four ways to sign in.

A badge by barcode scanner, an NFC tag, the tablet's camera or a typed code, then a PIN. With nobody signed in, the tablet is read-only.

  • Barcode scanner
  • NFC
  • Webcam
  • Typed code

Refusals in plain words.

“This tablet can only move stock in or out of ASM-1. Move it from a CNC-1 tablet, or ask a supervisor.” What it may not do, and what to do instead.

An outbox for when the network drops.

Offline, each change waits on the tablet with the name of whoever made it. Back online it is sent once, automatically. A change the node refuses stays in the outbox with the reason.

Measuring at the bench.

An instrument's live reading against the spec band. A steady in-spec value is recorded by itself. Out of spec, the unit is marked failed and the report counts it as scrap.

Quality holds.

A unit that fails a check set to “quality decides” goes on hold with its readings. Only quality signs it off, with a reason, in the shell.

TV boards

Every station, on the wall.

A display enrolls like a smart TV: it shows a short code, and a station manager or supervisor approves it for one station. From then on it shows that station's day, live: done today against the target, ahead or behind, what is running and what is next, each job labelled with the order it is for.

Nobody signs in on it, and it reads its own station's board and nothing else.

Assembly 1's board on a 4K TV in the demo plant. Every figure scales with the screen.

Approve where the work is.

Station managers and supervisors see what waits on their station, such as a kanban refill or work to make, and decide it at the tablet with a reason. Over their limit, the tablet says so without naming an amount they may not see:

It is worth more than you may approve (up to $5,000): leave it for someone whose limit covers it.

03 In the office

The office reads the same record.

The shell is the office's web app. Its sections are numbered, 03 Manufacturing, 05 Supply, 13 Finance and the rest, and each person sees the ones their role uses. What a tablet reports, the shell shows.

Maya's overview in the shell: key figures on top, then three proposals waiting for Maya: a kanban refill for $1,600, a work order for Shopify #1001 for $2,875 and a purchase order for $16,000, each saying what it does and why it waits. (open full size)

Every request says why it waits.

The plant manager's overview leads with what waits for a decision: a purchase order, a kanban refill, work for a web order. Each card says what it does and why it waits, as in “Over the $10,000 that may be spent without approval”, and the decision needs a reason.

Purchase order PO-33626c27 to Cobalt Machining opened as a record: the order, how it was decided (the proposal, approved by Maya), the exchange it came from (disruption alert, RFQ, signed quote, purchase order, acknowledgement) and its history. (open full size)

Every record shows how it was decided.

A purchase order, a proposal, a partner, an item or an order opens as a page: the proposal behind it, who approved it and why, the signed exchange it came from, and its history.

13 Finance as Finn, the CFO: inventory valued at standard cost by location and item, with Export CSV, beside work in progress by work order. (open full size)

Finance at standard cost, with CSV.

Inventory, work in progress, purchase commitments and shipped revenue and cost, all at standard cost. A cost nobody knows shows as unknown, never as 0. Each report exports as CSV.

See what each partner will be told.

Before an RFQ goes out, its preview shows each partner factory what it will be told and what it will not. Here Cobalt learns the part, quantity and date; the $95.00 price ceiling stays home, and every quote is checked against it.

04 Design to machine

From the drawing to the machine, on the same record.

Engineers draw the part in CAD and program it in CAM. A plant manager releases the program, and the machine's station knows which one to run.

  1. 01 CAD

    Draw the part or import its DXF. Parameters, manufacturability checks, an estimate and a 3D view.

  2. 02 CAM

    Plan the toolpath with a live preview and cycle time. The node generates it again and confirms it matches.

  3. 03 Release

    A plant manager releases it with a note, numbered for the machine: O1001, replacing O1000 for that operation.

  4. 04 At the machine

    The edge bridge delivers released programs to the machine and reports what the controller loaded. At CNC-1 the job says which program to run.

Drafts are never delivered. A machine still holding an old revision says so on the tablet.

05 Governance

Trust, built in.

The plant's rules decide who may do what, and the record keeps the evidence. People, agents, apps and partner factories all go through the same rules.

The default roles and what each may approve. The plant edits them and adds its own.
RoleApproves up to
Station manager$1,000
Line supervisor$5,000
Planner$10,000
Buyer$25,000
Plant manager$250,000
CFONo ceiling

Floor operators, quality, engineers and the admin approve nothing. Anything with no known value is over every limit but the CFO's.

  • Four eyes.

    Nobody approves their own proposal. A purchase you propose always waits for someone else.

  • A reason and an actor.

    Every change is kept with who made it and when: a person, an agent, an app, a device or a partner. A person's decision always has its reason, and a decision a rule makes names the rule.

  • One hash-chained log.

    Every change to the plant's records is an event. Each record carries the hash of the one before it, so a rewrite shows to anyone who kept a copy of the log's latest hash, as partners do. A log cut short shows at its next message to a partner.

  • Agents propose, rules decide.

    Agents propose work under the plant's rules. Routine work within a limit runs on its own; the rest waits for a person.

  • Signed and sealed.

    RFQs and quotes between partner factories are signed with Ed25519 and sealed so only that partner's node can read them on the way.

  • The ceiling stays home.

    The most you would pay is kept on your node and never sent. Every quote is checked against it.

  • Forgeries refused and counted.

    A quote changed after signing, or signed with another key, is refused and counted for that partner.

  • Apps sign in as themselves.

    An app proves who it is with its own key (DPoP), gets short-lived access and holds only the rights it was granted. It never approves.

Four eyes: Bea cannot approve a purchase order Bea proposed.
A quote in Cobalt's name, changed after signing: refused for its signature and counted on Cobalt's row. Its body is never kept.

Watch a partner's quote signed, sealed and checked, with the forgeries refused, or the rules an agent works under.

06 Works with

Connects to what the plant already runs.

Other systems reach Rivlet through the same node as people do, under the same rules.

  • Shopify

    A checkout becomes sales orders. Each shipment becomes one fulfilment, and the stock Shopify shows matches Rivlet's.

  • Partner factories

    Other companies' Rivlet nodes. RFQs, quotes, purchase orders and acknowledgements travel as signed messages, and each partner's log is witnessed.

  • MQTT

    A mirror of the plant's events to your own broker.

  • A2A

    An agent card for other companies' agents. What they propose waits under your rules.

  • MCP and AI assistants

    Assistants read the plant and propose actions. Their proposals are governed like anyone's.

  • Apps

    Installed from a manifest you review first. They sign in as themselves (DPoP), with only the rights you grant.

  • Edge bridge

    A small computer beside an instrument or a machine: readings in, released programs out.

  • HTTP API

    What the shell and the tablets do goes through one API, under each person's role.

07 Watch

See it work.

Twenty-nine captioned films of the product, all from the demo plant. The short films first, then the ones from the manual, by area.

Short films

On the floor

In the office

Design to machine

The network

08 Try it

Sign in as each role.

The demo plant opens online soon, at demo.rivlet.io. Each person below will have an account, and each sees and may do only what that role allows, so signing in as two of them side by side shows the rules at work. Everyone will share the one plant, and it will start over every night at 1 a.m. Pacific time.

The demo
demo.rivlet.io, opening soon
User name
one from the table
Password
shown here when it opens

Until then, the films on this page show each role at work in the same plant. Its clock stands at 09:30 on Monday 5 January 2026, and its partner factories are Brightline Castings and Cobalt Machining.

The demo accounts, one per role. Choose one on the demo's sign-in page, or type its user name.
User nameRoleTry this
mayaMayaPlant managerapproves up to $250,000See the whole plant, money included. Approve what waits above the others' limits with a reason, such as a purchase over $25,000 that Bea proposes, then open its record to see who decided what and why.
finnFinnCFO / financeno ceilingRead Finance: stock at standard cost, work in progress, what is on order and what shipped. Export it as CSV.
patPatPlannerapproves up to $10,000Approve the $2,875 work order the demand planner proposed for Shopify order #1001, if nobody has yet today. Plan work orders and kanban loops; anything over $10,000 waits for someone else.
beaBeaBuyerapproves up to $25,000Ask a partner factory for a quote and see what it is told and not told before it goes. Like any purchase Bea proposes, it waits for someone else to approve it.
samSamLine supervisorapproves up to $5,000Approve the $1,600 kanban refill for Brightline housings, if nobody has yet today. Set the day's targets, and approve a TV board.
oliviaOliviaFloor operatorASM-1 onlyAt the ASM-1 station: start a job, report good units and scrap, pull a kanban card. Moving stock at another station is refused, and so is Olivia's badge at another station's tablet.
quinnQuinnQualityapproves nothingKeep the gauge register: readings from an instrument past its calibration date are refused. A unit that fails a check set to Quality decides waits on hold until Quinn signs it off or scraps it.
eliEliIndustrial engineerapproves nothingLay out the floor, draw a part in CAD, and make a machine program in CAM for the released bracket BRK-100. A new part must be released, which takes an approver, before CAM can program it.
adaAdaAdminapproves nothingLook around Admin: people, roles and limits, badges, tablets and apps. The demo's nine people and its apps stay as they are. Make a code to enroll a tablet.

See for yourself

Watch it. Read it. Run it.

01 Watch

Seventy-three seconds: a web order through the plant, the shell beside two station tablets.

02 Read

The user manual: fourteen chapters by role, in plain words, with the same pictures and films.

Read the manual PDF · 163 pages · 51 MB

03 Run

The demo plant on your own machine, from the repository. It needs Rust 1.95 or later and Node.

npm --prefix web ci && npm --prefix web run build
cargo run --release -- demo --serve 127.0.0.1:8740 --ui web/dist

Then open http://127.0.0.1:8740/app/ and sign in with one of the tokens the demo prints, one per person. Its clock stands at Monday 5 January 2026, 09:30.