00The platform

Five pillars. Three unlocks. Production-shipped.

A multi-tenant API, a pluggable flow runtime, a clinical memory architecture, and an AI Computer Use layer that integrates with any EHR in days. Built for platforms that need depth they can't afford to build. Inspect what you'd embed.

Engine signal
Shipped, not roadmap
4
Production deployments running today.
15+
Therapeutic flows running in production.
100K+
Structured clinical data points captured.
Day 1
HIPAA / GDPR / 42 CFR Part 2 / SOC 2.
01Five pillars

Five pillars. Each one a 12-month build.

Most competitors ship one or two. Cuepri ships all five, plus the runtime that lets your team add more without touching the engine.

P.01

Engagement

Fifteen-plus clinical flows running in production. Voice mode, interactive widgets, real-time personalized meditations. Multi-model AI with automatic failover. 84% session completion.

P.02

Memory

A cognitive architecture, not RAG-with-vectors. Extraction pipelines, entity-relationship graphs, cross-session pattern detection. Years of clinical AI R&D, embedded.

P.03

Alerts

Two-tier alerts with contextual validation. Crisis (CSSRS), dropout (ARI), step-down readiness (SRI), struggling, medication concerns. 97 SI detections, 175 early interventions, 3 ER visits averted.

P.04

Documentation

Auto-generated clinical documentation (UR narratives, payer compliance notes, session summaries) assembled from continuous patient data with timestamped quotes and behavioral trending. 38–53% increase in PHP authorized days. 3 denial reversals.

P.05

Quality

Every conversation scored for clinical quality. Evaluations refine therapeutic flows automatically. The AI compounds in clinical depth over the contract life.

02What only Cuepri ships

The three things no competitor has.

These aren't features layered on top. They're architectural decisions baked into the engine.

Unlock 01

Pluggable Flow Architecture.

Every conversational journey is a `FlowHandler` class against a shared contract. Your treatment programs, coaching curricula, meditations, homework, custom check-ins deploy as flows on the same runtime. Add a new flow in days, not quarters.

Unlock 02

Continuations.

The AI proactively schedules and fires structured follow-ups tied to in-session commitments. Reactive between-session AI is table stakes; proactive is the unlock.

Unlock 03

AI Computer Use Integration.

Connect to any EHR in days. AI agents navigate the EHR's UI programmatically. No custom APIs, no vendor cooperation, no integration tax.

03The integration surface

An API, an SDK, and a runtime. White-label by default.

The Cuepri Platform API is the integration surface. Versioned REST, multi-tenant by design, lean responses with on-demand expansion, async-first, webhook + SSE event delivery. No Cuepri branding in any response.

Selected endpoints GET /v1/facilities/{facilityId}/clients ?include=weeklySchedule,events,risk &filter[tags]=anxiety &page=1&pageSize=50 POST /v1/facilities/{facilityId}/ehr-notes → 202 Accepted { jobId, statusUrl } GET /v1/facilities/{facilityId}/events/stream (Server-Sent Events) POST /v1/webhooks/subscriptions { events: ["sihi.detected","checkin.completed"], endpoint: "https://partner.com/cuepri", secret: "***" } GET /v1/facilities/{facilityId}/important-events ?period=2026-04-01-2026-04-30 &filter[type]=sihi
Versioned & multi-tenant
/v1/ prefix, all data scoped by facilityId. Database-agnostic API contract.
Lean by default, expand on demand
?include= parameter for optional enrichments. No over-fetching.
Async-first
200 for fast operations, 202 with job reference for long-running ones.
Real-time events
Server-Sent Events for browser clients. Webhooks (HMAC-SHA256, retries) for server-to-server.
White-label by default
No Cuepri branding in API responses. Patients see your brand. Clinicians see your workflow.
04Three integration paths

Three paths in. None require your engineers to wait.

Pick the path that matches your stack and your timeline. We'll meet you where you are.

Days

AI Computer Use

Cuepri's Computer Use agents drive your existing EHR / EMR / clinical UI programmatically. No custom API on the partner side. No vendor cooperation. Bidirectional reads and writes through the existing UI layer.

When you don't have an API, when the API is locked, or when you don't want to wait for a vendor to build one.
Weeks

REST API + Webhooks

Standard integration via the Cuepri Platform API. Versioned, multi-tenant, white-label. Webhook subscriptions for real-time events. SDK helpers for common languages.

When your platform has its own data model and you want to embed Cuepri's capabilities behind your existing surfaces.
Custom

Embedded runtime

Deeper embed for partners that want the full flow runtime inside their stack. Pluggable Flow Architecture means your treatment programs deploy as flows on the same engine. Co-engineered with our team.

When you're building or rebuilding a clinical product and want Cuepri to be the foundation, not a bolt-on.
05Security & compliance

Compliance-ready Day 1. Not a roadmap item.

Behavioral health is regulated more heavily than general healthcare. Cuepri ships 42 CFR Part 2-aware data handling, GDPR-compliant deletion flows, and SOC 2 controls. Built in, not bolted on.

HIPAAReady Day 1
GDPRCompliant
42 CFR Part 2Aware
SOC 2Type II in progress
Mandatory MFA

TOTP (RFC 6238) primary, SMS OTP backup, 5 hashed recovery codes. Required for all staff accounts.

Multi-tenant isolation

All data scoped by facilityId. No cross-tenant leakage paths. Verified at the API layer on every request.

Granular RBAC

Roles plus permissions stored separately. Cached ~5 min, server-enforced on every request.

Device trust + session TTL

Trusted devices skip MFA for 30 days, admin-revocable. 12-hour session hard limit.

Multi-layer rate limiting

Per-IP limits on auth, registration, session, and data endpoints.

Encryption + audit

Encryption at rest (Firestore, BigQuery) and in transit (TLS 1.2+). Full audit log of dashboard access.

06Inspect what you'd embed

Inspect what you'd embed.

We'll walk through architecture, security posture, and integration model in detail. Your timeline, your evaluators.

HIPAAReady Day 1
SOC 2Type II
42 CFR · Part 2Compliant
Deploys inDays, not quarters