Early access design partners only
Explore the public demo now. Production use is currently available to selected Design Partners only. Apply today!

Stop coordinating production
in spreadsheets

Orkyo is production scheduling software for manufacturing teams — one plan for the machines, people, and tools that run your jobs, so work gets scheduled, conflicts get caught, and capacity doesn't go to waste.

For production planners, operations managers, and workshop leads.

Prefer to self-host? Get the Community Edition on GitHub.

Shop floors run on limited resources.
Do you still track them by hand?

Jobs compete for the same resources

Machines, tools and equipment, and skilled people are limited. When planning happens in emails and spreadsheets, conflicts are discovered too late — after commitments are made.

Coordination overhead grows with scale

More sites, more teams, more products means more meetings, more version-of-truth problems, and more time spent chasing status updates instead of planning.

Utilization is invisible until it hurts

Underused capacity and overloaded machines both cost money. Without a central view, it's hard to see either until a delivery date slips.

Running a machine shop? See how Orkyo schedules jobs onto machines. Running a job shop? See job shop scheduling.

Plan. Assign. Ship.

1

Define your resources

Pick the kinds of resource you run — mills, benches, people, forklifts — or define your own. Set capabilities, availability, and site assignments once, and Orkyo uses them every time.

2

Submit and schedule jobs

Teams submit jobs as structured requests with requirements. Orkyo matches them to available resources, flags conflicts before they're committed, and builds a shared plan.

3

Track utilization in real time

See exactly what's booked, what's free, and where bottlenecks are forming — across all your sites — without chasing updates from individual teams.

Everything a production team needs.
Nothing they don't.

Job and request management

Every job enters as a structured request with its requirements attached. Orkyo matches it to the right resources, routes it through approval, and turns it into a scheduled plan.

Visual floorplan scheduling

One plan per site, holding everything that stands on it. Drag to place, draw to add, and see what's allocated, what's free, and what's in conflict at a glance.

People scheduling

Schedule skilled people the same way you schedule machines — with capability matching, groups and job titles, and absence handling built in.

Your types, your fields

Activate the resource kinds you run from a catalog, or define your own. Give each one the fields it needs, and keep its reference data — departments, maintenance history — as lists that belong to it.

Conflict detection

Catch double-bookings, capability mismatches, and overloads automatically — before requests are committed, not after delivery dates are missed.

Utilization and capacity tracking

See where your production capacity is going — and where it's being wasted. Make planning decisions based on data, not estimates.

New

Break a job into steps, and put them in order

Draw the dependencies between the tasks of a job and Orkyo holds each one until the work it waits for is done. A task can wait for all of its predecessors, for any one of them, or for a number you choose — so a delivery from either supplier releases the next step. Canceled work drops out of the condition instead of blocking the job forever. How dependencies work

Orkyo plan canvas: the eleven tasks of a line changeover as cards joined by arrows, one task marked ANY because either vendor delivery releases it, and another marked 2 OF 3.
A line changeover on the plan canvas. ANY releases the fixture mount on either vendor delivery, and the canceled task drops out instead of blocking the job.
New

Talk to your schedule

Hand the assistant a backlog and it plans the site. Ask why a job is in conflict and it answers in plain language, opens the page it is talking about, and applies the fix on your approval. It runs on your own Anthropic API key — or point any MCP client at your workspace instead, because Orkyo speaks the Model Context Protocol. Tokens are read-only until you say otherwise, and every change obeys the same rules your team works under. How the assistant works · How API & AI access works

The Orkyo assistant panel open beside the week calendar, reporting the unscheduled queue, naming the request that comes next, and flagging that 328 requests share one repeating conflict.
The assistant reads the plan and answers in plain language — here it finds a pattern behind 328 conflicts instead of one bad booking.
New

See what is holding the plan back

The bottleneck report ranks the stations and people that are overbooked, in hours, so you know which constraint to relieve first. Beside it runs the critical path — the chain of work that decides the finish date, with the float on every other request. Work with float can move. Work on the path cannot.

Orkyo bottleneck report: bar charts of the most overloaded stations and assets by hours overbooked, above a critical path table of 57 days end to end with the float on each request.
Overload in hours, and the 57-day chain that sets the delivery date.

See it on your own shop floor

Explore the public demo now. Production use is currently available to selected Design Partners only — multi-site support and GDPR-ready, hosted by us or self-hosted on your own infrastructure.

Orkyo floorplan view of a machine shop: machining cells, assembly and quality stations drawn on the plan, each one bookable.
A seeded demo facility. Every station drawn on the plan is a resource work gets booked onto — and every view above reads from the same one.
Free — up to 5 seats
Cloud — hosted & managed
Self-host — open source