Environmental and Sustainability Policy
What a small software company can actually do about its environmental impact, without pretending to more.
Our position
The environmental impact of a software company sits mostly in two places: the compute and storage its systems consume, and the hardware it specifies for clients. Those are the areas where our decisions make a measurable difference, so those are what this policy covers.
What we do not claim
ASTRI DEVS LTD does not claim to be carbon neutral, net zero or "100% sustainable". We have not measured our emissions, we do not purchase offsets, and we hold no environmental certification. Publishing any of those claims without the measurement behind them would be greenwashing, and a procurement team is right to discount it.
If a procurement requires a carbon reduction plan or a measured baseline, tell us at the outset. We will either produce one properly or tell you we cannot within your timescale.
Engineering choices
These are decisions we make routinely, and they reduce energy consumption as a side effect of being good engineering:
- Avoiding unnecessary compute. Static generation and caching in preference to rendering the same content on every request. This website is a static build for exactly that reason.
- Right-sizing infrastructure. Provisioning against measured load rather than against the largest plausible number, and reviewing it after go-live rather than leaving whatever was set up on day one.
- Efficient data transfer. Compressed assets, appropriate image formats and sizes, and shipping as little client-side code as the requirement allows. Less transferred data means less energy consumed across the network and on the device.
- Retention as a design decision. Data kept indefinitely because nobody decided otherwise is stored, backed up and replicated indefinitely.
Infrastructure
Where we choose a hosting provider, we prefer providers who publish their energy position and operate on renewable or low-carbon power. Where a client specifies the provider, we work with what they have specified.
We avoid architectures that keep resources running permanently to serve intermittent load, where a simpler design would do the same job.
Hardware and equipment
Where an engagement includes technology sourcing, we specify equipment against the requirement rather than against the largest configuration a budget will bear. Over-specification is waste at both ends of the equipment's life.
We favour extending the useful life of equipment already deployed over replacing it, and we specify equipment that can be repaired and that has a supported lifespan. Where equipment is replaced, we recommend responsible disposal in line with the Waste Electrical and Electronic Equipment regulations and, where practical, reuse rather than disposal.
Our own operations
We are a small, largely remote company with one registered office. Our direct operational footprint is correspondingly small: we do not operate a fleet, a data centre or a manufacturing process. We keep business travel to what an engagement genuinely needs, and prefer remote working where it does not reduce the quality of delivery.
Responding to environmental requirements
Where a procurement includes environmental or social value criteria, we respond only against commitments we can deliver and evidence. We would rather score lower on a criterion than commit to something we cannot demonstrate afterwards.