Your assembly line, on rails.
Model your process, pair a tablet with a one-time code, and let operators badge in and build. Every step they complete becomes a timestamped event on your dashboard.
Early access is open. Bring one line and we'll help you model it. See how it works
EU + US data residency · API-first — our UI runs on the same API you get · Pre-built ERP integrations
From signup to your first tracked unit — today.
If your floor runs on paper travelers, a spreadsheet, and a whiteboard — or a homegrown app nobody dares touch — this replaces it before lunch. No statement of work, no six-month rollout. The onboarding wizard walks this exact path.
Model your process
Products, revisions, stations, steps — start from templates, keep what fits.
Pair tablets
Any tablet, one one-time code. It becomes the station — scoped, revocable from admin.
Badge in operators
QR, barcode, or RFID. Enroll, print a badge, done. Operators never log in.
Run work orders
Guided steps, server-checked verdicts, rework fault trees, pack-out gates.
| 09:14:51 pass · 00:41
Watch the data land
FPY, cycle times, genealogy — live, from the first unit.
Built for the station. Visibility for the back office.
Guided assembly & inspection
Rich instructions with PDFs and photos. Numeric inputs with tolerances, enums, photo capture. Escalations reach the supervisor.
Rework that thinks in trees
A fault-tree walker guides diagnosis. Concurrent failure tracks, parts recorded per fix, every traversal on the record.
Gates that hold
No pack-out until final test passed and rework is closed. Verdicts are evaluated on the server — clients are never trusted.
Survives factory Wi-Fi
Definitions and the active session are cached on device. Steps queue offline and sync when you're back. A blip never blanks a wizard.
Labels, printed by the process.
A passing final inspection prints the serial label. A completed pack-out step prints the carton label. No drivers on the tablet, no shared PC with a label app.
At step completion. Any step can print when it passes — serial at final inspection, carton at pack-out, lot tags at kitting.
On demand. Reprint from any unit or work-order record, permission-gated, without leaving the station.
Your templates, your printers. Design and store label templates in BarcodeLabels.io and the floor pulls them by name; FactoryPrint, our lightweight print client, delivers them to any printer you already own.
Every step is a timestamped event. Everything else falls out.
Each execution is pinned to the assembly, revision, and instruction version that produced it — sliceable by operator, step, station, line, assembly, and revision. Every view exports CSV. Live dashboards for every line and the whole floor.
Rev B inherits Rev A's steps until you say otherwise — so the comparison works from the first Rev B unit.
Pricing that fits your floor.
Every floor is a different shape — line count, station count, what you're integrating with. Tell us about your lines and we'll put a proposal together.
Tell us about your floorWorks with your ERP. Doesn't require one.
Fully functional standalone — connect what you already run, when you're ready. The app's own UI consumes the same /api/v1 you get.
ERP
Items, BOMs, and work orders in; completions and scrap posted back to the work order.
NetSuiteAccess control
The badges your doors already know become floor identity — enroll once, badge in anywhere.
Avigilon AltaLabel printing
Labels at step completion or on demand — templates designed and stored in BarcodeLabels.io, delivered to any printer you plug in by FactoryPrint, our print client.
BarcodeLabels.ioAutomation & iPaaS
Scoped API keys; HMAC-signed webhooks with retries and a delivery log — ready for your integration platform.
Celigo
Azure Logic AppsOpen API
Everything the UI does is /api/v1 — versioned, cursor-paginated, documented with an OpenAPI spec and data dictionary.
CSV everywhere
Import, export, and upsert on every entity. Every dashboard view exports.
The questions every plant asks first.
What hardware do we need?
Any recent iPad or Android tablet running a browser — most floors use ~$200 10-inch tablets in kiosk mode. Line dashboards run on any TV with a browser stick. USB and Bluetooth barcode scanners work out of the box; badge scanning uses the tablet camera or a scanner.
Where do work orders come from if we don't run an ERP?
Create them in the app, import a CSV, or POST them to the API. A dispatch queue assigns released work orders to lines, and stations pull the next unit — no ERP required, ever.
Can our test equipment post results directly?
Yes. A test bench is just another station: it pairs with a revocable station token and posts step executions over the same API the tablets use — readings, verdicts, and timestamps land in the same event stream.
Do you trace component lots and serials into a unit?
Yes. A step can require a component scan — lot or serial — so unit genealogy answers "which valve lot went into SN 24-08114," and the recall question in reverse: every unit a suspect lot touched.
What languages does the floor see?
Step instructions carry per-language variants and the station follows the operator's badge profile — English and Spanish first, more as customers need them. Back-office stays English at launch.
What does it actually cost?
Pricing is put together per deployment — line count, station count, and what you're integrating with all factor in. Tell us about your floor and we'll put a proposal together.
From signup to your first tracked unit — today.
Model your process, pair a tablet, badge in an operator, build one unit, watch it land. Launching soon — leave an address and you're first through the door.
Prefer a conversation? Leave your work address and we'll reach out.