The healthcare model router

The generic router just got bought. It still cannot take PHI.

Comet is the hop you put PHI through. One customer BAA. Only frontier labs whose providers will sign. Everything else fails closed.

Why now

Stripe bought the generic router. It still has no BAA.

Stripe agreed to acquire OpenRouter on 19 August 2026. No official sale price. OpenRouter still offers no HIPAA BAA. The multi-model router is now a real category — and it still cannot sit in the BAA chain. That is the door.

The hop

One BAA. Frontier labs that will sign. Fail closed on the route.

You do not stitch five labs. You sign once. Compliance lives on the route — direct API, Azure, Bedrock, Vertex — never the model. If a provider will not offer a BAA, that model never enters the catalog.

01 Request

One interface

A PHI workload enters through a single contracted hop.

02 Policy gate

Eligible set

Only frontier models whose providers offer a BAA. Anything outside fails closed.

03 Frontier route

The contracted path

The BAA sits on the route. The model name does not carry it.

04 Certificate

Optional proof

A related-party Wellnite evaluation, disclosed. DEMO ARTIFACT. Never a HIPAA stamp.

Certificates are Wellnite evaluations of one route doing one job. Related party, disclosed — not independent certification, not “HIPAA certified,” not “BAA active,” not “Comet compliant.”

Team

We’ve already built the hard part.

26,000+

Clinicians globally

Nationwide

MPCs

Indefinite

Wellnite relationship

Paulo Gonzalez and Elisa Swan — both CEO & Co-founder of Wellnite — spent more than seven years building this healthcare infrastructure together. The network is live. The relationship is indefinite.

Who it’s for

Digital health vendors already shipping PHI.

The CTO with a note, a coding pass, or a follow-up in production this quarter.

The ask

Two or three design partners. Ninety days. One workload.

If you already put models on protected health information, take a slot.

Request a design partner slot