Flying is simulated. The servers are not.
Our flights burn no fuel, but the platform behind them still runs on real machines drawing real power. So we made the boring choices deliberately: European hosting, renewable electricity, and software light enough to run on less of both.
Three commitments we can point at.
100% renewable electricity
Every datacenter running CrewHub is supplied with renewable energy. No offset accounting standing in for the energy actually drawn.
Hosted in the European Union
Primarily France. Short network paths, a low-carbon grid, and one legal framework for every airline's data: GDPR, not a transfer clause.
Light by design
Modules you don't subscribe to are never provisioned. Nothing is trained on your data, and no background job runs for a feature you don't use.
One shared platform beats a thousand spare PCs.
Before CrewHub, an airline ran its own website, its own bot and often a home server humming in a bedroom around the clock. Consolidating hundreds of airlines onto shared, well-utilised hardware is the single biggest saving on this page — a machine at proper load does far more work per watt than fifty idling ones.
The ACARS client follows the same rule: it reports at the rate the flight needs and sleeps the rest of the time, instead of polling your connection every second of a ten-hour leg.
Storage is energy too.
We keep what an airline needs to run its operation and its history, and not much else. Logs are short-lived, telemetry is aggregated rather than hoarded, and an account that leaves takes its data out through the API and stops costing the planet a disk.
Hold us to it.
If something on this page stops being true, we would rather hear it from you than quietly leave it up. The team is on Discord.
