Softwr

Research · head to head

Florence eBinders vs Terra

Florence eBinders logo

Florence eBinders

Research

Electronic investigator site file and eRegulatory binder for clinical research sites

From
On request
Rated
-
Terra logo

Terra

Research

Open biomedical research platform for genomic analysis, priced only by the cloud you consume

From
Free
Rated
-

The short version

  • Only Terra has a free tier, so it costs nothing to try first.
  • Each has a real cost: Florence eBinders pricing is set against how much your sponsors are expected to reimburse rather than a rate card, so two similar sites can pay materially different amounts and neither has a public benchmark to negotiate against.; Terra the absence of a licence fee hides the real cost driver: an idle notebook virtual machine left running overnight, or a workspace bucket full of intermediate workflow outputs, quietly consumes grant money with no vendor invoice to prompt a review.
  • They diverge on capability: Florence eBinders covers Electronic investigator site file, Terra covers No platform licence fee.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Florence eBinders and Terra actually diverge.

Attributes where Florence eBinders and Terra differ
AttributeFlorence eBindersTerra
Starting priceOn requestFree
Pricing modelquoteOpen source, no licence fee
Free tierNoYes
PlatformsWebWeb, Google Cloud, Microsoft Azure

Identical on both: user rating (Not yet rated), category (Research).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Florence eBinders

  • Electronic investigator site file
  • Part 11 electronic signature
  • SiteLink remote monitoring
  • eSource
  • Delegation and training logs
  • Document templates
  • Site-side ownership
  • Integrations

Only in Terra

  • No platform licence fee
  • Cloud pass-through billing
  • WDL workflow execution
  • Notebook environments
  • Controlled-access data
  • Workspace sharing
  • Compliance posture
  • Multi-cloud

What people use each for

The jobs each tool is most often brought in to do.

Florence eBinders

  • An academic medical centre research office replacing physical regulatory binders across dozens of concurrent studiesnot Terra
  • A site management organisation standardising delegation logs and training records across multiple locationsnot Terra
  • A site under audit pressure that needs to show a complete, time-stamped document history rather than a folder of signed papernot Terra
  • A research site whose sponsors keep requesting remote monitoring access and currently receive scanned documents by emailnot Terra

Terra

  • A genomics lab running whole-genome alignment and variant calling pipelines without provisioning or maintaining a local clusternot Florence eBinders
  • A consortium sharing controlled-access human data across institutions where the data cannot be copied to each sitenot Florence eBinders
  • A health system analysing patient genomic data under a HIPAA business associate agreementnot Florence eBinders
  • A federal or federally funded project needing FedRAMP Moderate authorisation for its analysis environmentnot Florence eBinders

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Florence eBinders

  • Pricing is set against how much your sponsors are expected to reimburse rather than a rate card, so two similar sites can pay materially different amounts and neither has a public benchmark to negotiate against.
  • It is site-side only: it does not do electronic data capture, study budgeting or full trial management, so a research office still runs a CTMS and an EDC alongside it and pays for the interfaces between them.
  • The benefit case depends on sponsors and monitors actually using remote access; if your sponsor mix insists on on-site source data verification, you have digitised the binder without removing the visits that made it expensive.
  • Migrating years of existing paper and scanned regulatory documents into structured, indexed binders is a substantial one-off project that sites routinely underestimate and that is scoped and charged separately.
  • Adoption is heavily United States centred, so a European or Asian site will find fewer sponsors familiar with the platform and less mature alignment with local regulatory expectations than a domestic site enjoys.

Terra

  • The absence of a licence fee hides the real cost driver: an idle notebook virtual machine left running overnight, or a workspace bucket full of intermediate workflow outputs, quietly consumes grant money with no vendor invoice to prompt a review.
  • Cost governance is entirely the customer responsibility, and grant-funded groups without a cloud engineer routinely overspend before anyone reads the Google or Azure bill in enough detail to find the cause.
  • It assumes genuine bioinformatics competence: writing or adapting WDL workflows, managing data tables and debugging failed tasks are all on you, so a wet lab without computational staff cannot use it productively.
  • Feature parity between the Google Cloud and Azure deployments is not identical, so a decision on cloud provider constrains which capabilities and datasets you can reach and is expensive to reverse later.
  • It is a research platform rather than a regulated clinical system: it is not a validated GxP environment and does not carry the qualification package a diagnostic or submission workflow would require, so clinical use needs additional infrastructure and validation you provide yourself.

Pricing, plan by plan

Florence eBinders

On request
  • Florence eBinders$undefined/year
    • Priced against study volume, site profile and expected sponsor reimbursement
    • Electronic investigator site file with Part 11 signature and audit trail
    • SiteLink sponsor and monitor remote access

Terra

Free
  • Terra platformFree
    • No charge for the platform, administration, security controls or frontline support
    • Workspaces, workflow execution and notebook environments included
    • Available on Google Cloud and Microsoft Azure
  • Cloud consumption$undefined/month
    • Google Cloud or Azure charges passed through at cost with no markup
    • Running notebook virtual machines around 0.22 USD per hour, roughly 0.027 USD per hour when paused
    • Storage billed continuously on workspace buckets and intermediate workflow outputs

Which should you pick?

Choose Florence eBinders if

  • You need electronic investigator site file.
  • You also want part 11 electronic signature.

Choose Terra if

  • You need no platform licence fee.
  • You want to start without paying.
  • You work on Web, Google Cloud, Microsoft Azure.
  • You also want cloud pass-through billing.

Questions people ask

Is Florence eBinders or Terra better?
Neither clearly leads. Florence eBinders starts at On request and Terra at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Florence eBinders or Terra?
Terra has a free tier; the other does not. Paid plans start at On request for Florence eBinders and Free for Terra.
Does Florence eBinders or Terra run on more platforms?
Florence eBinders runs on Web. Terra runs on Web, Google Cloud, Microsoft Azure.
Can I use Terra for free?
Yes. Terra has a free tier, so you can try it without paying. Florence eBinders starts at On request.
What is Florence eBinders best used for?
Florence eBinders is most often used for an academic medical centre research office replacing physical regulatory binders across dozens of concurrent studies, a site management organisation standardising delegation logs and training records across multiple locations, a site under audit pressure that needs to show a complete, time-stamped document history rather than a folder of signed paper, a research site whose sponsors keep requesting remote monitoring access and currently receive scanned documents by email. Of those, an academic medical centre research office replacing physical regulatory binders across dozens of concurrent studies and a site management organisation standardising delegation logs and training records across multiple locations are not what Terra is typically brought in for.
What can Florence eBinders do that Terra cannot?
Florence eBinders covers Electronic investigator site file, Part 11 electronic signature, SiteLink remote monitoring, eSource. Terra covers No platform licence fee, Cloud pass-through billing, WDL workflow execution, Notebook environments.

Answered from the vendors’ own pages

Florence eBinders: Is this an EDC system?

No. It manages the site regulatory binder and source documents. Trial data capture is a separate system such as Medidata, Castor or REDCap.

Terra: Is Terra really free?

The platform is. There is no licence fee. Everything you pay is Google Cloud or Azure compute, storage and egress, passed through at cost.

Florence eBinders: Who normally pays for it?

The site buys it, but sites commonly recover the cost through per-study sponsor budgets, and Florence prices with that expected reimbursement in mind.

Terra: What actually drives the bill?

Running virtual machines and stored data. Pausing notebooks drops a virtual machine from about 0.22 to about 0.027 dollars an hour, and deleting intermediate workflow outputs is the other main saving.

Florence eBinders: Does it support 21 CFR Part 11?

Yes, with electronic signatures, audit trails and access controls. Validation for your intended use is still your responsibility.

Terra: Can I use it with protected health information?

Yes. Terra signs HIPAA business associate agreements and GDPR data processing agreements, and the Azure deployment holds FedRAMP Moderate authorisation.

Florence eBinders: Can sponsors see our documents?

Only what you grant through SiteLink. Documents stay under site control rather than in a sponsor-owned repository.

Terra: Is it validated for clinical or GxP use?

No. It is a research platform. Regulated clinical or submission workflows need validation and controls you build yourself.

Share

Related pages

Other head to heads