Gen3 (Data Commons Platform)

Open-source governed research-data commons with controlled-access request and authorization services.

7 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Terraform; Helm / Kubernetes operator; Kubernetes manifests

  2. Operated by

    Your team

    Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.

Deployment boundaries by provider
  • AWS: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    AWS Terraform Guide ↗ · Source checked 2026-11-19

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodTerraform; Helm / Kubernetes operator; Kubernetes manifests
InfrastructureServers / containers
Gen3 Terraform/Helm services on EKS with PostgreSQL, object storage, authentication and authorization services. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.
Licensing modelOpen Source / Open Core
Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseApache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

4 of 12 fields researched (33%) · 3 documented · 1 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

Gen3 documents Fence-based identity configuration and supported organisational/social methods including Google, Microsoft and research federations. Provider membership, client registration and user synchronisation require deployment configuration. Authentication is distinct from Arborist/data authorisation and development mock access.

Gen3 configured commons-user identity; provider affiliation and data permissions separate · Source ↗ · Helm identity configuration ↗ · Reviewed 2026-11-21

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The reviewed source supplies deployment configuration for Gen3 Terraform/Helm services on EKS with PostgreSQL, object storage, authentication and authorization services. Set organization-specific secrets, networking, storage and compatible image versions before use.

Reviewed deployment source collection; application images and infrastructure components have separate versions · Source ↗ · Deployment artifact ↗ (master (moving branch)) · Reviewed 2026-11-19

Documented · Editor reviewed.

Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing

The prerequisites and production deployment guide require Kubernetes and workload-appropriate CPU/RAM/storage but do not establish one complete numeric minimum for the selected commons. Databases, indexes, workspaces, data volume, processing concurrency and availability must be sized together.

Gen3 complete production commons footprint remains unconfirmed · Source ↗ · Reviewed 2026-11-21

Sources checked — unresolved · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Gen3 (Data Commons Platform); software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (8 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

Research administration here means controlled data-access requests and approvals, not sponsored-award accounting. Component/chart tags are separate releases; a single workflow-chart tag is not the version of the complete commons.

Community & maintenance

The reviewed upstream contributor history includes emalinowski, AidanHilt, EliseCastle23, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Category fit

Data & analytics
Open-source governed research-data commons with controlled-access request and authorization services.
Research & grant administration
Open-source governed research-data commons with controlled-access request and authorization services.

Compare within Data & analytics

  • ActivityInfo (Self-Managed Server)Commercial self-managed data collection, relational records and program-reporting platform.
    • Azure
    Customer-operated · Commercial Only
  • Airbyte Self-ManagedSelf-managed data movement and ELT platform with customer-operated connectors and job execution.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Source Available
  • Apache Doris Self-HostedApache-licensed analytical database with upstream AWS EKS/Alibaba ACK/ACS guides and a separately packaged cloudimg Azure VM path.
    • AWS
    • Azure
    • Alibaba Cloud
    Customer-operated · Open Source / Open Core
  • Apache DruidColumn-oriented analytics database for interactive queries over streaming and historical event data.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Apache SupersetBusiness intelligence and data exploration platform for SQL analysis, visualizations and shared dashboards.
    • AWS
    Customer-operated · Open Source / Open Core
  • AVEVA PI System (BYOL)Commercial industrial data collection, historian and visualization system with an AWS architecture.
    • AWS
    Customer-operated · Commercial Only
  • Azure Trusted Research EnvironmentOpen-source reference platform for isolated research workspaces and controlled data movement.
    • Azure
    Customer-operated · Open Source / Open Core
  • Cloud Carbon FootprintOpen-source cloud-usage, energy and carbon-estimation application.
    • Google Cloud
    Customer-operated · Open Source / Open Core

Showing 8 of 43 other listings in Data & analytics. These products address related workflows; read their category-fit notes before comparing scope. See all of Data & analytics →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • AWS Terraform Guide ↗ · AWS

      Institution deployment · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      Gen3 Terraform/Helm services on EKS with PostgreSQL, object storage, authentication and authorization services. Research administration here means controlled data-access requests and approvals, not sponsored-award accounting. Component/chart tags are separate releases; a single workflow-chart tag is not the version of the complete commons.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory