GoMedicus
GoMedicus — from a scoping workshop to a Series A, with one engineering team
GoMedicus set out to build the software layer for outpatient care in Germany: patients routed to the right doctor, clinicians working in one place instead of six. Cloudnonic has owned the engineering since January 2025 — infrastructure, backend, frontend and CI/CD — through public launch and a Series A.Visit site ↗19
Months from kickoff workshop to Series AFrom the first workshop to the funding round100%
Of the platform's engineering owned by CloudnonicInfrastructure, backend, frontend and CI/CD47 min
Measured recovery time in a disaster-recovery drillWithin the agreed recovery target8 min
Container deploy, with automatic rollbackRolling releases, no downtime windowYear2025 – Present
LocationGermany
Tech StackNestJS · Next.js · PostgreSQL · AWS · Terraform
Project ScopePlatform engineering · Full-stack development · Cloud infrastructure · Compliance and data protection
The problem
German outpatient care runs on tens of thousands of largely independent practices. Referrals, calendars, video, billing and documentation each live in a different tool, and very little of it talks to the rest. For a patient, that means ringing round until someone has a slot. For a practice, it means hours on the phone.GoMedicus wanted to fix the routing problem first: understand what a patient needs and send them to the right doctor in the network — in a practice, by video, or through a partner such as a pharmacy or a nursing home.The platform also had to work alongside the certified practice software doctors are required to use, rather than replace it.What we built
A multi-tenant platform with three surfaces: a clinician suite for doctors and practice staff, a patient-facing booking and care app, and internal operations tooling.At its core is a routing and availability layer that finds the right appointment across the network while respecting patients' free choice of doctor. Around that sit appointment management, video consultation through a certified provider, AI-assisted clinical documentation, reporting, and a partner API that makes adding a new booking channel a matter of configuration rather than a project.Integrating with established practice software was one of the most demanding parts of the build, and we chose to ship features only once they were safe, rather than early with known risks.Owning the whole stack
Cloudnonic is responsible for all active software development on the platform: frontend, backend, cloud infrastructure and CI/CD. GoMedicus owns product direction, acceptance and business decisions. That clear split lets a focused team move quickly without anyone guessing at priorities.The platform is built on NestJS, Next.js, TypeScript and PostgreSQL, running on AWS in the EU with all infrastructure defined in Terraform and environments fully isolated from each other.Releases go out through automated pipelines with health checks and automatic rollback, so the service stays available during routine deployments. Disaster recovery is tested, not assumed.Compliance as architecture, not an audit
The platform handles sensitive health data, so data protection had to be a property of the system rather than a document about it. Patient data stays in the EU, consent is checked before any patient data is accessed, and access is controlled and audited throughout.Retention, encryption and logging follow German and EU requirements, and the AI features were assessed against the relevant regulation from the start rather than retrofitted.Where AI actually sits
In the product, AI supports clinicians with documentation and triage, always with a clinician in the loop. No AI feature on the platform makes an autonomous clinical decision.In how we build it, AI is part of the delivery process: AI-assisted development and automated first-pass code review, so senior engineers spend their time on the decisions a model cannot make.Kickoff to Series A
A scoping workshop in January 2025 set the MVP scope, and the first working version followed within weeks. New modules rolled out step by step, leading to a public launch and the first paying patients through partner channels.When GoMedicus raised its Series A, the platform went through technical due diligence on documentation the engineering team had produced as it built — architecture decisions, security and data-protection concepts, and process documentation. Cloudnonic continues as the platform's engineering team.Outcome
- Paid appointments booked through partner channels and routed to network doctors
- New booking partners onboarded through configuration rather than custom projects
- Video consultations with triage running in front of them
- AI-assisted clinical documentation, reviewed by a clinician before anything is recorded
- A technical due diligence passed on documentation produced alongside the build
- A platform the client can offer to third parties as a product