OVOKby ACTIMI
Read the docsStart free

For digital-health startups

Build the healthcare product, not the plumbing underneath it.

Prototype against an FHIR R4 foundation, web and React Native SDKs, and documented supported-device workflows. Start in the Developer sandbox with test data, then review the production plans when your product is ready.

Start free Estimate startup runway Read the docs
ovok.com/console/fhir
SandboxTest data
Requests this month/ 10,000
FHIR Explorer
PatientObservationQuestionnaire
Events
POST/fhir/R4/Observation2014f82
POST/fhir/R4/Patient201b669
POST/fhir/R4/Observation2013093
POST/fhir/R4/Patient201977a
POST/fhir/R4/Observation20111a4
POST/fhir/R4/Patient201788b
node
❯await ovok.fhir.create(patient)
201 Patient/788b
❯await ovok.fhir.create(reading)
201 Observation/11a4
❯await ovok.fhir.create(patient)
201 Patient/977a
❯await ovok.fhir.create(reading)
201 Observation/3093
❯await ovok.fhir.create(patient)
201 Patient/b669
❯await ovok.fhir.create(reading)
201 Observation/4f82
❯

01

The work before the product

A healthcare product starts with a stack of its own.

A small team can otherwise spend its first cycles assembling identity, records, access rules and integrations before testing the experience that makes its product different.

Patient and practitioner identity

Authentication and FHIR identities for the people using your product.

Clinical records

An FHIR R4 backend and APIs for app workflows built around healthcare data.

Access control

Access Policies to define which project members can reach resources and operations.

Device and health data

SDK workflows for supported devices, plus documented HealthKit and Health Connect integrations.

Product services

Questionnaires, CMS, email and video-call capabilities where your product needs them.

RPM starting point

An out-of-the-box RPM app gives teams a concrete starting point alongside the SDKs and APIs for their own patient and practitioner experience.

Alert evaluation

Optional Signals enrollment per patient for eligible vital-sign readings.

Ovok supplies infrastructure and healthcare primitives. Your team still chooses external services and builds the product experience around them.

The Console FHIR Explorer listing synthetic test records

Your sandbox opens in the Console: browse test records in the FHIR Explorer and follow every request in Events.

02

Evaluate the surface area

Start with a sandbox, SDKs and test records.

The Developer plan lets your team exercise the API and SDK surface while it builds UI and product flows. It includes 50 test monitored patients, one sandbox environment and a 10,000-request monthly hard cap.

FHIR and API

Create and read test resources, then map the records your first workflow needs.

Web and mobile

Integrate the React SDK (@ovok/core) or React Native SDK (@ovok/native) into your app work.

Permissions and forms

Explore Access Policies and documented questionnaire workflows before shaping roles and screens.

Devices

Use the Native SDK guide to evaluate Bluetooth discovery and measurement handling. The Developer plan provides test data only; live ingestion through the Ovok IoT Service requires setup with the Ovok team.

Read about Devices
React SDK and @ovok/core React Native SDK Supported-device catalogue Access Policies

See Developer plan limits before planning an evaluation around its test-data scope or request cap.

03

Published implementation guides

Build a product workflow, not just an API demo.

These guides show concrete combinations of SDKs, FHIR resources and app-owned logic. They are implementation examples, not prebuilt regulated applications.

Blood Pressure RPM

Supported Bluetooth readings are normalized and saved as FHIR Observations for an app to read back.

Read about Blood Pressure RPM

Medication Reminder

FHIR medication requests, app-scheduled local reminders and patient-reported administrations form an adherence history.

Read about Medication Reminder

Type 2 Diabetes Risk Screening

A QuestionnaireResponse and supported glucose measurements are combined in an example screening workflow.

Read about Type 2 Diabetes Risk Screening

Whole-Person Healthspan & Coaching

Selected HealthKit or Health Connect data, reflections, goals and human coaching in a wellness example.

Read about Whole-Person Healthspan & Coaching

04

A clear product boundary

Use Ovok as infrastructure. Keep the product yours.

Ovok provides

  • FHIR R4 backend and APIs
  • Authentication and Access Policies
  • SDK primitives and supported-device workflows
  • Optional Signals evaluation for enrolled patients
  • Documented healthcare services and integrations

Your team builds

  • Patient and practitioner experience
  • Brand, business model and product logic
  • Clinical and operational workflows
  • Care pathways and follow-up decisions
  • The application’s intended purpose and regulatory strategy

05

From prototype to production

Move forward when the product is ready.

Evaluate in the sandbox, validate a bounded workflow, then review the production plan and terms that match your first cohort. Growth includes two environments and 25 sub-tenants; Scale includes three environments and unlimited sub-tenants.

  1. 01

    Developer sandbox

    Build with test patients and explore the API, SDK and configuration surface.

  2. 02

    Validate a workflow

    Confirm your data model, access boundaries and device requirements against the documented capabilities.

  3. 03

    Choose production terms

    Compare Growth and Scale limits, included monitored patients and commercial terms on the pricing page.

Startup program

Eligible startups receive 50% off Growth for the first 12 months if they are under three years old and have raised less than €2 million.

Review pricing and eligibility

What could your team keep for product work?

Compare an illustrative backend build with the engineering, production subscription, and infrastructure needed to integrate Ovok. Change the assumptions to match your runway.

Illustrative planning model · 3-year view · edit every assumption. Product feature development is omitted from both paths; the comparison covers the backend and integration scope only.

Engineering and time
FTE

Capacity available for backend work or Ovok integration.

FTE
€/year
months
engineer-months
engineer-months

Applied to both scenarios so the same requirements are compared.

engineer-months

For work needed beyond Ovok's supported integration surface; applied to both sides.

Usage and ongoing costs
patients
%
€/month
€/month

Your own app, data export, and other residual infrastructure.

FTE
FTE
devices

Additional to the first device included with each monitored patient.

Illustrative: assumes 50% off the Growth base price for 12 months from production start; overages are not discounted. Confirm treatment in your offer.

Build and run it

€276,1383-year total cost

Integrate Ovok

€163,6253-year total cost

Potential cost avoided€112,51340.7% of the in-house estimate

Swipe or scroll horizontally to view the full comparison.

YearPatientsBuild and run itIntegrate OvokCumulative difference
1150€147,937€78,125€69,812
2188€64,100€42,750€91,162
3234€64,100€42,750€112,513

Year 1 cost categories

Build the backend

Backend build and setup
€134,583
Hosting
€4,500
Maintenance
€8,854

Integrate with Ovok

Integration and setup
€42,500
Residual hosting
€5,000
Residual maintenance
€10,625
Ovok subscription
€20,000
Backend ready, in-house~9.5 months
Ovok integration ready~2.0 months

Technical effort estimate only; not a guaranteed launch date.

13.0 engineering months could be redirected from backend build to product work.

Patient-volume sensitivity

113 patients today€112,513 potential difference
150 patients today€112,513 potential difference
188 patients today€108,817 potential difference
Start building with Ovok Read the docs

Illustrative estimates only, not a quote or promised savings. Public Growth/Scale prices exclude VAT, one-time setup, custom integration, hardware, and support extras. Salary and hosting inputs are editable assumptions, not market benchmarks.

Start with the sandbox

Build against the real API and SDK surface.

Use test data to shape the product workflow, then bring specific technical and commercial questions into the next evaluation step.

Start free Read the docs