Partner with
SomeEHR

Resell, white-label, or build on top of a production EHR platform. Flexible deployment, transparent licensing, and a documented API for developers.

46
Days to production
73k+
Lines of code
REST
Documented API
Deployment

Three ways to deploy. One platform.

Match the deployment model to the practice's needs — from maximum data sovereignty to zero hardware management.

🖥️ On-Premise

Full EHR runs on a Linux server inside the practice's firewall. Patient data never leaves the building. Maximum security and data sovereignty.

  • Full data sovereignty
  • Patient data behind practice firewall
  • TLS on the local network
  • No cloud database exposure
  • Lowest ongoing infrastructure cost
  • Practice provides Linux server
  • Requires basic network configuration
Recommended

☁️ Cloud-Hosted (Google Cloud)

Production-proven on Google Cloud Run, serving real patients today. No on-site hardware, no server to maintain. Any healthcare-grade Wi-Fi or a travel router gets a tenant fully operational — including mobile prescribing and chart access from a provider's phone.

  • Zero on-site hardware
  • Auto-scaling and managed infrastructure
  • Google HIPAA BAA coverage
  • Fast deployment — minutes, not days
  • Provider mobility — chart and prescribe from anywhere
  • Data transits cloud network

🔀 Hybrid

Clinical data on-premise, patient portal in the cloud. A middle-ground option for practices that want local-only chart storage but still need a cloud-reachable portal.

  • Clinical data stays on-site
  • Portal accessible from anywhere
  • Balanced cost and security
  • Two environments to manage
Per-Tenant Economics

Onboard a tenant for the cost of a tablet.

With cloud deployment, there's no per-tenant server to buy, rack, or maintain. A complete front desk and check-in station costs a few hundred dollars in hardware — set up in minutes, no IT visit required.

Two-tablet front desk and check-in kiosk with Stripe terminal
Licensing

Flexible licensing for every partner type.

Whether you're a medical suite operator, a clinic network, or a software company — there's a licensing model that fits.

Site License

For medical suite operators

Hold a site license for your facility. Sublicense to individual tenant practices at your own pricing. You manage onboarding and first-line support.

  • Single license covers the facility
  • Sublicense to tenants at your markup
  • Shared hardware infrastructure
  • You own the tenant relationship
  • Volume pricing available

White Label

For clinic networks & franchises

Your branding, our platform. Deploy across your network with your name, your colors, and your domain. We stay invisible to the end user.

  • Custom branding and domain
  • Per-tenant pricing
  • Centralized or distributed deployment
  • Training and onboarding support
  • Priority feature requests

Developer License

For integrators & builders

API access to build on top of the platform. Extend workflows, add integrations, or build companion applications for your market.

  • Full REST API documentation
  • Google Workspace data layer (bring your own BAA)
  • Integration endpoints for Stripe, Twilio, AllTraq
  • Multi-tenant architecture support
  • Developer sandbox environment
For Developers

A stack you can work with.

Modern, documented, and extensible. No proprietary black boxes.

⚙️ Backend

  • FastAPI (Python) with Pydantic models
  • Fully typed REST API with auto-generated docs
  • Google Sheets & Drive as data layer
  • Local JSON transaction store for speed
  • Headless browser integrations
  • Background task processing

🎨 Frontend

  • React + TypeScript (Vite)
  • Modular component architecture
  • Tablet and desktop responsive
  • Stripe.js and Google Places Autocomplete
  • Signature pad with caching
  • Provider-specific UI routing

🔌 Integration Points

  • Stripe Terminal + Elements + Connect
  • Twilio SMS & WhatsApp
  • Sinch fax API
  • VoIP.ms SMS API
  • AllTraq RTLS (UWB)
  • Google Calendar API

☁️ Infrastructure

  • Google Cloud Run + Cloud NAT (production)
  • Cloudflare CDN + proxy
  • Ubuntu Linux available for on-prem deployment
  • Public TLS (portal) + self-signed TLS (LAN option)
  • Google Secret Manager
  • Git-based deployment workflow
Engineering Standards

Built to be trusted. Built to scale.

This isn't a vibe-coded prototype. Every sprint is planned, peer-reviewed, smoke-tested, and promoted through a formal DEV→PROD protocol. Production means production — real patients, real payments, continuous operation.

🛡️

Not vibe coded. Not a prototype.

Every endpoint is typed, documented, and version-bumped. Every frontend component ships with hooks, styles, types, and utils in its own module. Architecture Decision Records (ADRs) govern every structural change. The system has been red-team and blue-team reviewed, HIPAA-audited, and smoke-tested before every deploy — and it runs live clinical care every day without interruption.

🔴🔵 Red & Blue Team Reviews

Security reviewed from both attacker and defender perspectives before every production promotion. Vulnerabilities are found internally, not in the field.

🧪 Smoke Tested Every Deploy

Full end-to-end test matrix — patient lookup, check-in, SOAP notes, payments, fax, SMS — verified against the Cloud Run URL before any frontend deploy ships.

📋 Formal Sprint Protocol

Sprint-based development with structured handoff documents, ADRs for every architectural decision, and a strict DEV→PROD promotion checklist. No cowboy deploys.

🔒 HIPAA Compliance Module

45 automated safeguards monitored continuously — SSL, MFA, encryption, IAM, audit logging. Traffic-light indicators in Settings, not an annual checkbox exercise.

⚡ Built for Continuous Operation

Zero-downtime deploy discipline. Live patient care cannot be interrupted — every change is tested in DEV, verified, then promoted. Rollback procedures documented.

📐 Version-Controlled Everything

Every file carries a version header. Every backend endpoint and frontend component is independently versioned. Git commit discipline enforced at every milestone.

Architecture — Designed for Rapid Growth

⚙️ Backend

Routes
Clean REST endpoints — one file per domain. No logic in routes, only delegation to services. Easy to extend, impossible to break adjacent routes.
Services
All business logic lives here. Stateless, testable, independently deployable. Adding a new integration means adding a service — nothing else changes.
Models
Pydantic-typed throughout. Every request and response validated at the boundary. No silent data failures.
Runtime
FastAPI (Python) on Google Cloud Run — async, auto-scaling, managed. New tenants add zero infrastructure overhead.

🎨 Frontend

Components / Modules
Each feature is a self-contained module under src/components/. No spaghetti imports, no shared mutable state across features.
Hooks
Data fetching, auth, and side effects isolated in custom hooks per module. Logic is reusable; UI stays clean.
Types
TypeScript strict mode. Every API response typed end-to-end. Compile-time safety before anything reaches the browser.
Styles / Utils
Module-scoped CSS and utility helpers. No global style leakage. New modules add no risk to existing UI.
Partner With Us

Let's build something together.

Whether you're looking to resell, white-label, or integrate — we'd like to hear from you. Pricing is a conversation, not a checkout page.

Let's Talk