Healthcare backend as a service
Healthcare Backend as a Service for FHIR-Native Products
The healthcare backend pieces are predictable: identity, RBAC over clinical relationships, frontend-friendly APIs, file handling, scheduled work, notifications, audit-friendly access logs, and a deployable artifact. Fire Arrow ships them as one stack.
Who this is for
Product and engineering leaders looking for a faster path from clinical concept to regulated product backend.
Clinical applicability
A digital therapeutics team can launch patient intake (Patient + Questionnaire), PRO tracking (QuestionnaireResponse + Observation), clinician review (Practitioner with PractitionerCompartment access), and reminders (CarePlan-to-Task with subscription notifications) without designing a proprietary clinical schema.
The deployment options
Self-host Fire Arrow Server on your own Kubernetes, Docker Compose, or VM environment. The artifacts are a Docker image and a PostgreSQL database. For teams that prefer managed FHIR storage, Fire Arrow Core sits in front of Azure Health Data Services or another FHIR R4 server and contributes the application layer (auth, rules, GraphQL).
Either way, the operating model is your choice. There is no required SaaS dependency, no managed control plane, and no per-record pricing. The same configuration runs in development, staging, and production.
What stays your responsibility
Clinical workflow design. Regulatory scope (MDR, HIPAA, GDPR data processing roles). Identity provider choice. Tenant strategy. Backups, monitoring, and incident response in your environment. Fire Arrow contributes the authorization model, API surface, and workflow primitives; the operating context is yours to define.
Related docs
Related pages
FAQ
Is there a managed cloud version?
Not as a public SaaS. Fire Arrow is delivered as deployable software that runs in your environment. Managed deployment for specific customers is a separate engagement.
How is it priced?
Per deployment, not per record or per user. See the Editions section on the homepage for current pricing tiers, or talk to us about your specific deployment shape.
Will Fire Arrow lock me into a custom data model?
No. Data is stored as standard FHIR R4 resources. If you ever migrate away, the data is portable through any FHIR-compatible export tool.
