A conventional host draws power all day whether anyone visits or not, and most small sites are idle almost all the time. A Drupflare site uses a processor only while it answers a request. When nobody is visiting, it holds no compute at all.
| views/site/month | shared hosting renders | drupflare renders | saving |
|---|---|---|---|
| 10,000 | 100.00% | 7.60% | 99.95% |
| 100,000 | 100.00% | 0.76% | 99.84% |
| 1,000,000 | 83.36% | 0.08% | 98.98% |
| 20,000,000 | 28.34% | 0.004% | 92.67% |
| 50,000,000 | 13.32% | 0.0015% | 85.96% |
| 100,000,000 | 6.99% | 0.0008% | 77.14% |
Under 20M views a month, we save over 90% of energy from your computers no longer being idle.
Modeled against institutional workloads, that scales.
| example | sites | traffic, as published | views/site/month | saving |
|---|---|---|---|---|
| Arizona State University | 426 | 35M monthly page views | 82,160 (derived) | 99.86% |
| Mass.gov | 1 | ~15 million page views a month | 15,000,000 | 93.83% |
| NASA (nasa.gov) | 1 | ~1M page views a day | 30,440,000 (derived) | 90.22% |
| a U.S. government news agency | 47 | 1 to 2 billion monthly page views | 21.3 to 42.6 million (derived) | 92.38% to 87.51% |
If your institution has environmental targets, this is the right platform for you.