Healthcare, life sciences, financial services, insurance, legal
Patient records, client money, privileged material. The boundary is written down somewhere and somebody signs for it.
Log 07 · named on the record
So here is the list written out instead, with what each of these organisations is, and who does the work of putting it in. Five names, one services partner, one healthcare partner. That is the honest size of it.
| Organisation | What it is | Sector |
|---|---|---|
| Infosys | One of the largest technology services firms in the world, and also an investor and the exclusive services partner for this platform. | Services |
| Maverix Oncology | An oncology organisation, in a sector where the deployment boundary is the first question anyone asks. | Life sciences |
| Tulane University | A private research university in New Orleans. | Education |
| Queensland Government | A state government in Australia. | Public sector |
| City and County of Honolulu | A municipal government in Hawaii. | Public sector |
Two governments and a university in the client list is not an accident. Those are exactly the buyers whose answer to "can our records go to your cloud" is no, and who therefore need a product that can run inside their own.
In August 2026 Infosys invested through its innovation fund and became the exclusive professional services partner, for at least a year.
That is the part of an enterprise rollout that a small engineering team cannot do: the process mapping, the change management, the people in the room for six months. For healthcare specifically, delivery runs through Optimum Healthcare IT, an Infosys company.
The runtime, the memory, the orchestration, the deployment options.
Integration, change management and scale, exclusively, since August 2026.
The vertical practice for hospital and payer environments.
The published industry list runs through healthcare and life sciences, financial services and insurance, legal, engineering and construction, manufacturing and supply chain, oil and gas, and chemicals. They have one thing in common, and it is not their workflows.
Every one of them holds records that a policy, a regulator or a contract says must stay inside a boundary. That is the reason a deployment option is a product feature here rather than a footnote on the pricing page.
Patient records, client money, privileged material. The boundary is written down somewhere and somebody signs for it.
Long processes, many systems, and documents nobody has read since they were filed.
Client names, the partnership and the industry list are taken from NinjaTech's own public pages and its own blog. No customer outcome, deal size or metric is claimed here, because none is published.
The interesting conversation is the one about where it runs, not the one about what it can write.