Model OR-4 · Pittsburgh, PA · Series A
Planning engine for manufacturers, distributors and fleets
Orrery's agents test candidate plans against your live inventory, labor, routes and contracts, tell you what each trade-off costs in plain language, and re-plan the moment something breaks.
In production at 19 operators.
A recorded run, slowed down so you can read it. In production the same run finishes in about 40 seconds, then waits for a person to approve it.
Five steps, every time something changes. Scroll to run them.
Orrery connects to your ERP, WMS and TMS and keeps a live model of every SKU, dock, driver, shift and contract clause. It refreshes every minute, so the plan starts from what is true now.
1,312 constraints in a typical regional network
Planning agents branch from today's plan, each pulling a different lever. Re-sequence, rebalance, substitute, split, defer. Most branches are bad. That's the point; the good ones only show up when you try the bad ones too.
10,000 candidates in under 40 seconds
Every candidate runs against the model through the next 14 days. Cost, service, labor and risk are scored with your weights, set by your planners, not ours.
4 objectives, weighted by you
The frontier narrows to a few plans that are each best at something. Orrery says what each one costs, who it protects and what it puts at risk, in sentences your CFO can check line by line.
Every number links to its source row
A dock goes down, a driver calls out, a supplier slips. Orrery sees it in the event stream, repairs the plan from where it stands and asks a person before anything ships.
Median re-plan: 38 seconds
Measured against the same quarter a year earlier, with the customer's own numbers. Names and figures are shared with permission.
−31%expedite freight in one quarter
Our planners used to spend Monday rebuilding the plan Friday's shortages broke. Now they spend it choosing between three good plans. That's a better argument to have.
97.6%on-time in full, up from 91.2% in 20 weeks
The explanations sold it. When Orrery says plan B costs $4,180 more and protects 37 priority orders, my CFO can check every one of those numbers herself.
9 hplanner hours a week on re-planning, down from 46
Dispatch still makes the call. They just stopped making it at 4 a.m. with a whiteboard and a phone.
Move the sliders to match your operation. The math is printed below the result, so you can argue with it.
Illustrative annual value
$0
a yearIllustrative only. These assumptions are medians from 14 pilots, not a promise. In a pilot we measure your real numbers against your own baseline.
Orrery reads from your systems of record and writes back only after a person approves. No rip and replace, no second source of truth.
Orrery
ERP
Approved plans write back through the same connection.
Here is where we are, including what isn't finished. Ask for any report and we'll send it under NDA the same day.
| Control | Detail | Status |
|---|---|---|
| SOC 2 Type I | Report dated 14 March 2026. Available under NDA. | In place |
| SOC 2 Type II | Observation window opened 1 July 2026. Report expected February 2027. | In progress |
| Single sign-on | SAML 2.0 and OIDC on every paid plan, with SCIM provisioning. | In place |
| Data residency | US (Oregon) or EU (Frankfurt). Data and backups stay in region. | In place |
| Encryption | TLS 1.3 in transit, AES-256 at rest, a key per tenant. Customer-managed keys on Enterprise. | In place |
| Your data | Trains your models only. Never pooled across customers, never sent to outside model providers. | In place |
| Penetration test | Annual, by an outside firm. Last completed May 2026; summary letter on request. | In place |
| Deploy in your cloud | Single tenant today on Enterprise. Your own cloud account is on the 2027 roadmap. | Planned |
| ISO 27001 | Planned for 2027. Not started; we would rather finish Type II first. | Planned |
Everything in the app is in the API. Start a run from your own tools, stream its progress, read the frontier and request approval.
import osfrom orrery import Orrery client = Orrery(api_key=os.environ["ORRERY_API_KEY"]) # Re-plan the western network after a supplier sliprun = client.runs.create( network="northgate-west", trigger={"type": "inbound_delay", "po": "88213", "hours": 48}, objectives={"cost": 0.4, "service": 0.5, "labor": 0.1}, horizon_days=14,) for event in run.stream(): print(event.kind, event.summary) best = run.frontier()[0]print(best.explain()) # the trade-off, in plain languagebest.request_approval(approvers=["network-planning"])import { Orrery } from "@orrery/sdk"; const orrery = new Orrery({ apiKey: process.env.ORRERY_API_KEY }); // Re-plan the western network after a supplier slipconst run = await orrery.runs.create({ network: "northgate-west", trigger: { type: "inbound_delay", po: "88213", hours: 48 }, objectives: { cost: 0.4, service: 0.5, labor: 0.1 }, horizonDays: 14,}); for await (const event of run.stream()) { console.log(event.kind, event.summary);} const [best] = await run.frontier();console.log(await best.explain()); // the trade-off, in plain languageawait best.requestApproval({ approvers: ["network-planning"] });# Re-plan the western network after a supplier slipcurl https://api.orrery.example/v1/runs \ -H "Authorization: Bearer $ORRERY_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "network": "northgate-west", "trigger": { "type": "inbound_delay", "po": "88213", "hours": 48 }, "objectives": { "cost": 0.4, "service": 0.5, "labor": 0.1 }, "horizon_days": 14 }' # Stream the run as server-sent eventscurl -N https://api.orrery.example/v1/runs/run_7Hq2/events \ -H "Authorization: Bearer $ORRERY_API_KEY"Everyone who needs to see a plan can see it. You pay for planning runs; one run re-plans your whole network against what is true right now.
Most regional distributors use 1,500 to 4,000 a month.
Estimated monthly cost
$8,060
$24,000 flat
90 days
One site or one slice of your network
From $6,500 a month
Includes 1,000 runs, then $2.40 a run
Up to 25,000 runs a month
Volume pricing
Above 25,000 runs, or special terms
Multi-region networks and regulated data
What shipped, when. We post every release here, including the boring ones.
v4.12
A late truck now starts a repair run on its own. Approval rules still apply, so nothing ships without a person.
v4.11
Plain-language summaries in two more languages, with every number still linked to its source row.
v4.10
Create, update and remove Orrery users from your identity provider with SCIM 2.0.
v4.9
Seniority bidding, minimum rest and overtime caps as hard constraints, written from the agreement text.
v4.8
Replay any plan against the last 90 days of what actually happened and see where it would have broken.
Trust
Our observation period started. The report is due February 2027.
v4.7
Frankfurt is generally available. Data and backups stay in the region you choose.
v4.6
Streaming iterators and typed frontier objects. The 1.x SDK keeps working until May 2027.
Orrery was started by planners and solver engineers who got tired of plans that died on Tuesday. Series A, $24M, March 2026.
CEO
Ran network planning for a 900-truck grocery distributor for nine years. Still keeps the whiteboard.
CTO
Built crew-scheduling solvers for a regional airline, then the simulation platform at a warehouse robotics company.
Chief Scientist
PhD in stochastic optimization. Writes the part of the engine that says when it isn't sure.
31 people in Pittsburgh and remote across US and EU time zones.
We'll replay it in Orrery with your data, under NDA, and show you what it would have done. 45 minutes with a solutions engineer who has run a planning desk.
Request received. This is a demo site, so nothing was sent and nobody will call. On the real site this would confirm your slot by email.