BRUTAL Optimizer
Licences, downloads, and anything the application does on your machine. If a module changed a setting you did not expect, this is the address — every module records what it touched, so we can tell you exactly what happened.
Arhas · Contact
Reach the product, not the parent.
Support for a product is answered where the product is built. Those three addresses are real and in use today. The Arhas mailbox is not, so it is not printed here — it is marked as missing instead.
01 — Product support
Three products, three mailboxes.
A parent-company inbox that forwards your ticket to the same engineer two days later is not a service. Write to the product.
MedOS
If you run MedOS in a clinic or a hospital: accounts, billing, migration, and questions about what the software will and will not let you record.
LabOS
LabOS has no mail domain of its own yet, so it uses the MedOS one. That address is the one printed on the LabOS site today, which is why it is the one printed here.
supportEmails — src/data/company.ts. These three are published because they exist; every other address you might expect on this page does not.
Product sites: brutaloptimizer.com med-os.in lms.med-os.in
02 — Security and everything else
A vulnerability has its own route. Use it.
Report a vulnerability
If you have found a security issue in BRUTAL Optimizer, MedOS or LabOS, the canonical route is our security.txt. It names the address, the policy and what you can expect back. Please do not open a public issue, and please do not publish a working proof of concept before we have replied.
If that file does not yet name a mailbox — see the block beside this one — send it to the support address of the affected product with security in the subject line, and hold the details until someone answers.
/.well-known/security.txtThe Arhas mailbox
[general mailbox pending verification]
There is no monitored mailbox on the arhas.in domain yet. We could invent a plausible one, print it in the footer, and find out later how many people wrote to a room with nobody in it. An address that nobody reads is a worse outcome than an honest gap, so the gap is marked and left open until the mailbox exists.
Press and partnerships in the meantime: the kit, the boilerplate and the full claims register are on the press page, and everything on it is cleared for quotation without asking us first.
src/data/company.ts — email.general and email.security are unverified
03 — What is not on this page
The four things a contact page usually has, and why this one has none.
None of them is missing by oversight. Each one would require us to publish something we cannot stand behind, on the page where a stranger is most likely to trust us.
- A phone number Every phone number in our own repositories is test data — placeholders that were shipped next to coworking addresses on a product site. None of them rings anywhere. A number that does not answer is worse than no number, so there is no number.
- A contact form arhas.in is a static site with no backend. A form here would post to nothing, or to somebody else’s service. A form that accepts your message and silently discards it is precisely the kind of software this company exists not to ship, and we are not going to open with one.
- A quote form There is nothing to unlock by talking to us. Every self-serve price is published on the product that charges it — ₹699 for MedOS, ₹999 for LabOS — and no published price moves because of who is asking. LabOS quotes its top Enterprise tier rather than printing it, which is stated on the product; a form on this page would not get you a better number on any of the others.
- A chat widget A third-party script, a set of cookies, and a bot answering in the first person as though it were a colleague. We would rather you had an email address that reaches a person.
When the mailbox exists, it will appear here in plain text.
Not behind a form, not behind a bot, and not behind a qualification call. The same way the prices are published on the products that charge them.