Partners

Lumepath builds the platform. Partners bring it to market.

Signet is licensed, not retailed. A delivery partner takes the platform, puts its own name, logo and wording on every surface, and owns the clinic and employer relationships.

Who for

Partners put their name on every surface.

Organisations that sell and operate screening programmes. Laboratories and employers come through partner channels — not as direct Lumepath buyers. Lumepath does not sell to patients.

Screening is a pipeline with a doctor in the middle — admit, hold unsafe work, named clinician release, patient report, employer aggregate at k ≥ 10. Partners licence Signet under their own brand; Lumepath stays behind it.

What you licence

Signet — one stack, four stages.

You licence the mechanism: Intake, Hold, Compose, Deliver — including the refusals and receipts that make the pipeline defensible in diligence. Hold rules, signed lineage and the privacy floor are platform invariants; branding, templates and integrations are set per partner.

Stage walk and refusals: Signet — what arrived, why it waited, what was sealed, and who received what.

Four brand surfaces under your name:

  • A workspace for the clinic team
  • A private smart report for each patient — clinician-signed before the patient path opens
  • An aggregate for the employer (privacy floor k ≥ 10)
  • Partner operations / client-success console — jointly configured on first licences; full self-serve ops console as product direction

Device boundary, named clinician release and fail-closed Hold: Signet · Boundaries · Hold.

Keeps / owns

What Lumepath keeps. What the partner owns.

  • Lumepath keeps The pipeline (Intake, Hold, Compose, Deliver), fail-closed behaviour, hold rules, signed lineage, byte-identical regeneration, and the privacy floor (k ≥ 10, raiseable by the tenant, never lowerable). Those invariants are the same for every partner. Lumepath’s inbound market is partners only.
  • Partner owns Brand, wording libraries, clinic-signed languages and templates, market access, clinic and employer relationships, local operations, sales motion, and post-sale support to their clients. Lab and CMS integration ownership sits on the partner side; Lumepath can assist on first licences.

Laboratories and employers reach Signet through the partner’s channel. Lumepath does not sell to patients and does not pitch laboratories or employers as direct buyers.

White-label

Joint configuration first; self-service as direction.

First licences are configured jointly with Lumepath — brand, wording, templates and surfaces set together. The product direction includes self-service branding so your team can take more of that work over time.

  • First licences — joint configuration. First programmes are not blocked on self-service being finished.
  • Direction — self-service branding and a fuller self-serve ops console, so operators can run Signet without Lumepath in the room.

We do not publish portal screenshots or claim a finished self-serve product.

Commercial

Deal by deal. No single default.

No list price, no standard package, no default revenue split. Structure first; figures only in a private schedule. Write to hello@lumepath.ai.

Three fee types appear across deals:

  • Joint-configuration / implementation — one-time brand and configure on first licences
  • Platform fee — right to run Signet (SaaS or dedicated), support band, included allotment
  • Usage — volume beyond allotment (released reports, clinics, or an agreed schedule unit)

Options A–E below. Mix by deal; no single default. Option E needs deal-level approval before quoting — ceiling and fair-use stay in the private schedule.

Option Shape When it often fits
A Annual platform Partner-wide; heavy joint config
B Per report Pilots / uncertain volume
C Per clinic / site Clinic go-live as sales unit
D Platform + usage Commitment floor; fair scale
E Platform only High volume; approval + ceiling before quoting

Cloud

Cloud-agnostic; SaaS ships first on GCP.

SaaS ships first on GCP; residency named per deployment against the clinics you serve. Other clouds or self-hosted (client KMS) are deal terms — not a second product.

Residency follows the clinics you serve. Exact hosting terms are confirmed in contracting. See Trust · Residency for the exception-honest posture.

Markets

Global, partner-led — not framed around an HQ city.

Workforce and clinic-led screening programmes are licensed through delivery partners wherever they already operate. Lumepath does not open a geography itself.

Primary focus: United States; Southeast Asia (Singapore). Focus names where partners already operate. It is not an HQ map and not a committed rollout.

Local-language clinical text ships only with clinic-signed content — the same rule in every market.

Residency is named per deployment against the clinics served. A listed market is not a claim that every row already sits in that market. See Trust · Residency.

Further markets open through partner conversations — not as Lumepath-direct laboratory or employer sales, and not as open geographies Lumepath announces alone. Write to hello@lumepath.ai. Hong Kong / Greater Bay Area stays off the outbound list.

Diligence

What partners can show without inventing proof.

A released document stays a fixed record. Diligence answers sit in the product: fail-closed holds, receipted release, byte-identical regeneration, k ≥ 10 employer views, residency named per deployment.

  • Forward Trust — send Trust (and Residency) to IT / DPO / security. Built-as-is controls — no compliance badges.
  • Security questionnaires — we answer partner review questionnaires directly. Ask for the partner DD pack at hello@lumepath.ai.
  • Assurance — SOC 2 Type II and independent penetration testing programmes in place / commencing. Controls are operated to that bar. We name a framework as certified only when a deployment has been audited against it — not as completed certificates here.
  • Stage walkthrough — walk medical directors through the four stages on Signet: what arrived, why it waited, what was sealed, and who received what — including that AI-assisted interpretation and smart reports sit in Compose behind named clinician release and fail-closed Hold.
  • Clinical posture — device boundary, named clinician release and fail-closed Hold on Signet · Boundaries and Hold.

We do not publish customer names, logos, testimonials or usage counts. We do not claim named lab, CMS or IdP integrations without a proved endpoint. Prices are deal by deal — not listed here. Residency answers stay exception-honest on Trust · Residency.

Stage

Signet is live. A new generation is under active build.

What partners licence today is production software. What is under build is the next generation of the same line. We do not publish customer names, logos or usage counts.

Delivery partners: write to the partner team.

Signet · Trust and residency · Boundaries · Hold