Pricing

Priced by unit operation, not by seat.

Annual subscriptions scale with the number of process unit operations in your twin. One price covers every operator, engineer, and manager who needs access.

Pilot
$2,400 per year

For engineering teams evaluating digital twin technology on a single process section. Up to 3 unit operations.

  • Up to 3 unit operations
  • Physics-based twin engine
  • 15-second sync cycle
  • OPC-UA + MQTT ingest
  • Outcome-linked alerts
  • 30-day onboarding support
Request Pilot Access
Most Common
Standard
$9,600 per year

For continuous-process plants deploying twins across a full process train. Up to 12 unit operations.

  • Up to 12 unit operations
  • All Pilot features
  • All 6 protocol connectors
  • Monte Carlo ensembles
  • Sensitivity envelope reports
  • Priority engineering support
  • Full audit trail logging
Request Pilot Access
Enterprise
Contact us for multi-site pricing

For multi-site or complex deployments requiring dedicated support, custom integrations, or on-premises deployment.

  • Unlimited unit operations
  • All Standard features
  • On-premises deployment option
  • Custom historian connectors
  • Dedicated process engineer
  • SLA with uptime commitments
  • Executive business reviews
Talk to Us

All prices in USD. Annual billing. We also offer a 90-day money-back evaluation period on Pilot subscriptions.

What counts as a unit operation?

A unit operation is a discrete physical process step that can be described by its own governing equations. Common examples in our current deployment base:

SEPARATION
  • Distillation column
  • Absorber / stripper
  • Crystallizer
  • Centrifuge train
REACTION
  • CSTR / PFR reactor
  • Fermenter / bioreactor
  • Polymerization vessel
  • Digester
HEAT TRANSFER
  • Heat exchanger
  • Evaporator / dryer
  • Lyophilizer
  • Pasteurizer
FAQ

Frequently asked questions.

Onboarding begins with a 1-hour technical scoping call where we review your process configuration, sensor infrastructure, and historian setup. From there, we configure the twin engine to your specific unit operations and set up the data connectors. Most pilot deployments reach their first live prediction within 4–6 weeks of the scoping call.
No. Twynvex reads from your existing DCS / historian via standard protocols — OPC-UA, MQTT, or Modbus TCP. We do not write back to your control system. The twin is a passive observer and predictor. Your DCS configuration and control loops remain exactly as they are.
The Twynvex agent runs locally on your network as a lightweight edge process. If connectivity to cloud services is interrupted, the agent continues collecting sensor data locally. On reconnection, it backfills the twin with the buffered readings. Local alerting continues to function during any connectivity interruption.
By default, raw sensor readings are processed on-premises and only aggregated model state (not raw tag data) is sent to the dashboard API. For Enterprise customers, a fully on-premises deployment option is available where all data stays within your OT network boundary. We can provide a data flow diagram for your IT and OT security review.
Yes. You can upgrade your subscription at any point. The additional unit operations are added to your running twin configuration. We credit the pro-rated value of your current subscription against the upgraded plan.

The scoping call is free.

Tell us your process configuration. We'll tell you how many unit operations that is, which connector would be fastest to deploy, and whether your sensor density is sufficient to run the physics model. No sales pitch, just engineering.

Request Pilot Access Read the Docs