Carbon negative by design
velixir runs on 100% renewable energy at our primary regions. The residual we can't avoid (manufacturing, transmission losses, embodied hardware) we offset 2× over, every day, via verified carbon-removal credits on the public registry.
How we calculate it
Honest energy model + conservative residuals + a fat margin. Each step below is auditable; nothing is taken on faith.
Sum the platform's vCPU footprint
We snapshot every healthy app deployment, running database, and running cache, then sum their plan-allocated vCPUs across the day. HA instances count twice (primary + standby).
Convert to energy
Each vCPU-hour gets multiplied by a conservative 8 W draw and a 1.25× PUE (data-centre overhead). Both numbers err high so the resulting kWh figure is generous rather than optimistic.
vCPU-hours × 8 W × 1.25 PUE ÷ 1000 = kWh
Apply a residual emissions factor
Our primary regions run on 100% renewable energy contracts. That makes the operational kWh near-zero, but we still charge ourselves 50 gCO2e per kWh for manufacturing, transmission losses, and embodied hardware emissions amortised over the asset's life. For reference, the EU grid average is around 250 g/kWh, so we're being deliberately conservative.
Multiply by 2× and buy removal credits
Each day at 02:00 UTC, our daily job multiplies the previous 24h estimate by 2 and orders that many kg of verified removal credits: biochar, enhanced weathering, reforestation with permanence guarantees. We deliberately steer clear of pure-avoidance offsets.
Daily audit
Every day, every purchase. Failed days are shown alongside successful ones; we don't hide the rough edges.
All purchases route through a portfolio of verified carbon-removal projects. Each certificate links to the source registry (Puro.earth, Verra, Gold Standard) so you can cross-check our claim against the underlying retirement.