Cloud Carbon Footprint

Open-source cloud-usage, energy and carbon-estimation application.

5 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

    Application platform deployment

  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
  • Google Cloud: Customer cloud account · Customer-operated

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

    GCP App Engine ↗ · 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 methodApplication platform deployment
InfrastructureServers / containers
Cloud Carbon Footprint API deployed to Google App Engine with configured cloud-usage data sources. 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.

5 of 12 fields researched (42%) · 3 documented · 2 unresolved. Evidence coverage is not a feature score.

Single sign-on
Not confirmedEvidence and scope for Single sign-on

The reviewed API authentication middleware logs success and calls next without validating a user. Cloud-account credentials in its configuration authenticate usage-data collection, not dashboard users. A supported external IdP login, account/role mapping and protection of both UI/API remain unconfirmed; an identity-aware proxy would need a separately reviewed design.

Actual upstream middleware on moving trunk; cloud-source IAM is separate from application-user SSO · Source ↗ · Cloud data-source authentication configuration ↗ · Reviewed 2026-11-20

Sources checked — unresolved · Editor reviewed.

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

The reviewed source supplies deployment configuration for Cloud Carbon Footprint API deployed to Google App Engine with configured cloud-usage data sources. Set organization-specific secrets, networking, storage and compatible image versions before use.

Cloud Carbon Footprint deployment example; review the full linked installation instructions · Deployment artifact ↗ (trunk (moving branch)) · Reviewed 2026-11-19

Documented · Editor reviewed.

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

The current API App Engine recipe selects instance class B2 with basic scaling capped at one instance. This is a deployment example, not a complete UI/API/cache capacity or HA baseline. Query range, account/project count, billing-data processing and cache/database growth need sizing; do not treat one small API instance as a validated 100-user HA design.

Current API example allocation on moving trunk; complete workload sizing remains unconfirmed · Source ↗ · Application and frontend deployment steps ↗ · Reviewed 2026-11-20

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.

Cloud Carbon Footprint; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

The project publishes a moving latest release marker. The reviewed repository remains active, but this marker does not identify an immutable production application release or support duration.

Cloud Carbon Footprint upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (7 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.

Scope & considerations

The named hosting path is Google App Engine; reading AWS/Azure billing does not establish app deployment there. Estimates and dashboards are not audited emissions or regulatory-compliance certifications. The moving latest release tag is not an immutable application version.

Community & maintenance

The reviewed upstream contributor history includes camcash17, dtoakley, 4upz, 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 cloud-usage, energy and carbon-estimation application.
Observability
Open-source cloud-usage, energy and carbon-estimation application.

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
  • Cloudera on CloudCloudera-managed control plane that provisions data, analytics and AI workload services into a customer's public-cloud account.
    • AWS
    • Azure
    • Google Cloud
    Shared operations · vendor control plane · Commercial Only

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.

    • GCP App Engine ↗ · Google Cloud

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

      Cloud Carbon Footprint API deployed to Google App Engine with configured cloud-usage data sources. The named hosting path is Google App Engine; reading AWS/Azure billing does not establish app deployment there. Estimates and dashboards are not audited emissions or regulatory-compliance certifications. The moving latest release tag is not an immutable application version.

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

Suggest a correction · Back to directory