Get JupyterHealth running in your environment, with the team that helped build it.
JupyterHealth is a free, open-source, secure connective layer for integrating wearable, clinical, and patient-generated data into modern computational and AI-enabled health care workflows.
The Commons Project (TCP) offers a focused suite of services to help health systems and research institutions deploy and maintain JupyterHealth, securely, at enterprise scale.
Who It’s For
Health systems and care teams integrating wearable, device, clinical, and patient-generated data into care within and beyond the clinic.
Universities, academic medical centers, researchers, and life sciences organizations working on biomarker discovery, longitudinal analysis, real-world evidence, and translational research.
Medical technology and digital health companies evaluating devices, conducting real-world pilots, and supporting monitoring across clinical and at-home settings.
Organizations delivering patient-facing programs that use continuous monitoring and patient-generated data to support care between visits.
Our Implementation Service Tiers
1. Advisory Implementation
For teams with internal engineering capacity that want expert guidance.
Architectural guidance and reference design
Implementation roadmap and project scoping
Security, privacy, and integration review
Standards and interoperability consulting
2. Full Implementation
End-to-end deployment for teams without sufficient internal capacity.
Environment setup and cloud deployment
Integration across EHRs, devices, and data sources
Security hardening: identity, secrets management, audit logging
SSO/identity, environment promotion, and email provisioning
Open-source maintenance planning and knowledge transfer
3. Customer Support
Recurring post-implementation support after go-live.
Troubleshooting and incident response
Maintenance and security patching
Platform upgrades and migrations
SLA-based response and escalation
Implementation Roles
| Project Manager | Single point of accountability for scope, schedule, and stakeholder alignment. |
| Cloud Architect | Designs deployment topology, environments, and integration points. |
| Cloud DevOps Engineer | Infrastructure as code, environment promotion, observability. |
| Application Engineer | Configures and extends JupyterHealth modules for your use cases. |
| Network/Security Engineer | Identity, secrets, network segmentation, audit logging, compliance. |
Pricing
Scoped to your engagement. Complexity ranges from a single deployment with limited integrations to enterprise multi-site deployment with advanced security and compliance requirements.
We provide a clear written proposal after an initial scoping conversation. JupyterHealth itself remains free under an open-source license; clients pay only for the time and expertise of the TCP team supporting their implementation and ongoing operation.
As a nonprofit, we use service revenue to improve JupyterHealth, sustain the open-source work behind it, and advance our broader mission.
How We Engage
Discovery call: your goals, data sources, infrastructure, and timeline
Scoping workshop: define the level of integration, from a single project through full-system deployment
Written proposal: scope, deliverables, team, timeline, and pricing
Kickoff and delivery: execution with regular check-ins
Go-live and handoff: knowledge transfer plus optional ongoing support
Why The Commons Project?
Founding JupyterHealth partner: we helped build JupyterHealth and maintain the standards and patient-data tooling underneath it.
Mission-aligned: we're a 501(c)(3); service fees fund the open-source work that benefits everyone.
Standards-first: every deployment is built on open standards so you're never locked into TCP.
Production track record: we operate infrastructure used by millions every day.