Arhas · About
Three products, held to one standard.
Arhas builds BRUTAL Optimizer, MedOS and LabOS — a Windows optimizer, a hospital system and a laboratory system. They share no code, no market and no runtime. They share a rule.
01 — What Arhas is
A parent company that adds a rule, not a logo.
Arhas is the parent of three products. It is not a platform, a suite or an ecosystem. The products do not share a database, a design system or a language — one is a native Windows application in C#, two are web applications on Cloudflare Workers. Nothing technical joins them.
What joins them is who buys them. A gamer with one PC. A two-doctor clinic. A single pathologist. None of those buyers has a procurement committee, an IT team or a security reviewer, and none of them can check whether the vendor is telling the truth. The industry has priced that in and built a market where the claim on the website is the only thing you get.
So the parent exists to hold one line across all three: a guarantee that lives in a settings tooltip is a promise, and a guarantee that lives in the code path is a fact. We ship the second kind, and we publish where to look.
Read the standard in full02 — The obvious objection
Why does a PC optimizer sit next to a hospital system?
It is the first thing a hospital owner asks, so it gets answered before the third paragraph rather than buried under a values statement.
The three products do not share a market. They share a buyer with the same problem: no way to audit the vendor. And gaming is where that problem gets caught fastest.
A gamer with one PC will run the benchmark. They will screenshot the result, post it, and say plainly that the optimizer did nothing. A clinic owner will not. A pathologist will not. The optimizer market is a landfill of placebo precisely because it is the one market where the placebo gets found out — and the vendors ship it anyway.
A product sold into gaming is disciplined by its buyers whether it likes it or not. Our argument is that the same discipline belongs in the two markets where nobody is checking. BRUTAL Optimizer is not an odd neighbour to MedOS and LabOS. It is the evidence that the standard survives contact with people who can catch us.
-
BRUTAL Optimizer
PC gamers first, because placebo gets caught fastest there. Then everyone else.
The optimizer market is a landfill of placebo. BRUTAL publishes what it will not ship — no registry cleaner, no RAM booster, no SSD defrag, no guaranteed FPS number — and then makes those refusals structural.
-
MedOS
Two-doctor clinics and small hospitals, with no IT team and no procurement committee.
The hospital software market runs on "request a quote" — a price you cannot see until someone has qualified you. MedOS publishes every price, charges no setup fee, and lets you export your data for 30 days after you leave.
-
LabOS
Single-pathologist labs and diagnostic chains, working to NABL standards.
The old way is results re-keyed by hand, quality control in a spreadsheet, and reports in Word. LabOS labels its own illustrative figures as illustrative — it prints "representative examples shown" under its own screenshots.
03 — Where we operate
India, stated precisely enough to be checked.
The software is built in India. MedOS and LabOS are sold in India, priced in rupees, and written against Indian regulation — PCPNDT blocked at the field, Schedule H1 and X registers written on dispensing, NMC 2023 generic naming, the NABL evidence an assessor will actually ask to see. BRUTAL Optimizer is a Windows application; its buyers are wherever Windows is.
Our terms name Courts in Hyderabad, Telangana, India. That is the single entity fact two independent product legal pages already agree on, so it is the one we are willing to print.
Data residency, in full
- Compute for MedOS and LabOS runs on Cloudflare Workers with a Mumbai placement hint.
- The MedOS database is Turso, in ap-south-1.
- Object storage is Cloudflare R2 — APAC, and not guaranteed to be in India.
Three sentences, where the industry writes one. “All your data stays in India” is shorter, and it is not true of anybody running on this stack. The long version is on engineering.
04 — What this page does not contain
There is no team section here, and that is deliberate.
An about page is normally a founding year, a headcount, five faces and a map pin. We cannot verify a single one of those, and inventing them is exactly the behaviour this company was set up not to have. So the page says what it can source, and lists what it cannot.
- A founding year No incorporation date exists in any record we hold. A plausible year is still a guess, and a guess printed in a serif face is still a guess.
- A leadership section No founder bio, no headshot, no titles. When there is a named person who has agreed to be named, they will be named here and nowhere earlier.
- A headcount No "team of engineers", no number of people. The figure would be flattering to us and unverifiable to you, which is the combination this company exists to avoid.
- An office address The addresses printed on one of our product sites are coworking desks, shipped next to phone numbers that were test data. They are not a registered office and they will not be reprinted here.
- A customer count There are no customers on record. No logo wall, no star rating, no testimonial — and no tenth invented doctor to keep the other nine company.
Software you can check.
We publish the price, the mechanism, and the limits. Then we ship the code that enforces them.