Pricing
Priced per line, because that's what you measure.
A line is the unit the whole product is built around, so it's the unit you pay for. Start with one and add the rest as the loop proves itself.
Every plan starts with a 14-day trial on one line. No card required.
Single Plant
The whole engine pointed at one site, working from the first export.
€300 / month
or €2,500 a year
Up to 1 plant · Up to 3 lines
- OEE at shift, day and week — computed from your own rows, never estimated
- The Six Big Losses as rules you can adjust, priced against what your line actually earns per hour
- Every loss split by whether it was this line's own fault or something upstream starving it
- Quality and Reliability as their own dimensions — capability, control charts, MTBF, failure modes
- Every AI capability: the written report, stop-code reading, the photograph reader, the planner
- A weekly report email, and watch rules that alert when a figure moves
- Unlimited people from your organisation — nobody is charged per seat
Company
Several plants, one view — lines compared against each other, not just against themselves.
€900 / month
or €7,500 a year
Up to 5 plants · Up to 15 lines
- Everything in Single Plant, at up to five plants and fifteen lines
- An organisation roll-up ranking every line you can see, worst first
- The same measurement on every line, so a comparison between two plants means something
- A schedule built from each line's measured rate, with what-if scenarios costed against the real order book
- Every AI capability, exactly as Single Plant gets it — what you pay for here is scale, not features
- Weekly report email, watch rules, and a shift handover for every boundary
- Unlimited people from your organisation — nobody is charged per seat
Enterprise
Past fifteen lines the shape of the problem changes, and so should the conversation.
Let's talk
Annual agreement, scoped to your footprint.
More than 5 plants, or more than 15 lines
- As many plants and lines as your operation actually runs
- The same engine and the same AI as every other plan — nothing rebuilt, nothing reduced
- An optional collector inside your own network reading your historian's API directly
- Rollout, onboarding and contract terms scoped to how your group is organised
Need more lines than your plan includes? Add one for a flat €100 a month — the same price whichever plan you are on.
Next step
Whichever plan looks closest, the next step is the same one.
Tell us how many lines you run and what your historian exports.
What doesn't change
Three things that hold on every plan.
Every plan is the whole engine.
No tier computes OEE less carefully, holds the statistics back, or hides the drill-down — and the AI is part of the engine, not an upsell.
Nobody is charged per seat.
Invite the whole plant: per-seat pricing makes people share a login, and a tool nobody can open is a tool nobody checks.
Extra lines are one flat rate.
Every plan includes a set number of lines to start. Add more at a flat €100 a month each — the same price for your fourth line as for your twentieth, with nothing to negotiate.
Included
All of it. This is the full list, not the top tier's list.
Getting the data in8
The part that kills most rollouts. Optora reads what your plant already produces rather than asking it to produce something new.
- Drop a folder of exports and it works out what each file is — event logs, counter snapshots, tag archives, quality readings, order books
- Three historian shapes read natively: an event log, a periodic snapshot with cumulative counters, and a long-format tag archive
- A review screen before anything imports, so you see what will land and what will not
- Rows that do not parse are counted and downloadable, never silently dropped
- Column mappings save per line, so the second upload is one screen instead of a wizard
- Scheduled CSV drops on a five-minute cadence, for plants that want a live picture
- An optional collector that runs inside your own network and reads your historian's API — Optora still only ever receives outbound HTTPS
- ERP exports read the same way: item masters, BOMs, work orders, purchase orders, stock
Measuring the line11
Deterministic arithmetic on your own rows. Every figure traces back to the events that produced it.
- OEE at shift, day and week granularity, computed in code and never estimated
- The Six Big Losses as rules you can adjust, not hardcoded branches
- A Loss Pareto priced with the contribution margin your line actually earns per hour
- Every loss split by whether it was this line's own fault or something upstream starving it
- Drill-down from any figure to the raw events behind it
- Twelve further indicators: Utilization, TEEP, schedule attainment, failure modes, downtime concentration, Cp/Cpk, Pp/Ppk, defect severity, data quality and inferred-reason coverage
- Six statistical pattern detectors with multiplicity correction, so a finding is significant rather than merely striking
- Quality as its own dimension — inspections, capability, and a control chart per characteristic
- Reliability as its own dimension — MTBF, failure modes, and intervals that are getting shorter
- An organization roll-up ranking every line you can see, worst first
- Shift calendars, planned stops, plant calendar exceptions, per-line loss rules, per-SKU scrap costs and plant and line targets
Planning the work6
The second half. Once a plant's real rates are measured, they are the right input to a schedule — so Optora builds one.
- An order book, typed in or fed from your ERP
- A schedule built by an engine that uses your line's MEASURED rate rather than its ideal one
- What-if scenarios: change a due date, a rate or a shift pattern and see what it costs before committing
- A control loop that notices when reality has moved away from the plan and proposes a recompute
- Maintenance windows priced against the real order book — what this Tuesday's downtime actually costs in late deliveries
- Every plan is a proposal a planner approves or rejects, and a rejection is recorded with its reason
Telling somebody5
A finding nobody sees is not a finding.
- A written report where every number has been checked against the computed data before it is stored
- A weekly report email on a schedule you set
- Watch rules that alert when a figure MOVES, with hysteresis so a number hovering on a threshold does not alert twice a day
- A shift handover that summarises what the outgoing shift left the incoming one
- A delivery log that records every message deliberately NOT sent, and why
And the rest4
- Every AI capability, on every plan — the report, the stop-code work, the photograph reader, the planner
- Unlimited people from your organisation
- CSV export of any drill-down, and PDF of any report
- Column mapping templates saved per line
Before you buy
Questions a plant asks first.
Do you need access to our network?
No. Optora never dials into your plant, and there is no inbound connection of any kind — no OPC-UA client, no VPN, no firewall exception, no account on your OT network.
The simplest way in is a file you export and upload, and plenty of plants never do anything else. If you want a live picture without touching that boundary, a small collector runs inside your own network, reads your historian's or ERP's own API from there, and sends outbound HTTPS to us. It is your network talking to us; we are never talking to your network.
That is a positioning choice rather than a limitation. Plants air-gap their OT networks for good reason, and a tool that never asks to cross that line has one less thing to argue about.
What does the AI actually see, and can it invent a number?
It can not, and that is enforced rather than promised.
Every figure is computed in code from your rows before any model is involved. Where the model writes about those figures, it is handed the computed payload, and each number in the prose it returns is checked back against that payload before anything is stored. A response citing a figure that is not there is discarded whole — not trimmed, not corrected.
It does see more than statistics. If you photograph an HMI or a handwritten shift sheet, it reads the picture. If your operators type notes, it reads them. If you upload your equipment manual, it reads that. In each of those it is held to its own source: a reading must quote a line the model itself transcribed, a gloss must appear in the manual word for word, and the photograph is kept and shown beside the result so a person can check it.
Nothing read from a photograph or a note is ever written into your production record. Those numbers stay what they are — somebody's phone, and somebody's handwriting.
Who inside our company can see it?
Only people you invite. Everything is scoped to your organisation by row-level security in the database, so another customer's queries cannot reach your rows even in principle.
Within your organisation there are admins, supervisors and members. Configuration that changes what your history MEANS — shift calendars, rates, loss rules, targets — is admin-only, because those edits re-score numbers you have already published.
Can we evaluate it without sending real plant data?
Yes. There is a synthetic export with patterns deliberately injected into it, so you can watch the detectors find things you already know are there before deciding whether to upload anything of your own.
What happens when our export format changes?
You re-map it once and the saved template updates. Rows that no longer parse are counted and downloadable rather than dropped, so a format change shows up as a number on the import screen instead of a silent gap in next month's OEE.
If the shape is one Optora has not seen before, it will tell you what it thinks each file is and ask you to confirm before anything imports.
Which historians do you support?
Any that can export CSV — the mapping is config-driven rather than a parser per vendor. Optora reads an event log, a periodic snapshot with cumulative counters, or a long-format tag archive, and detects which one you have sent.
If your export does not fit one of the three, that is worth a conversation before you buy, not after.
Start with one line.
One export is enough to see whether any of this is true for your plant.