Ninja
Open the console

Log 07 · named on the record

A logo wall proves nothing.

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.

Named, not implied
T+00:00Named clients
OrganisationWhat it isSector
InfosysOne of the largest technology services firms in the world, and also an investor and the exclusive services partner for this platform.Services
Maverix OncologyAn oncology organisation, in a sector where the deployment boundary is the first question anyone asks.Life sciences
Tulane UniversityA private research university in New Orleans.Education
Queensland GovernmentA state government in Australia.Public sector
City and County of HonoluluA 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.

T+2026-08-04Who puts it in

A platform
does not deploy
itself into a
bank.

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.

Platform

Ninja

The runtime, the memory, the orchestration, the deployment options.

Delivery

Infosys

Integration, change management and scale, exclusively, since August 2026.

Healthcare

Optimum Healthcare IT

The vertical practice for hospital and payer environments.

T+01:00Where the deployments go

The industries
that cannot
send the data
anywhere.

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.

Regulated

Healthcare, life sciences, financial services, insurance, legal

Patient records, client money, privileged material. The boundary is written down somewhere and somebody signs for it.

Industrial

Engineering, construction, manufacturing, supply chain, oil and gas, chemicals

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.

Bring the job
your review
board blocked.

The interesting conversation is the one about where it runs, not the one about what it can write.