Onymos

The conventional arc of a software business is: get the customer, get the customer's data, and then the data becomes the moat. Your data trains the model, powers the analytics, and makes leaving expensive. Onymos, founded in Palo Alto in 2017 by Shiva Nathan, decided to run that logic in reverse. Its software is built on what it calls a "no-data architecture" - the company says it does not access, capture, or store customer data, which instead stays inside the customer's own environment, on-premises or in their own cloud.

If you are an enterprise, and especially if you are a hospital or a diagnostic lab governed by HIPAA, the scariest slide in any vendor review is the data-flow diagram: where does our data go, who touches it, what happens if they get breached. Onymos's answer is to delete the slide. There is no flow because the data does not move. That is either a clever compliance posture or a genuinely different way to build software, and Onymos would like you to believe it is both.

The product wrapper for this is "Features-as-a-Service," a phrase Onymos has used to describe itself as, immodestly, the "world's first." The idea is that every app team on earth keeps rebuilding the same load-bearing parts - login, biometrics, chat, notifications, data storage, location - and none of that work is a competitive advantage. It is just tax. Onymos sells those features as drop-in modules, each bundled with UI components, backend logic, and cloud functions that run on AWS, Azure, or Google Cloud.

The sales argument is about sprawl. "Software-as-a-service sprawl creates complexity and a lack of visibility for enterprises and their apps," Nathan told TechCrunch when the company raised its Series A. Instead of wiring your app to a dozen third-party SDKs - each with its own updates, outages, and OS-compatibility quirks - you build against one integration layer. When Apple changes something in iOS, in theory, Onymos absorbs the breakage so your team doesn't.

The name is not an accident. "Onymos" is deliberately the antithesis of "anonymous," which is a fun bit of branding for a company that then goes on to build its reputation on not knowing who your users are. There is a tidy irony there: a company named for being known, whose product is designed to know as little as possible.

Nathan is not a first-timer. Before Onymos he led Intuit's Platforms & Services organization and held technical leadership roles at Oracle and CA. That is a background heavy on the unglamorous middle of software - the platform layer, the shared services, the stuff nobody demos on stage. Onymos is, in a sense, that career philosophy turned into a company: the belief that the reusable plumbing is where the leverage actually lives.

The other unusual move is on lock-in. Enterprise software's quiet business model is that switching costs do the retention work for you. Onymos, by contrast, will license you the underlying source code and let you deploy it inside your own infrastructure. If you want to walk, you can take the code with you. It is the kind of concession that sounds reckless in a pitch meeting and turns out to be a reason risk-averse buyers say yes.

The through-line is intake: the moment messy, real-world information - a faxed requisition, a photographed insurance card, a sensor reading - crosses the threshold into a system that expects it to be clean. That threshold is where errors are born and where they are cheapest to kill. Onymos has quietly rebuilt its whole story around owning it, landing on the tagline "The Lab's Intelligent Intake Layer."

For a lab tech, the practical effect is prosaic and welcome: instead of a clipboard and a keyboard, you get structured data that has already been read, checked, and cross-referenced. It is automation aimed at drudgery rather than headcount, which is the version of automation people tend not to resent.

Onymos is a small company - roughly 26 people - selling into large, regulated ones. Its publicly referenced customer and partner logos skew toward healthcare, life sciences, and retail pharmacy, the industries where paperwork is heaviest and compliance is least forgiving.

That is the lean-infrastructure playbook: you do not need to be big to be load-bearing. You need to solve one expensive problem so completely that a Fortune 500 buyer is comfortable putting it in the critical path. The globally distributed team - Palo Alto plus India, Singapore, and Iceland - is how a company this size covers that much ground.

The Series A landed after a year in which Onymos says annual recurring revenue grew more than 300%. That is the demand signal investors were buying: not just a clever architecture, but evidence that enterprises are tired enough of SaaS sprawl to consolidate onto fewer, deeper vendors.

Third-party sources estimate annual revenue in the neighborhood of $5.5M. The company has not disclosed a valuation, and figures like these should be read as approximate rather than audited.

Onymos describes its culture as inclusive and problem-focused, built around a distributed team and a heavy emphasis on developer experience. For a company selling to engineers, DevX is not a nicety - it is the product surface. The advisory bench has drawn from Twilio, Benhamou Global Ventures, Arcutis Biotherapeutics, and Varian Medical Systems, a mix that tracks with the pivot from horizontal app tooling toward regulated healthcare.