Photo, signature and failed item captured offline.
Plant operating system
Run the floor from one live record.
FloorFile connects checks, maintenance, safety, documents, training, frontline HR and corrective work, so the plant stops chasing answers across paper, spreadsheets and siloed tools.
Machine hub
Wrapper 1
Maintenance
Set by failed check
Report downtime
Start due check
Open manuals
Today
7 openR. Diaz - on shift, certified, lowest load.
Suggested from the failed check.
Assignment trace
01
Job title: Maintenance Technician
02
Training: LOTO current
03
Shift: active until 3:00 PM
04
Load: 2 open jobs
Two taps or one scan to any record
Offline checks, photos and signatures
API-first from the first release
What it is
A working layer for the plant, not another management dashboard.
FloorFile is where the daily operational record lives: who did the check, what failed, which machine was involved, what evidence was captured, who is qualified to respond, what document applies and whether the corrective work actually closed.
It replaces paper checklists, spreadsheet schedules, basic CMMS setups, light QMS tools and scattered training notes. It coexists with ERP, HCM, MES, PLM and BI through a public API, exports and webhooks.
Designed for adoption
The floor has to trust it.
Open the next job fast.
Role-specific home screens lead with today's checks, work orders, approvals and alerts. Common floor work stays one screen deep.
Scan the thing in front of you.
QR, barcode and NFC lookup opens the machine, part, document or location hub with the right quick actions beside it.
Keep working without signal.
Checks, work orders, downtime, incidents, comments, photos and signatures save locally and sync when the tablet comes back online.
Native response
A failed check should do more than create a red row.
FloorFile ships with automation playbooks for the high-value manufacturing reactions. Each one can run automatically, suggest the action to a human, or stay off.
Capture the failure
The operator completes a check, adds photos, signs, and marks a failed item, even offline.
Protect the asset
The equipment can move to maintenance, downtime can open, and the history stays attached to the machine.
Dispatch the right person
The assignment engine filters by job title, certifications, roster, location and current load.
Close the quality loop
A CAR, NCR, SCAR or corrective check can be suggested or created with the source evidence already linked.
What lives inside
The connected record for quality, assets, people and proof.
Quality
Checks, forms, audits, CARs and advanced QMS.
NCR, change control, supplier quality, risk and FMEA, deviations, OOS, lot genealogy and Part 11-ready signatures can be switched on when needed.
Maintenance
Assets, downtime, work orders, parts and vendors.
Equipment hubs connect service history, PMs, corrective work, manuals, parts, qualified staff and predictive recommendations.
People
Workforce, training, rosters and frontline HR.
Track worker records, locations, attendance, leave, milestones, certifications, competence gaps and confidential HR case notes without becoming payroll.
Evidence
Documents, comments, alerts, reports and exports.
Controlled documents, acknowledgements, access logs, attachments, entity comments, notifications and audit-ready reporting stay tied to the work.
No-consultant setup
Productive before the binder gets dusty.
Start from Lean, Manufacturing or Regulated presets. Import workers, assets, parts and existing labels. Pick starter packs for checks, PMs, dashboards and corrective workflows. Then tune the system instead of building it from scratch.
- 1 Import what the plant already uses.
- 2 Choose the modules that should exist.
- 3 Turn on playbooks at the right level.
Architecture
Built for Cloudflare from the beginning.
React and Vite on Cloudflare Pages. Hono on Cloudflare Workers. Neon serverless Postgres with Drizzle and row-level security. R2 for evidence. KV for short-lived infrastructure state. OpenAPI and a generated SDK for every module.
Cloudflare Pages
Workers API
Neon Postgres
Drizzle ORM
R2 evidence
Event outbox
Public API
Offline PWA
Pricing
Site-based plans, because the floor should actually use it.
Unlimited frontline users are included. Admin and editor seats scale by plan. Pricing shown monthly, billed annually.
Lean
$495/site/mo
For teams replacing paper checks, spreadsheet schedules and scattered training records.
- Unlimited frontline users
- 5 admin/editor seats
- Checks, forms, CARs and documents
- Workforce, training and notifications
- Starter packs and guided setup
Most common
Operations
$1,250/site/mo
For plants connecting quality, maintenance, safety and frontline work in one operational layer.
- Unlimited frontline users
- 15 admin/editor seats
- Everything in Lean
- Maintenance, downtime, parts and vendors
- Automation playbooks, API and webhooks
- Reports, exports and analytics
Regulated
$2,450/site/mo
For mature quality programs that need controlled change, traceability and regulated records.
- Unlimited frontline users
- 30 admin/editor seats
- Everything in Operations
- NCR, supplier quality, FMEA and change control
- Deviations, OOS and lot genealogy
- Regulatory e-signature mode
Enterprise plans are quoted for multi-site rollouts, SSO, validation support, migration services, custom retention policies and deeper integrations.
Fair questions
What FloorFile is not trying to be.
Does FloorFile replace our ERP?
No. It handles the plant operating layer: floor execution, quality evidence, maintenance response, competence and corrective work. Finance, purchasing, costing and inventory system-of-record stay in the ERP.
Is this a full HRMS?
No. FloorFile owns frontline people-ops, competence, attendance context, leave visibility and HR documentation. Payroll, benefits, pay calculation and labor planning stay in the HCM or payroll system.
Can modules disappear for teams that do not need them?
Yes. Modules and advanced capabilities are company-toggleable. Disabled modules vanish from menus, dashboards, pickers, optional fields and APIs.
Does the floor really work offline?
Core execution is designed to. Checks, photos, signatures, downtime, work orders, incidents and comments queue locally, then sync through the same stateless API when the device reconnects.