Developer-first headless EHR — API-first healthcare infrastructure on FHIR - oystehr.com
· 1 month ago
Buy it if you have engineers building a custom healthcare product and want FHIR-native APIs with usage-based pricing. If you are a clinic that needs working EHR software out of the box, this is the wrong tool.
Confidence
Medium. Based on ~20 public sources; independent user reviews remain sparse.
Ratings
Value for money
Ease of use
Feature depth
Support qualityNo support evidence in sources reviewed
Security posture
Pricing
Pay per use
Usage-based
ModelUsage-based
Monthly feesNot disclosed
HardwareNot disclosed
Best for
→Health-tech startups building custom EHRs
→Urgent care and telehealth platforms
→Dev teams wanting FHIR-native APIs
→Teams starting from open-source Ottehr
Not for
×Clinics without in-house engineers
×Anyone wanting turnkey, out-of-the-box EHR
×Small practices needing billing and scheduling day one
×Buyers wary of proprietary serverless lock-in
Gotchas - check before you buy
medium
Usage-based billing scales with API volume; model per-call costs before committing.
medium
Proprietary Zambda/serverless patterns add learning curve and some lock-in versus vanilla FHIR servers.
low
Parent company MassLight also sells dev services; clarify ownership if they build for you.
Pros and cons
Pros
+API-first, FHIR R4/R5-native platform built for developers
+Usage-based pricing with published fees; no enterprise sales gate
+HIPAA compliant and ONC Health IT certified
+Ottehr open-source EHR gives a customizable starting point
Cons
−100% headless — you build and maintain every clinical workflow yourself
−Requires serverless and Zambda patterns; steep for non-engineers
−Young, bootstrapped company; no outside funding yet
Comments
One queue. No nested comments. Give a display name first. Limit: 200 words per comment and 7 comments per day. You can edit or delete yours.
No comments yet.