Licensing
Commercial models for how you adopt the central layer.
Licensing maps to deployment reality: direct clinical programs, platform embedding via API, or partner distribution. The infrastructure story is consistent—managed intelligence, tenant-scoped operation, integration depth that matches your team and procurement needs.
How to choose
How to choose the right path.
Use these prompts in internal alignment and with our team—they are decision aids, not a self-serve matrix. If two paths apply, we usually start with the one that matches who owns the integration contract and customer relationship.
Where does the workflow live today?
- Mostly inside your own product or EHR/LIMS — you need APIs, webhooks, and predictable volume.
- Mostly in a clinical or operational team using FI’s surfaces — you need seats, governance, and training.
- You resell or embed intelligence for your customers — you need branding, packaging, and partner economics.
Who owns integration and uptime expectations?
- Your platform team owns the integration contract and SLAs — lean Enterprise API with clear rate and support tiers.
- Your clinical ops owns day-to-day use; IT still needs auditability — lean Clinic with documented security review.
- Your product org owns roadmap and customer comms — lean White-label with co-built templates and enablement.
How deep is the intelligence layer in your story?
- Back-end scoring and reporting behind your UI — API-first packaging.
- Visible audit and benchmark program for providers — clinic packaging with review queues and dashboards.
- Differentiated offering under your brand — partner program with commercial and technical alignment.
Technical patterns: see Integration. Security and diligence: see Security.
Models
Who each model is for.
Each column is a packaging and responsibility split. Features and deployment lines are representative—exact entitlements are in your order form or MSA.
Specialist practices, trichology clinics, and single-site or small-network operators running a structured HairAudit / procedural audit program—not building a custom integration stack.
You consume Follicle Intelligence as the managed central layer: ingestion, scoring, reporting, and governance surfaces without owning API middleware. Multi-tenant cloud by default; isolation and retention per agreement.
- Full pipeline: evidence ingestion, scoring, reporting, and review queues
- Administrative dashboard for case flow and visibility
- Practitioner seats sized to practice scale
- Support and documentation appropriate to clinical operators
Managed cloud (multi-tenant)
Health systems, diagnostic platforms, labs, and product teams embedding Follicle Intelligence into existing workflows—your UX, our scoring and benchmark depth behind authenticated APIs.
The same intelligence core as the managed product, exposed for your stack: REST ingestion and scoring, asynchronous jobs, webhooks, and tenant-scoped keys. Volume, regions, and dedicated options are contractual—not one-size-fits-all.
- REST APIs for ingestion, scoring, and report generation
- Webhooks and job polling for long-running work
- Volume licensing and configurable rate limits
- Support and SLA options by agreement
Cloud API or customer-influenced environments (by agreement)
Software vendors, EHR/LIMS providers, and platform builders who distribute audit and benchmark capability as part of their product—your brand, shared roadmap, partner economics.
Partner programs align packaging with how the central layer is embedded: branded surfaces, template and report customization, and integration support so your customers see continuity with your stack, not a bolt-on.
- Branded experience: partner-controlled UI and reporting surfaces
- Templates and commercial packaging co-defined with your roadmap
- Integration support for your application stack
- Partner programs (enablement, commercial terms) as agreed
Cloud or dedicated (by agreement)
Packaging
Aligned with the infrastructure story.
Licensing should read as a consumption choice on one platform—not three disconnected products.
One intelligence core
Clinic, API, and partner paths differ in who hosts the UX and who owns integration—not in pretending to be separate products. Packaging reflects consumption model and governance.
Tenant and contract boundaries
Isolation, data residency, subprocessors, and SLAs are expressed in your agreement. This page orients buyers; it does not replace legal or security review.
Seat counts, SLAs, security exhibits, and regional terms are set in contract. For platform context, see Platform. Start with contact for a scoped conversation.
Follicle Intelligence™ connects HairAudit (surgical evidence and audit surface), Hair Longevity Institute (biology and longitudinal treatment intelligence), and IIOHR (methodology, training, standards, and governance alignment).