Huma alternatives for teams that want a dedicated participant research platform

Huma brings a broad regulatory footprint and a full service CRO in Alcedis. If you want participant research technology that your own team configures, under your own brand, without buying CRO services, WeGuide is built for that. It connects to REDCap, Salesforce and HL7 / FHIR systems you already run.

Organise a demo See the full comparison

No pressure, no hard sell. A 30 minute walkthrough with a research colleague who's built platforms like yours.

Where WeGuide differs

Research is the whole product
Technology you configure, not a services contract
Your brand, your participants' devices

Used by leading research and medical institutes.

Why research teams look for a Huma alternative

The short version

Huma has built something few digital health companies have: a disease agnostic software as a medical device platform cleared or registered in the US, EU, UK, Canada, Australia and beyond, and a clinical trials business in Alcedis, a German CRO with more than three decades of research behind it. For pharma sponsors who want regulated software and trial operations from one group, that combination is real.

See the full comparison

Why teams look elsewhere

The questions usually come from teams who wanted something narrower. Huma now describes itself as the "Operating System for AI in Regulated Industries", serving healthcare, life sciences and government. Its product range spans primary care apps, emergency triage, remote monitoring, clinical scribing and clinical trials, and its growth has come through acquisitions including iPLATO, Alcedis, eConsult and Aluna, with a partnership announced in 2025 to accelerate further M&A. Its announcements in 2026 include an AI clinical scribe and a Samsung research partnership. Research is one line among many.

The second question is about the delivery model. Huma's clinical trials offer is led by Alcedis, a full service digital first CRO covering planning, monitoring, data management, biometrics and pharmacovigilance alongside its own eCRF and patient apps. That suits sponsors who want to outsource the study. It suits less well an academic group, registry or sponsor that already has a clinical operations team, or a CRO relationship elsewhere, and wants technology it configures and runs itself.

WeGuide is built for those teams: a participant research platform with whitelabel apps, eConsent, eCOA and wearables, configured alongside you and sold as technology, not services. If Huma already fits your study, that's a good outcome, and we'll say so. If it doesn't, the shortlist below covers the platforms teams most often compare.

Key differences between WeGuide and Huma

For teams that want participant research technology rather than a CRO engagement, here's what changes when you move to WeGuide.

Research is the whole product

WeGuide is built for participant research: clinical trials, registries, cohorts and digital health programmes. Every part of the roadmap, from eConsent to wearable integrations, is shaped by research teams. Huma's platform serves health systems, governments and life sciences, with clinical trials delivered through Alcedis. Both are legitimate strategies, and they lead to different products. If your organisation runs research rather than care pathways, a platform shaped only by research teams tends to fit more naturally.

Technology you configure, not a services contract

WeGuide's no code Program Builder and Medical Form Builder let your team configure the study, with our delivery team alongside you for typically two to four weeks and a named contact afterwards. You keep your own clinical operations team, CRO or academic trials unit. Huma's research offer is built around Alcedis as a full service CRO, which is a strength if you want to outsource. If you don't, you avoid paying for operational services your team already provides, and you keep the study design decisions inside your own organisation.

Your brand, your participants' devices

WeGuide ships whitelabel native iOS and Android apps under your organisation's own App Store account and name, with native Garmin, Apple Health, Health Connect and Fitbit Air integrations so participants use the devices they already own, and sponsors can provide devices where needed. On supported Garmin models, WeGuide also collects raw accelerometer and gyroscope data at 25 Hz through the Garmin Health SDK. Huma goes further on one device: protocol level control and raw or near raw biosensor access on Samsung Galaxy Watch through its 2026 Samsung partnership.

Compare

Full comparison: WeGuide vs Huma

REDCap

Feature

Request a Demo

Company focus

Participant research and engagement platform

Healthcare AI company across care, life sciences and government that describes itself as an "Operating System for AI in Regulated Industries"

Research delivery model

Technology platform configured alongside your team

Clinical trials led by Alcedis, a full service digital first CRO with its own eClinical platforms

Full CRO services

Not a CRO. Works with your operations team or CRO

Planning, monitoring, data management, biometrics, medical writing and pharmacovigilance through Alcedis

Participant app

Whitelabel native iOS and Android apps under your own App Store account and name, or the existing WeGuide app

Huma Cloud Platform for organisations building their own digital health apps, with no code configuration, APIs and an SDK. Branding terms for research studies are not published

Study configuration

No code Program Builder, with your team configuring and ours alongside

No code configuration of the Huma Cloud Platform, and Alcedis builds custom eCRFs per protocol

eCRF and EDC depth

Medical Form Builder with conditional logic, plus two way REDCap sync

In house eCRF and EDC, built on Alcedis' web based eCRF work since 1998

eScreening and eConsent

eScreening and eConsent with version control, re-consent workflows and audit trail

Integrated screening and consent workflows, plus Alcedis mobile eConsent apps

eCOA and ePRO

A library of validated instruments

eCOA and ePRO modules

Wearables and devices

Native Garmin, Apple Health, Health Connect and Fitbit Air, raw accelerometer and gyroscope data at 25 Hz through the Garmin Health SDK on supported Garmin models, and sponsor provided devices

Device agnostic platform for third party devices (heart rate, glucose, smart inhalers), plus protocol level control and raw or near raw biosensor data on Samsung Galaxy Watch

Telehealth

Built in televisits

Telemedicine module

Medical device regulatory status

TGA registered Class I medical device software

FDA 510(k) Class II, EU MDR Class IIb, MHRA Class IIb, TGA Class IIb, Health Canada Class II, and others

Hosting regulated AI algorithms

Outside WeGuide's scope

Platform clearance covers hosting AI algorithms for screening, diagnosis and decision support

Security and compliance

ISO 27001:2022, HIPAA (BAA available), GDPR, FDA 21 CFR Part 11 compliant, managed cloud hosting

ISO 13485, ISO 27001, SOC 2 Type II, HIPAA, NHS DSPT, 21 CFR 820 (QSR) and ISO 14155

REDCap integration

Two way sync via the REDCap API

REST API in Alcedis Platforms for integrating third party solutions. No REDCap integration described on Huma or Alcedis pages

Registries and longitudinal cohorts

GenV birth cohort and FSHD Global registry run on WeGuide

Non interventional and real world evidence studies through Alcedis

Onboarding

Discovery call, configuration alongside your team (typically two to four weeks), named delivery contact

Alcedis runs studies from planning to close out as a full service partner

Pricing

Project based, quote on request, includes hosting, support and modules

Not published

REDCap

Top alternatives to Huma in 2026

Here's the shortlist of clinical research platforms teams most often evaluate alongside Huma. Some are pure technology, some bundle services, and each has a different sweet spot.

Alternative #1

Where WeGuide goes further

For teams that want the participant side of a study in one platform, here's what changes when you move to WeGuide.

A platform built only for research

Technology first, not services first

No code configuration by your team

Whitelabel apps under your brand

Native consumer wearables

Two way REDCap sync and open integrations

eConsent with re-consent workflows

Engagement built for long studies

Multilingual studies

Built for regulated research

Every WeGuide study runs on our managed infrastructure. Your IT team doesn't patch servers, manage backups, or run disaster recovery drills.

TGA Registered

Registered Class I medical device software with the Therapeutic Goods Administration.

ISO 27001

Certified information security management covering access, audit, and incident response.

Data Hosted in Australia

Participant data is hosted in Australian data centres with sovereign data controls.

GDPR Compliant

GDPR, HIPAA, and 21 CFR Part 11 ready for multi-country and US-based studies.

Biometric Security

Participant access protected by PIN code and biometric authentication on device.

256-bit AES Encryption

All data encrypted at rest and in transit with automated backups and disaster recovery.

Where Huma excels

A regulatory footprint most platforms don't have. The Huma Cloud Platform holds FDA 510(k) Class II clearance (K230214), EU MDR Class IIb certification, and lists MHRA Class IIb, TGA Class IIb, Health Canada Class II, Saudi FDA Class C and CDSCO Class C status, backed by ISO 13485 and ISO 27001. WeGuide is TGA registered Class I. If your study software needs to host regulated diagnostic or decision support algorithms, Huma is built for that.

A full service CRO in the same group. Alcedis has run clinical research for more than 30 years, built Germany's first web based eCRF in 1998, and reports 670+ studies conducted. If you want one partner to plan, run, monitor and analyse the study, that depth is a genuine advantage.

Raw wearable signals for digital endpoints. Through its June 2026 partnership with Samsung, Alcedis gives sponsors protocol level control of Galaxy Watch sensors and raw or near raw signal access. WeGuide collects raw accelerometer and gyroscope data at 25 Hz on supported Garmin models, but for biomarker work built on Galaxy Watch biosensors, Huma's access goes further.

A route from research to regulated product. Huma positions its platform as a bridge: algorithms developed in research can be launched into care as software as a medical device on the Huma Cloud Platform. For pharma teams planning a companion app or digital biomarker, that continuity has value.

Deep pharma relationships. AstraZeneca and Bayer invested in Huma's Series D, and Huma has announced programmes with Pfizer and Merck KGaA. Alcedis publishes testimonials from people at Bayer, AstraZeneca and Boehringer Ingelheim about its EDC and CRO work.

If you are a pharma sponsor who wants regulated software and full service trial delivery from one group, Huma is a defensible choice. We'd rather say that than oversell what WeGuide does.

Can WeGuide and Huma work together?

‍

Within a single study, we'd usually recommend one participant app. Across an organisation, they can coexist. A health system might run care pathways, remote monitoring or virtual wards on Huma while its research office runs registries and investigator led studies on WeGuide. WeGuide's Integration Engine connects through HL7 / FHIR, REST API and webhooks, so data can move between the two where your governance allows. The same applies to sponsors: a pharma team might use Huma and Alcedis for a late stage programme that needs full CRO delivery and regulated algorithms, and WeGuide for investigator led studies, patient registries or engagement programmes where its own team wants to stay in control of the build.

How the switch works

For teams that are ready to run studies on WeGuide instead of, or alongside, Huma, here's how onboarding typically plays out.

Discovery Call

A 30 minute conversation with one of our research delivery team. We look at your protocol, how your current study is delivered, and whether you need a CRO or just the technology. If Huma and Alcedis are the better fit, we'll tell you.

Study Configuration

Our team works alongside yours to configure the study in WeGuide: consent flows, instruments, schedules, wearable connections and branding. Your operations team or CRO stays in charge of the protocol. We make sure the platform reflects it. If REDCap or another system holds your study data, we configure the Integration Engine at this stage. Typical timeline: two to four weeks.

Participant Onboarding

Your whitelabel app goes live under your organisation's brand. Research coordinators invite participants, and eConsent, eCOA instruments and engagement content are ready from day one, with your own operations team or CRO running the study.

Ongoing Support

You get a named research delivery contact, not a ticketing queue. We stay involved for the life of the study, including amendments, re-consent and new study waves.

Case studies: research teams running their own studies on WeGuide

BRACE Trial (Murdoch Children's Research Institute)

An international randomised trial testing the BCG vaccine in healthcare workers during COVID-19, run across several countries with thousands of participants. BRACE was a hybrid trial, with vaccination and blood collection in person, and MCRI running the study with WeGuide as its participant platform.

GenV (Generation Victoria)

Generation Victoria is a whole of state longitudinal birth cohort in Victoria, Australia, following roughly 124,000 people: about 50,000 children and 74,000 parents. A research programme of that scale and length needs a branded study app that families keep on their phones for years, run by the research team itself.

FSHD Global

A longitudinal patient registry for facioscapulohumeral muscular dystrophy, combining patient reported outcomes with wearable integration. A patient organisation running its own registry, on its own terms, with WeGuide as the technology underneath.

Helping researchers transform ideas into discoveries.

Hear what our clients have to say!

"GenV trusted WeGuide to run a multi-year population health study with roughly 124,000 Victorians, about 50,000 children and 74,000 parents. Longitudinal engagement at this scale requires push notifications, multi-modal data capture, and a whitelabel app that families will keep on their phones for years.""

Susan Clifford

Senior Research Officer

“The main benefit of WeGuide is its convenience. I can’t imagine how we would follow thousands of participants and collect their data without WeGuide!”

Kaya Gardiner

Trial Project Manager

"WeGuide has transformed how we manage our patient registry. The ease of digital screening and obtaining eConsent has significantly improved our workflow."

Emma Weatherley

Managing Director

"The WeGuide trial offers staff a practical tool for recording daily COVID-19 symptoms and temperatures. For those in high-risk areas, daily reminders and alerts provide peace of mind and reassurance about their health."

Kate Cranwell

Manager

"It’s obvious that WeGuide is committed to develop technology that benefits people in the community. WeGuide has been a great partner in achieving this goal within Western Health."

Paul Eleftheriou

Chief Medical Officer

Questions

Straight answers on how WeGuide compares to Huma, what moving a study looks like, and when Huma is the right call.

Is Huma still focused on clinical research?

Huma still offers clinical trials, delivered through Alcedis, and announced a Samsung wearable partnership for research in June 2026. Its company positioning is broader: it describes itself as an "Operating System for AI in Regulated Industries", and its recent announcements include AI clinical scribing tools and the 2025 acquisition of the respiratory care company Aluna. Research is one line among several.

Is Huma a CRO?

Huma's clinical trials business is Alcedis, which describes itself as a full service digital first CRO and also builds its own eCRF, EDC and patient apps. WeGuide is not a CRO. We provide the participant platform and a delivery team, and work with your operations team or the CRO you choose.

Huma holds Class IIb status and WeGuide is Class I. Does that matter?

It depends on what your software has to do. Huma's clearances let its platform host algorithms that support screening, diagnosis and clinical decisions as a regulated device. If your study needs that, Huma is built for it. If you need consent, outcome capture, engagement and wearable data, confirm the classification you need with your regulatory team. WeGuide is TGA registered Class I medical device software and FDA 21 CFR Part 11 compliant, which covers what many research protocols ask of the participant platform. It's a question worth settling before you shortlist, because it can decide the vendor on its own.

Can WeGuide collect Samsung Galaxy Watch data like Huma?

WeGuide's native integrations are Garmin, Apple Health, Health Connect and Fitbit Air, and its raw sensor data (accelerometer and gyroscope at 25 Hz through the Garmin Health SDK) comes only from supported Garmin models. Huma's 2026 Samsung partnership gives Alcedis protocol level control of Galaxy Watch sensors and raw or near raw signal access, which WeGuide does not offer. If raw Galaxy Watch signals are central to your endpoint, Huma is worth a close look.

Can we use WeGuide with our existing CRO?

Yes. WeGuide is sold as technology, so your CRO, academic trials unit or in house team runs the study while WeGuide provides the participant app, eConsent, eCOA and wearable data. Data flows to your systems through the Integration Engine, including two way REDCap sync, Salesforce, HL7 / FHIR, REST API and webhooks. Many of the teams we work with already have an operations partner they trust, and WeGuide is designed to slot in beside them.

How do we move from Huma to WeGuide?

Most teams don't move participants mid study. They complete the current study on its existing platform and start new studies or new waves on WeGuide. Where historical data needs to come across, we scope it on the first call and bring it in through REST API or REDCap sync.

More comparisons