NABLA VS RECAPRO
The Nabla alternative for when the consultation must not leave the facility
Nabla leads the medical scribe market in France: 100,000 practitioners, 190 healthcare organisations, 55 specialties, native EHR integration (Epic, athenahealth, Weda) and European hosting (Google Cloud, Belgium region). It is an excellent product — as SaaS. Recapro installs on your own servers, up to full air-gap. The difference is not compliance: it is where the processing happens.
What SaaS deployment cannot guarantee technically
Five findings verified on nabla.com and its Trust Center (August 2026). None is a compliance gap: Nabla publishes ISO 27001, SOC 2 Type II, HIPAA, GDPR and the EU AI Act. They are consequences of the deployment model.
Audio is processed on the vendor's infrastructure
With SaaS, the consultation leaves the facility to be transcribed and summarised at the provider. The subprocessor list in Nabla Trust Center names Microsoft Azure for transcription, scoped "U.S. Regions", with no documented European variant; hosting itself is Google Cloud, Belgium region, for non-US customers. Nabla also states that it stores no audio after the consultation and never reuses data to train its models: these are real commitments, backed by certifications. They rest on contract and audit, not on network topology.
No deployment on customer servers
Nabla's website mentions neither an on-premise install nor an appliance at the customer site. For a facility whose internal policy forbids health data from leaving its own datacentre, the trade-off is therefore settled contractually, never architecturally.
No air-gapped mode
A SaaS service needs outbound connectivity to work. Isolated sites, closed networks and environments without outbound internet stay out of reach. Recapro runs fully air-gapped, AI models included.
The AI engine is not named publicly
The Trust Center names Microsoft Azure as the transcription subprocessor, but Nabla names neither a provider nor a model publicly for generating the note itself. Many vendors make the same choice and it is not a failing, but it leaves one question open in a risk assessment: where does the model run, and under which jurisdiction?
The scope is the clinical consultation
Nabla is built for the doctor-patient encounter and its integration into the patient record. Non-clinical meetings — team huddles, medical boards, steering committees, vendor reviews — fall outside its documented scope. Recapro covers them, with a healthcare mode.
Recapro vs Nabla: the honest matrix
Comparison verified on nabla.com and its Trust Center (August 2026). Nabla leads on two criteria, Recapro on five: these are not the same products.
Nabla: offices in Brooklyn (New York) and Paris (22 rue Chapon). Its Trust Center lists SOC 2 Type II, ISO 27001, HIPAA, GDPR, EU AI Act, Texas RAMP, PIPEDA and CIS Level 2, together with end-to-end encryption, no reuse of data to train models and no audio storage after the consultation. Source: nabla.com (August 2026).
On HDS: Nabla compliance & security page claims HDS-certified infrastructure, but the HDS claim is not documented on its own Trust Center, which lists the eight frameworks above without HDS. We report the gap; we draw no conclusion from it.
Hosting and subprocessors: Google Cloud, Belgium region, for non-US customers. The transcription subprocessor listed in the Trust Center is Microsoft Azure, scoped "U.S. Regions", with no documented European variant. Nabla names neither a provider nor a model publicly for generating the note. Verified 13 August 2026.
Nabla displays 190 healthcare organisations, 100,000 practitioners and 55 specialties on its French home page; other pages of the site mention over 200 organisations and over 120,000 professionals. Patient-record integrations cited: Epic, athenahealth, Weda. Nabla publishes no pricing grid: the site offers a free trial and a demo on request.
Recapro: hosting at France-Nuage (Vendée) and Scaleway (Paris), self-hosted AI inference, HDS-ready architecture, Fortress on-premise from €19.90/seat/month (10-seat minimum). Recapro holds no ISO 27001 or SOC 2 certification of its own. Source: Recapro pricing.
Nabla or Recapro? it depends on your constraint
The two products do not solve the same problem. Here is how to decide in one read.
Choose Nabla if…
- Your primary need is the consultation note, written in the vocabulary of your specialty.
- You want the note to land straight in the patient record (Epic, athenahealth, Weda), with no copy-paste.
- You are an independent physician and want to start on your own, with no infrastructure project.
- ISO 27001, SOC 2 Type II and European hosting answer your risk assessment.
- You want a product already deployed at scale: Nabla reports 190 healthcare organisations and 100,000 practitioners.
Choose Recapro if…
- Your internal policy or your regulator requires that audio never leaves your datacentre.
- You must operate on a closed network with no outbound connection: isolated site, constrained environment, continuity drill.
- You want to be able to name and audit the AI model that processes the data, and know which machine it runs on.
- You also need to cover non-clinical meetings: team huddles, medical boards, steering committees, vendor reviews.
- You need a published price to build a budget before opening a sales conversation.
Put differently: if your priority is clinical depth and patient-record integration, Nabla is the better choice. If your priority is that the data never travels, it is Recapro.
What Recapro adds that SaaS cannot
Six capabilities that follow from the deployment model, not from a compliance level.
On-premise inside your facility
Installed on your servers (Kubernetes, dedicated machine or appliance). Audio, transcript and note stay inside your network perimeter. Nabla is a SaaS service.
Fully air-gapped mode
Recapro runs with no outbound connection at all, embedded AI models included. It is the only configuration where data not leaving is a property of the architecture rather than a contract clause.
Self-hosted AI inference
Models run on our infrastructure in France (France-Nuage in Vendée, Scaleway in Paris) or directly on yours. Nabla names neither provider nor model publicly.
Every meeting, not just consultations
Team huddles, medical boards, steering committees, vendor reviews, interviews: Recapro is a general-purpose meeting notetaker with a healthcare mode. Nabla focuses on the consultation.
Published pricing grid
Cloud Team at €22.90/user/month (€17.90 annual) and Fortress on-premise from €19.90/seat/month, 10-seat minimum. Nabla publishes no price: free trial and demo on request.
Outputs to your internal tools
Documented REST API plus SharePoint, Google Drive, Salesforce, HubSpot and SAP connectors. On the patient record, however, Nabla native integration (Epic, athenahealth, Weda) stays ahead.
Trial Recapro alongside Nabla in 3 steps
No forced switch.
Scope the perimeter
Together we identify the consultations and meetings that must stay inside your network perimeter. The rest can stay exactly where it is today.
Install
Sovereign cloud in France, or Fortress on-premise on your own servers, up to fully air-gapped.
Run side by side
Recapro runs next to your current tool. You compare notes on your own meetings before deciding anything.
Onboarding support included from 10 seats.
Pricing
Three tiers. Same sovereignty.
Choose the level of isolation adapted to your criticality.
Fortress
Physical server installed on your premises (or on your existing servers). A single Sovereign Shield subscription, whatever the hardware tier.
~130 W max — about the same as a desktop PC left on. ≈ €210/year of electricity.
For 1 to 10 users
For 11 to 30 users
For 31 to 60 users
For 61 to 90 users
Custom configuration for large teams. Response within 24h.
Subject to compatible performance. Prior technical assessment.
Minimum 10 seats billed, i.e. EUR199/month: a 3-person firm pays the same Shield as a 10-person one. Above 10 seats, billing is strictly per seat.
Everything in Cloud Tailored, plus:
- Server installed on your premises (or your own servers)
- Air-gap: AI 100% disconnected from the internet
- No data ever leaves
- Hardware & commissioning included
- Fit for legal, medical, defense and finance
- Priority 24/7 support
Nabla
Competitor
Free trial and demo on request
- • SaaS medical assistant
- • Native patient-record integration (Epic, athenahealth, Weda)
- • 55 clinical specialties covered
- • ISO 27001, SOC 2 Type II, HIPAA, GDPR, EU AI Act
- • Google Cloud hosting, Belgium region (non-US customers)
- • No audio storage after the consultation
- • No reuse of data to train models
- • No on-premise deployment and no air-gapped mode
* Fair Use Policy: Usage is limited to 10 hours of audio processing per day per user, in compliance with working time legislation.
All prices are shown excluding tax (excl. VAT); VAT applies at the prevailing rate. Offers reserved for business customers.
"From" refers to the price of the first tier or the standard configuration, actually available; the final price depends on your configuration and the number of seats.
Fortress hardware is a fixed asset generally depreciable over 4 years; VAT is in principle recoverable, subject to your own accounting and tax regime (general information, not tax advice).
Your templates and your lexicon follow you from Cloud Tailored to Fortress.
Nabla leads the medical scribe market in France, and its patient-record integration is hard to match. Recapro answers a different constraint: making sure the consultation never leaves the facility, up to full air-gap, with a published grid from €19.90/seat/month on-premise. Recapro pricing details.
Recapro also covers other regulated industries
Wherever data must not leave the perimeter of the organisation.
Comparing several tools? See our global comparison or the Dicte alternative.
Nabla vs Recapro: frequently asked questions
01
Is Nabla compliant for health data?
Nabla Trust Center lists SOC 2 Type II, ISO 27001, HIPAA, GDPR, the EU AI Act, Texas RAMP, PIPEDA and CIS Level 2, together with end-to-end encryption, no reuse of data to train its models and no audio storage after the consultation. This comparison does not dispute any of it. One nuance is worth knowing: Nabla compliance & security page claims HDS-certified infrastructure, but the HDS claim is not documented on its own Trust Center. And the question asked here is different anyway: do you want those guarantees to rest on a contract and audits, or on the fact that the data never leaves your premises?
02
What is the real difference between Nabla and Recapro?
Where the processing happens. Nabla is a SaaS service: the consultation is transcribed and summarised on the vendor's infrastructure, with contractual commitments and certifications behind it. Recapro can be installed on your own servers, up to a fully air-gapped mode with no outbound connection. In that configuration, data not leaving becomes a property of the architecture.
03
Does Recapro replace a clinical scribe?
Not like for like, and that deserves to be said plainly. Nabla is a clinical scribe integrated into the patient record, with 55 specialties covered and native connections to Epic, athenahealth and Weda. Recapro is a general-purpose meeting notetaker with a healthcare mode: it produces the note, but it does not replace native patient-record integration.
04
Is Recapro certified HDS, ISO 27001 or SOC 2?
No, Recapro holds none of these certifications of its own today, and we would rather write it down. Recapro hosts in France (France-Nuage in Vendée, Scaleway in Paris), offers an on-premise deployment including air-gapped, and its architecture is HDS-ready. On ISO 27001 and SOC 2 Type II, Nabla is unambiguously ahead. On HDS, however, neither documents a certification: Nabla claims HDS-certified infrastructure on its marketing page, but the claim does not appear on its Trust Center.
05
Which AI models does Recapro use?
Recapro self-hosts its inference: the models run on our infrastructure in France, or directly on yours when deployed on-premise. Nabla names neither an AI provider nor a model publicly — a common choice in the sector, which nonetheless leaves the jurisdiction of the processing an open question.
06
Can Recapro be used for non-clinical meetings?
Yes, and that is its home ground: team huddles, medical boards, steering committees, vendor reviews, interviews. Nabla focuses on the consultation and its integration into the patient record; those meetings fall outside its documented scope.
07
How much does Nabla cost?
Nabla publishes no pricing grid: the site offers a free trial and a demo on request (verified August 2026). Recapro publishes its prices: Cloud Team at €22.90/user/month (€17.90 annual) and Fortress on-premise from €19.90/seat/month, 10-seat minimum.
The consultation never leaves your facility
Free plan, 2h/month. On-premise and air-gap demo on request.
✓ Free plan 2h/month, no credit card