At the University of Michigan, the decision began with an expiration date. The university was retiring an electronic data capture system. Its SABER group, which helps design and run multicenter research, needed a replacement. There were studies to launch, participants to hear from, and regulatory requirements to satisfy. The interesting question was how much work the next system would leave for the people using it.
- EDC, eConsent, randomization, and patient-reported outcomes together.
- Commercial software with roots in Vanderbilt’s academic REDCap.
- Project-based pricing. Test the handoffs before buying.
SABER chose REDCap Cloud. In the company’s published case study, the group singled out functionality, usability for staff who were not programmers, and a portal that let participants provide feedback directly. One project was DEPTH, a phase 2 trial investigating doxycycline for emphysema in people living with HIV. Here was an ordinary software purchasing decision with unusually consequential paperwork.
That decision offers a useful way into this company. REDCap Cloud sells software for collecting, managing, connecting, and analyzing clinical research data. Its customers include drug developers, medical device companies, contract research organizations, academic investigators, and health systems. Its wager is that a study works better when its information spends less time waiting between systems.
“enabling us to adjust to new parameters”
Cathie Spino / SABER director
On REDCap Cloud, in the published customer case study
02Two REDCaps. Different responsibilities.
The name has an academic family tree. Paul Harris created the original REDCap at Vanderbilt in 2004. In February 2016, Vanderbilt announced a licensing agreement with nPhase, the company behind REDCap Cloud, to bring a commercial version to market. The academic software and the commercial business remain separate. Vanderbilt’s own guidance directs for-profit organizations needing a maintained, Part 11-compliant system toward REDCap Cloud.
The distinction matters because software always arrives with a second purchase: responsibility. With an institutional installation, somebody must arrange hosting, security, maintenance, and validation. REDCap Cloud packages managed infrastructure and support with its subscription. Its careers page recruits for a distributed workforce, fitting a business serving research teams across locations.
The commercial market is crowded. Medidata, Oracle, Veeva, Castor, and Medrio all give research buyers alternatives. REDCap Cloud’s proposition combines its academic lineage with managed delivery, patient participation tools, and connections to external data. That combination is worth evaluating against a study’s actual workflow; familiarity with the REDCap name alone cannot make the purchasing decision.
03The patient is also a data source
Electronic data capture, or EDC, provides the study’s structured forms and database. Randomization tools help assign participants to study groups. Medical coding organizes clinical terms. Electronic consent handles the consent workflow. These are practical jobs, and putting them in one environment can remove some of the repeated administration that accumulates around a trial.
Then there is myREDCap Cloud, the patient-facing portal. Participants can engage through a browser or mobile device, complete screening, consent remotely, and submit patient-reported outcomes. Electronic clinical outcome assessments extend that feedback. A hybrid study can combine visits with participation from home, while connected devices contribute measurements alongside what patients say about their experience.
A portal does not eliminate the work of recruiting or caring for participants. It changes where certain tasks can happen. For a study that needs frequent feedback between appointments, that is a meaningful design choice. For researchers, the appeal is receiving those responses within the wider study environment rather than assembling another disconnected stream of information.
04Collect once. Keep the context.
The harder problem sits beyond the form. An electronic health record, laboratory result, and wearable reading can describe the same person in different ways. REDCap Cloud offers eSource integrations and standards-based exchange with health records, including HL7. The point is to reuse information captured at its source, reducing manual entry while retaining the history needed to understand it.
Its reporting tools bring operational and clinical information into dashboards. Computing notebooks support SQL, Python, and R. In September 2025, nPhase announced REDCap Cloud 2.0, emphasizing the combination of trial data and real-world data, automated quality checks, traceable datasets, and protocol changes during ongoing studies. The AI pitch rests on that groundwork: analysis needs data whose origin and meaning can be inspected.
- 01CaptureForms · patients · devices
- 02ConnectIntegrate · standardize · check
- 03ReviewDashboards · analysis · audit
05A faster pipe still needs plumbing
A public Pfizer/nPhase presentation describes moving from daily batch delivery to roughly three-to-five-minute data readiness using Databricks. The speakers recount pipelines breaking after schema changes, difficult consolidation of access controls, and overprovisioned computing. Their advice: establish governance early, expect changing data structures, and plan for multiple clouds. They report lower costs after moving to serverless computing.
Those are useful lessons for a buyer, even without copying the architecture. Ask what happens when a protocol adds a field. Ask who can see that field. Ask how a failed transfer becomes visible. Speed measured at the database is only valuable if the people downstream can trust what arrives. That is a more demanding test than watching a dashboard refresh.
Change a field.
Follow the data.
Find the handoffs.
06The bill follows the study
REDCap Cloud prices by project. Subject count, study duration, selected modules, and professional services shape the quote; enterprise agreements cover portfolios. Hosting, updates, and support are part of its managed offering. Implementation services include study builds, migrations, custom integrations, and training. A sensible comparison therefore counts internal labor and ongoing operation alongside the subscription.
Services deserve a line of their own in that calculation. A platform can include training and still require a team to learn a different workflow. REDCap Cloud advertises an eLearning curriculum with 32 modules, alongside implementation and migration assistance. Buyers can turn that into a concrete request: show the training plan for the people who will build forms, answer queries, and review results. The quality of that transition belongs in the procurement conversation as much as the feature list.
The company’s financing also has a documented trail. Placement agent Cypress describes preferred-stock rounds in December 2015 and May 2017, with Vanderbilt among the investors. Bigfoot Capital lists a senior growth facility invested in 2021. These records show a business funded through both equity and lending, without establishing what any particular customer should expect to save.
For an eligible academic team with supported institutional REDCap and modest needs, buying another platform may add little. A regulated, multisite program with patient questionnaires and external data has a different calculation. Start with the handoffs: draw where information is collected, changed, checked, and reviewed. Then make the vendor demonstrate those transitions. SABER’s choice began when an old system’s time ran out. The broader opportunity is to stop wasting the time between systems.