A routing plan can look efficient until a vehicle is unavailable, a customer changes a delivery window or a warehouse cannot release an order. The planner then has to reconstruct the constraints and decide which promise to change. That coordination can consume as much effort as producing the original plan.
OpEra Technologies is building a decision engine for factories, warehouses and fleets. Its public description covers planning, scheduling, allocation and routing, with operational data translated into mathematical models. The current website emphasizes updating the plan as real conditions change. [1][2]
Operations research behind the product
OpEra is a YC Fall 2026 company founded by Hindy Rossignol and Bernardo Chalita. Their public profiles describe master's degrees in operations research at MIT and experience spanning machine learning, industrial optimization and research. The company identifies MIT's Operations Research Center as part of its origin. [2]
That background is relevant because a usable plan needs an explicit objective and constraints. Minimizing distance, maximizing service and protecting margin can lead to different decisions. A buyer should be able to identify what the model is optimizing and where the organization's priorities enter the calculation, rather than accept “optimal” as a context-free product claim.
From operating context to a model
The current website describes ingesting data, mapping the operation and constructing a mathematical model for the decisions the customer wants to support. It says the model then runs against the current operational state, with new constraints expressed when reality changes. [1]
For an operations leader, that means the setup work deserves attention. A missing capacity rule or an inaccurate service-time assumption can make an otherwise sophisticated plan unusable. We would ask the team to show how an operator's correction becomes part of the model, how the version is recorded and how the revised result is checked before it is used.
Delivery routing across several depots
OpEra publicly presents a retailer delivery-routing scenario involving many stores and home deliveries. Its website reports lower delivery cost and fewer routes, alongside an on-time-delivery measure. These are the company's published claims; the visible description does not provide a complete independent evaluation or a named customer's full baseline. [1]
The scenario is still useful for scoping a pilot. A retailer can supply historical orders, depots, vehicle capacity and delivery windows, then compare the proposed routes with the plan that was actually run. We would examine missed constraints and service consequences as carefully as distance or cost, because the business does not buy a shorter route at any cost.
Scheduling people, machines and work
Scheduling is another explicit area in OpEra's public company description. It covers what runs when and who works on it, across physical operations. The product's broader planning scope includes how much to make, buy and stock. Those are documented target decisions rather than evidence that every planning problem has the same deployment model. [2]
A useful evaluation would isolate one recurring decision, such as allocating work after a resource becomes unavailable. The planner should be able to compare feasible alternatives and understand which commitments change. We would ask how the product handles a problem with no feasible solution: surfacing the conflict can be more valuable than presenting an apparently complete schedule that violates an unstated rule.
Allocation with an economic objective
The website also describes an order-allocation example for a services marketplace and a sales-planning example for a sugar producer. Those examples connect operational choices with utilization and margin, while keeping the decision domain different from vehicle routing. The headline results remain vendor-reported and should retain that attribution. [1]
Our read is that the common idea is an explicit tradeoff. Which resource receives an order, which customer gets scarce stock and which plan best reflects the commercial priorities? Before comparing results, a buyer should agree on the objective, the permitted actions and the constraints that may never be relaxed. That makes a demonstration understandable to both the operating owner and finance.
Where OpEra fits on SOTA2
| Product & task | Position | Comparison scope |
|---|---|---|
| OpEra AI Decision EngineOptimize RoutesLogistics & Supply Chain | #4 | 7 companies · 9 candidates 7 ranked products |
| OpEra AI Decision EngineSchedule ResourcesLogistics & Supply Chain | #4 | 9 companies · 10 candidates 7 ranked products |
What we would look for in a pilot
Start with one recurring decision and a historical period whose inputs and actual outcomes are available. Have planners validate the model's constraints before comparing proposed plans. Measure feasibility, operating cost and service outcomes together, then introduce a disruption to see how the plan changes. Record the time needed for people to inspect and approve the recommendation.
For the COO, the key questions concern exceptions and control. Can an operator explain a binding constraint, correct bad source data and understand a tradeoff? What happens if the system cannot find a feasible answer? Agree on the path from recommendation to execution and on who may authorize a departure from the normal operating rules.
For the CFO, compare implementation and ongoing service costs with a baseline that uses the same demand, resources and service requirements. Separate modeled savings from savings realized after execution. Changes in volume, fuel cost or product mix should not be silently credited to the optimizer.
The SOTA2 view
OpEra is worth examining when a physical operation repeatedly makes the same constrained decisions and spends substantial effort replanning them. Its useful proposition is to turn operating knowledge into a model that can be inspected and updated. The buying decision should rest on feasible plans and realized outcomes for a defined workflow, with the tradeoffs visible to the people accountable for them.