Scan your repo. Cut your carbon.
Sign in with your Google or GitHub account to get started.
The cloud is physical infrastructure that consumes real electricity. Every architectural choice a developer makes — which compute service, which region, how often CI runs — has a direct energy cost. Most developers never see that number. We think they should.
~1%
of global electricity
Data centres consume roughly 1% of global electricity — a share that grows every year as cloud adoption accelerates. The software choices developers make today determine the hardware utilisation of tomorrow.
40%
CI energy wasted
Studies show that 40% of CI compute time is spent re-downloading dependencies that haven't changed. A single actions/cache step eliminates that — for every project, on every run, forever.
14×
idle VM waste
An always-on EC2 instance runs 720 hours per month. A student project is actually used roughly 50 of those hours. The other 670 hours burn electricity for nothing. Serverless scales to zero.
95%
renewable in us-west-2
AWS Oregon (us-west-2) runs on more than 95% renewable energy. Moving a workload from ap-southeast-1 to us-west-2 can cut its effective carbon intensity by 40% with a single config change.
50 MB
vs 1.1 GB Docker image
node:20-alpine is 50 MB. node:latest is 1.1 GB. Every CI pull, every container start moves that delta across the wire. Alpine is not a trade-off — it's strictly better.
You cannot improve what you cannot measure. Most developers have no idea how many compute hours their project wastes per month, what that costs, or what it emits. GreenDev Coach makes that number concrete and personal.
Every green practice we recommend is also a performance or cost win. Alpine images build faster. Caching reduces pipeline time. Serverless eliminates idle spend. Sustainability and quality are the same thing.
The habits a developer forms in university follow them to every startup, every enterprise, every cloud bill they'll ever write. Teaching green patterns early creates a compounding effect at industry scale.
We don't show a generic "be sustainable" message. We show your repo, your CI triggers, your Docker base image, your region — and exactly what to change, with the YAML to paste directly into your workflow.
From repo URL to actionable sustainability report in under 30 seconds. Here's exactly what happens under the hood.
Enter any public GitHub repository URL. GreenDev Coach uses the GitHub API to read your repo structure — no cloning, no credentials, no code execution.
Tell us how your project is deployed. We use this to calculate real energy and cost baselines — an EC2 instance vs Lambda has a 14× difference in idle compute.
GreenDev runs five specialised static analysis engines simultaneously. Each focuses on a different dimension of your project's environmental impact.
Your overall score (0–100) is calculated by deducting points for each detected issue. Five category subscores show exactly where to focus.
AWS Bedrock (Claude) generates four tailored versions of your report — each optimised for a different audience.
We DO access
Public file tree
GitHub Actions YAML
Dockerfile
package.json
We NEVER access
Source code execution
Private repos
Secrets or env vars
Your AWS account
We built GreenDev Coach to empower developers to write software that actively respects our planet. A sustainability analysis tool that scans public GitHub repositories and gives student developers an actionable roadmap to greener, cheaper cloud deployments.
The best time to write green code was before you shipped. The second best time is now.
Sustainability Engine
Static analysis across CI/CD, Docker, compute, assets
AI Report Generator
AWS Bedrock Claude — plain English to pitch-ready reports
Score & Subscores
Per-category grading across 5 dimensions
Framework Comparator
Green score benchmarks for Next.js, Astro, Svelte, Remix & more