NewLive in three weeksHow we deploy

Enterprise

Industrial AI, deployed the way your company works.

Operon works inside your security perimeter, your systems and your approval chains. Our engineers work inside your company for the first month, and your first AI employees go live in three weeks.

Security overview
Plant control room with analog panels

MOC delta agent

Run 482
09:41:02Rev C → Rev D · 14 sheets compared
09:41:0922 deltas found · 3 touch the PSV-1302 loop
09:41:15Traced 6"-P-1204 across sheets 114–116
09:41:21MOC package drafted · awaiting approval
Every step loggedView diffApprove

Operon workspace

Where your people review and approve the work.

Detection, verification, knowledge and workflows in the browser, with the permissions, audit trail and approval gates that enterprise engineering work needs.

  • Sign in with Google or Microsoft, or a password stored only as an Argon2 hash. Workspaces are invitation-only.

  • Workspace owners manage members and roles; access follows projects, sites and companies.

  • Verifications, corrections and approvals are logged against the person who made them.

Sheet 114 · P&ID

Rev D

1,284 items detected · 12 routed to review

P-1301A

Centrifugal pump

0.99

FV-1204

Control valve

0.97

6"-P-1204-B2A

Process line

0.96

TT-1211

Temperature transmitter

0.94

PSV-1302

Relief valve

0.74Review

Private deployment

Your perimeter, your infrastructure.

Run Operon in an isolated workspace in our cloud, or inside your own network for documents that can't leave it. Either way, your drawings and everything derived from them stay yours.

  • Database-level separation means one company's workspace cannot read another's.

  • The engine runs inside your network, and documents never leave your perimeter.

  • Encryption in transit and at rest, with regular encrypted backups.

MOC delta agent

Run 482
09:41:02Rev C → Rev D · 14 sheets compared
09:41:0922 deltas found · 3 touch the PSV-1302 loop
09:41:15Traced 6"-P-1204 across sheets 114–116
09:41:21MOC package drafted · awaiting approval
Every step loggedView diffApprove

Integrations & API

Connected to the systems you already run.

Operon reads from the places your documents live and writes to the systems downstream through exports, REST, GraphQL and an SDK. Our engineers build the connections each deployment needs.

  • Document control systems, file shares and cloud drives.

  • Estimating templates, registers, maintenance and ERP systems, by export or API.

  • Your systems group or integrator can ship applications on the same verified data.

Tag register · Turnover

Live
TagTypeDrawingStatus
P-1301APumpPID-114
E-201ExchangerPID-115
PSV-1302Relief valvePID-114
LT-2207Level transmitterPID-118Open

Forward-deployed engineers

Live in three weeks.

Our engineers work on site with your teams. They configure Operon for your documents, symbol conventions and workflows, run the first jobs with you and stay through production.

  • The work picked, and your data connected.

  • Your first AI employees at work, with your people approving.

  • We stay through the first month, tune the work and measure the savings.

Take-off · Bid set Add. 2

Running
Read 312 sheets
Reconciled equipment schedule
Tracing duct runs across levels
Draft take-off for review

The security and scale you expect

Operon runs in an isolated tenant or inside your own network. Your data and everything derived from it stay under your control, and we never train models on it.

View the security overview
CloudVPCOn-prem
Data · Context · AI employees
Isolated workspace

Cloud or your own metal

An isolated tenant per customer, or the full stack inside your network for data that can't leave it.

DataContextOutputsKnow-how
Your perimeter

No training on your data

Own your IP

Your data, your context and your outputs are yours. We don't train on them and don't retain them after you leave.

Week 1Your data connected
Week 3AI employees live
Month 1Savings measured

Live in three weeks

Our engineers connect your data in the first week, and your first AI employees go live in three.

Governance

Controls your security team will ask for

The answers to the first page of your security questionnaire, built into the product rather than promised in a deck.

Read the security overview

Single sign-on

Google or Microsoft sign-in. We never receive those passwords or request access to email, files or calendars.

Role-based access

Invitation-only workspaces, with owners managing members, roles and seats.

Audit log

An append-only record of access changes, plus a log of every verification and correction.

Encryption

In transit over HTTPS and at rest with our hosting providers, with encrypted backups.

Workspace separation

Database-level separation: one company's workspace cannot read another's.

No training on your data

We do not use your organization's content to train AI models, ours or anyone else's.

Questions from IT and procurement

  • In the United States, on Google Cloud in its Iowa region, with encrypted backups kept by Cloudflare. For documents that can't leave your network, Operon can run on-premise.

  • Where a feature uses an external model, such as AI-assisted take-off drafts, requests go to OpenAI with response storage turned off. Under OpenAI's API policies that data is not used to train its models. Our Privacy Policy lists every provider.

  • You can export your content during your subscription and any grace period. We then delete workspace content within 30 days, or sooner if you ask in writing. Encrypted backups expire within 90 days.

  • Yes. We work through your questionnaire and architecture review with your IT team as part of procurement.

  • Yes. Where you have an order form or agreement signed with Operon, it controls wherever it differs from our standard terms.

Start with the work that costs you the most.

Tell us where your team loses the most hours. Three weeks later, an AI employee built for your company is doing that work.