Nabla

What Is Nabla?

Clinicians spend a well-documented chunk of every working day on notes instead of patients. Studies of EHR use routinely put documentation time at one to two hours for every hour of direct patient contact, and that burden is a leading driver of physician burnout. Nabla was built to close that gap by listening to the patient-clinician conversation and drafting the note automatically.

Founded in Paris in 2018 by Alex Lebrun, Delphine Groll, and Martin Raison, Nabla Technologies SAS has grown steadily since. The company now reports more than 85,000 clinicians using its platform across 130-plus healthcare organisations, with over 20 million patient encounters processed annually. Lebrun previously built and sold conversational AI companies to Facebook, and that product pedigree shows in Nabla's focus on ambient capture rather than yet another dictation app clinicians have to remember to open.

The company sits in EuropeanStack's Healthcare AI category alongside Copenhagen-based Corti. Comparing the two is instructive: Nabla focuses on the clinician-facing scribe experience embedded in EHR software, while Corti leans more toward developer infrastructure. Nabla raised a $70 million Series C in June 2025, led by HV Capital with Highland Europe, DST Global, and Cathay Innovation participating, bringing its total funding to $120 million.

Internationally, Nabla also competes against US ambient-scribe vendors such as Abridge, which has raised far larger funding rounds and built a bigger US health-system footprint. What Nabla offers in that comparison is a European company of record, a Paris-based team, and — for non-US customers — data hosted in EU infrastructure rather than routed through a US-headquartered parent by default.

Key Features

Ambient documentation inside the EHR

Nabla's core product listens during a consultation and generates a structured clinical note without the clinician dictating separately afterward. Rather than living as a standalone app, it integrates directly into Epic, athenahealth, Oracle Health, NextGen, and Greenway Health, so the note appears where clinicians already work. A custom integration path, Nabla Connect, covers EHR platforms without a native connector. Ambient scribes can still mishear a drug name or a dosage, so Nabla positions the clinician's sign-off as a required step, not an optional check, before a note becomes part of the record.

Coding suggestions grounded in guidelines

Beyond the note itself, Nabla suggests E/M and ICD-10 codes based on AMA guidelines and the documented encounter. For practices where coding accuracy affects reimbursement, this reduces one more manual step, though the suggestions still require clinician sign-off rather than auto-submitting claims.

Audio handling designed to minimise retention

Nabla processes audio in short chunks during the encounter and discards it afterward rather than storing full recordings. Only the resulting transcript and note persist, and by default for just 14 days, a period practices can configure to match their own retention policy. For clinicians uneasy about patient conversations being recorded and archived indefinitely, this is a meaningfully different design than a "record everything, review later" approach.

Data residency, with one real caveat

Nabla's trust centre states that non-US customer data is hosted in EU Google Cloud data centres in Belgium, while US client data stays in US regions. That is a genuine EU-hosting commitment for European healthcare organisations. It comes with a caveat worth flagging: speech-to-text processing runs through Microsoft Azure in US regions for all customers, meaning a slice of the audio pipeline is not purely EU-hosted even for European clients. Practices with strict data-residency mandates should raise this directly during procurement rather than assume full EU containment.

Certification stack

Nabla holds SOC 2 Type II certification (renewed through October 2025) and ISO/IEC 27001 certification (achieved September 2025), alongside HIPAA and GDPR compliance. It also lists CCPA and PIPEDA coverage for North American customers and states EU AI Act alignment on its trust centre.

Support for interns, residents, and specialty templates

Beyond the core scribe, Nabla ships note templates tuned to different specialties rather than a single generic format for every encounter type. Interns and residents get unlimited free consultations regardless of plan, a detail that matters for teaching hospitals training rotating clinicians who would otherwise blow through the 30-consultation free-tier cap within days.

Pricing

Nabla offers a genuine free tier: up to 30 consultations a month, with full EHR integration included and unlimited use for interns and residents. That is enough to trial the product properly, though too thin for any clinician carrying a normal patient list.

Beyond the free tier, Nabla does not publish official pricing. Third-party trackers and reviewer sites consistently cite a Pro plan in the range of $119 to $239 per clinician per month, but Nabla will not confirm a figure without a sales conversation. Enterprise pricing for hospitals and telehealth networks is fully custom, including tailored models and SAML SSO. Buyers comparing Nabla against Corti's published usage-based API pricing will notice the contrast immediately — Nabla's opacity is standard for clinician-facing scribe apps, but it is not the norm across the whole healthcare AI category.

EU Compliance & Privacy

Nabla is a French company operating under GDPR by default. Its EU data-hosting commitment for non-US clients is a real, verifiable design choice, confirmed on its own trust centre rather than just a marketing claim. Note retention defaults to 14 days and is configurable per organisation, giving practices meaningful control over how long patient data persists in Nabla's systems.

Nabla Technologies Inc. is a separate US subsidiary, registered in 2023 as a joint data controller for US operations. Nabla's privacy policy includes a consent clause covering US data transfers. That's standard for a company serving both EU and US healthcare markets, but it's worth reading closely before rollout at any organisation with strict cross-border data rules. The French SAS remains the contracting entity and files capital changes under French law — the entity EU customers actually sign with.

That structure is a common one for European AI companies that also sell into the US. A French or German parent stays the entity of record for European contracts, while a US subsidiary handles local sales and acts as joint controller for American customer data. It is worth a procurement team's five minutes to confirm which entity actually signs the contract, rather than assuming the marketing site's country flag settles the question.

Who It's Best For

Hospital groups and multi-site practices on Epic, athenahealth, or Oracle Health get the deepest value, since Nabla's native EHR integration removes the manual copy-paste step that undermines most standalone scribe tools. Rollout is also faster at this scale, since IT and clinical informatics teams only need to validate the integration once before extending it across departments.

Solo clinicians and small practices can validate the product on the free tier before committing budget, though they should confirm current Pro pricing directly rather than relying on third-party estimates.

European health systems with data-residency requirements should ask specifically about the Azure speech-to-text nuance rather than assuming full EU containment based on the headline hosting claim.

Practices that need coding automation to submit claims automatically, rather than coding suggestions requiring sign-off, will find Nabla's current scope stops short of that.

Teaching hospitals training rotating clinicians benefit from the unlimited intern and resident allowance, which sidesteps the free-tier cap that would otherwise apply to every trainee.

The Verdict

Nabla solves a real, well-measured problem — clinician documentation burden — with an ambient-capture design that fits into existing EHR workflows rather than adding another app to the desktop. Its EU hosting commitment for non-US clients, current certification stack, and 14-day default retention are genuine strengths for European buyers, tempered by the Azure speech-to-text nuance and a US subsidiary worth understanding before signing. Pricing opacity beyond the free tier is a real friction point, one shared with most of the category but not with every competitor. For hospital groups on a supported EHR, it remains one of the stronger European options in ambient clinical documentation.

Frequently Asked Questions

Is Nabla GDPR compliant?

Yes. Nabla is a French company (Nabla Technologies SAS) and is GDPR compliant. Non-US customer data is hosted in EU Google Cloud data centres in Belgium, though speech-to-text processing runs through Azure in US regions for all customers, which is worth checking against your data-residency requirements.

How much does Nabla cost?

Nabla offers a free tier for up to 30 consultations a month. It does not publish paid pricing; third-party trackers report the Pro plan at roughly $119 to $239 per clinician per month, with custom enterprise pricing for health systems.

Does Nabla store patient audio recordings?

No, not by default. Nabla processes audio in short chunks during the consultation and discards them afterward. Only the resulting transcript and note are stored, for a configurable period that defaults to 14 days.

Which EHR systems does Nabla integrate with?

Nabla integrates directly with Epic, athenahealth, Oracle Health, NextGen, and Greenway Health, plus a custom API called Nabla Connect for platforms without a native integration.

Does Nabla have a US entity?

Yes. Nabla Technologies Inc. is a US subsidiary that acts as a joint data controller for US operations. The French SAS remains the contracting entity for European customers under French law.