Olyron health suite
Olyron
Identity for
health systems.
One login for clinics, care teams, and health products. Accounts, CRM, Labs, and Browser share the same org graph, so clinical ops and member lifecycle stay coherent.
Identity is the operating system for care.
Olyron Accounts sits at the center: the org graph, SSO, RBAC, and audit. Every health product (CRM for members, Labs for clinics, Browser for care-team sessions) inherits the same control plane.
Olyron Accounts
SSO, org graph, RBAC, JWTs, audit: the substrate under every health app.
Health suite apps
CRM, Labs, Browser: one org graph, one audit trail.
Health stacks weren’t designed to share a patient.
Clinics and health orgs run disconnected tools for roster, CRM, and browser access: stitched by integrations that drift. Olyron replaces the stitching with a shared identity substrate.
A stack of disconnected health tools
- Clinic software, CRM, and browser tools with separate logins
- Parallel patient and member records that never stay in sync
- Consent and HIPAA posture scattered across vendors
- Every compliance question becomes a cross-vendor audit
- Per-seat pricing that punishes growing care teams
- Security posture stitched together from screenshots
One substrate under every health app
- One org graph: the same person across CRM, Labs, and Browser
- One identity, one bill, one audit trail for the health stack
- Native cross-app context for clinics, members, and care teams
- Identity events feed security and consent posture in real time
- Bundle pricing that scales with the organization
- Tenant isolation, RLS, and SOC 2 posture built into the platform
Identity for health systems
Accounts is the platform. CRM is included. Labs and Browser are add-ons. Every app reads the same org graph, and more health apps can join later.
Platform Accounts · Included CRM · Add-ons Labs, Browser
The details that separate us.
Eight proof points your CTO will quiz us on during diligence, answered up front.
Substrate
Org-aware JWTs
Every call carries org_id, role, tenant_id, and scopes. Downstream APIs enforce context without guesswork.
Shared graph
One customer record
CRM, Labs, and Browser all read the same org graph. No sync jobs, no dual-entry, no drift.
90+ permissions
RBAC built for audits
Granular scopes per app plus user impersonation for support. Audit-ready out of the box.
Pipeline AI
Lead scoring that explains itself
Conversion probability on every deal with engagement signals, not a black-box score.
Browser
Governance on the same graph
Identity-aware sessions and entitlement-gated tiles under your org identity, same Accounts login as CRM and Labs.
Health-built
Every module earned its place
Each product exists because clinics and health teams hit a real operational pain: not a generic SaaS guess.
Supabase core
Postgres + RLS + pgvector
Tenant isolation, row-level security, and cross-app AI memory on a platform your engineers already know.
Edge everywhere
Sub-100ms globally
Vercel Edge + Supabase Edge Functions route every call to the nearest region before it hits Postgres.
See what your team gets
From org dashboards to SSO consent. Every surface is built for speed, clarity, and trust.
12
Members
3
Pending invites
5
Registered apps
Quick actions
Invite a teammate
Add members with roles
Register an app
Set up "Sign in with Olyron"
Org settings
Name, slug, config
Built for the health stack.
Accounts, CRM, Labs, and Browser on one identity substrate: priced as a bundle, deployed independently, unified by design.
Products
One identity substrate
Org graph
Every app reads the same record
RBAC permissions
Granular per-app scopes
p99 latency target
Edge compute globally
Every health org we’ve watched hit the same wall: clinic software, CRM, and browser tools. Separate logins, separate invoices, parallel patient records. Olyron treats that as one identity problem, not six vendors.
Why we built it
The moat health stacks can’t retrofit.
Identity isn’t a feature on Olyron. It’s the substrate. Once a clinic or health org runs on Olyron Accounts, every additional app (Labs, CRM, Browser, and future health products) drops in with zero integration cost.
Olyron Identity
Authentication, organizations, invitations, OAuth consent, and cross-app SSO. Claims enriched with org context so downstream services inherit the same security bar, automatically.
SSO & OAuth consent
Hosted flows with explicit approvals, ready for enterprise procurement reviews.
Org-aware JWTs
Claims carry active org, role, and tenant so APIs enforce context without guesswork.
RBAC memberships
Owner, admin, member, billing, and read-only, plus 90+ granular per-app scopes.
Tenant isolation
RLS-first patterns for multi-tenant SaaS. Dedicated projects available for Enterprise.
Bundle pricing. Transparent. Scales with the org.
Accounts is the platform. CRM is included. Labs and Browser switch on as add-ons. More health apps can join the same graph later.
Starter
Accounts + CRM. The foundation for clinics and care teams.
- Olyron Accounts (Platform)
- Olyron CRM (Included)
- Up to 10 seats
- Email support
Growth
Clinical ops + governance. Built for growing health orgs.
- Everything in Starter
- Olyron Labs (Add-on)
- Olyron Browser (Add-on)
- Up to 50 seats
- Priority support + SLA
Enterprise
Full health suite, dedicated infrastructure, compliance posture.
- Full suite: Accounts, CRM, Labs, Browser
- Dedicated Supabase project
- SOC 2 Type II, HIPAA BAA
- Custom SLA, named account team
See the full pricing matrix for platform, included apps, and add-ons.
Open the suite
Jump straight into each live Olyron product. Same Accounts login across the graph.
Ship on the same substrate we use.
Register your app, validate redirect URIs, and exchange one-time codes for org-aware profiles. Your roadmap stays on product. Identity, RBAC, tenancy, and audit come from the platform.
// Exchange SSO code for an org-aware user profile
const res = await fetch("https://accounts.olyron.com/api/sso/token", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({ code, app_key: "your_app" }),
});
const { user, org, role, scopes } = await res.json();
// → user.id, org.id, role, scopes[] all flow through JWT claimsReady for identity-native health systems?
Pilot clinics and care teams onboard in Q3 2026 with 50% launch pricing. Commercial licensing opens January 1, 2027. Let’s talk.
Request early access
Interested in partnering?