OOMU® Control
By the time you hear about it, twelve people will already be using it.
OOMU is free, including at work, so your people can install it this afternoon without asking anyone. We think that is the right way around. OOMU Control is how the organization gets the wheel: one place to decide who, which models, and what gets written down.
The honest post-mortem
It was never really about the model.
The rollouts that stalled did not stall because the model was not clever enough. They stalled for three reasons, and everyone involved knows what they were.
Nobody could see what it did. Legal asked what happened to the documents and nobody had an answer that survived a follow-up question.
Nobody would give it anything real. So it got the harmless work, produced harmless results, and justified nothing.
The bill grew faster than the benefit. Per-seat, per-question, per-region, plus the consultants brought in to explain the invoice.
There is a fourth reason nobody writes down. It was chosen at the top and handed down, so nobody below ever wanted it.
An agent nobody is allowed to audit is not an asset. It is a liability with a subscription.
OOMU Control
One place to answer the questions you are about to be asked.
Everything below is about the organization, not the person. Your people already have OOMU working the way they want it. Control is how you put a single shape around all of it without taking anything away from them.
- People sign in the way they sign in to everything else Your identity provider and the groups you already keep. Somebody leaves on Friday and their access to OOMU leaves with them.
- You decide which models are allowed Approve the providers you are comfortable with, block the ones you are not, and require that certain kinds of work never leave the machine at all.
- Roles, so not everyone can do everything The finance team and the summer intern do not need the same permissions, and now they do not have to have them.
- A record for the whole organization, in one place What was planned, what was approved, what was done. Exportable to wherever your security people already look, in the format they already read.
- Capabilities you build and never publish Hand three hundred people the workflow your own business depends on without putting it anywhere public, and take it back if you need to.
- Deploy it like software, not like a favor Push the app and its policy to the fleet through the management tools you already run, rather than emailing everyone a link and hoping.
- Spending limits, set before the invoice Cloud budgets by person, by team, or by kind of work. The surprise bill was always the avoidable part.
- Run it on your own infrastructure if your rules say so Inside your own tenancy, with support and response times agreed in writing rather than implied by a status page.
Nothing that keeps a person safe is in that list, and nothing ever will be. Approvals, the sandbox, permissions, and your own local history ship with the free product. Charging you for the safety would turn it into a sales tactic, and then it stops being safety.
Unit economics
The cheapest inference is the kind you already own.
Your organization has already bought a large fleet of capable computers. In most AI deployments they are used as thin clients pointed at somebody else's data center, and you are billed by the question for the privilege.
OOMU inverts that. Everyday work runs on the Apple Silicon machines you have already paid for, at no marginal cost. Cloud models stay available for the jobs that genuinely need them, on your keys and your policy, which turns spend into a decision instead of a surprise.
Budget stops scaling with curiosity. People are allowed to experiment again.
Licensing
The short version, said out loud.
Using OOMU is free, including commercially. An employee, a freelancer working for clients, a whole department that found it on their own. No license, no seat count, no letter from us.
OOMU Control is licensed. You pay when the organization wants to govern OOMU centrally rather than leave it to each person.
Selling OOMU on is a separate matter. Building it into your own product, reselling it, or running it as a service for other people are different rights from using it, and those are licensed too.
OOMU is proprietary software, licensed and not sold. Scope, terms, and support are agreed directly with Eldris.
Have your people try it first. That is usually the fastest evaluation there is.
It is free and it is the same product. Let them use it on something real, then come and talk to us about the fleet.