Processing and storage
Consider the amount of computation and stored data the workflow needs. More capacity should serve a clear requirement.
Corporate responsibility / Sustainability
Software has a physical footprint through computing, storage, devices, and the work required to build and maintain it. We consider those tradeoffs when planning our own site and discussing customer projects.
Our approach
A useful review starts with the parts of a project that consume energy or materials, rather than an unsupported impact claim.
Consider the amount of computation and stored data the workflow needs. More capacity should serve a clear requirement.
Consider what users need to download, how often an update is necessary, and whether the delivery method fits the work.
Software that can be maintained and adapted may avoid unnecessary replacement work. Device and platform requirements belong in project scoping.
Our approach
Environmental considerations sit alongside performance, reliability, accessibility, and cost. The appropriate choice depends on the use case.
Identify the users, data, expected workload, and operating environment before deciding on an architecture.
Discuss processing, storage, hosting, and offline operation where those choices affect the project.
Agree on update needs, support, and what can be changed without rebuilding the entire workflow.
If a project requires an environmental claim, define the measurement boundary and evidence before using that claim.
Our approach
These are observable design choices, not measured environmental outcomes.
The public site is built as lightweight static pages with no tracking scripts.
Site fonts, images, scripts, and styles are served from EngLogics paths rather than third-party marketing embeds.
The site does not include advertising or analytics trackers. See the cookie information for the current setup.
Our approach
We do not currently publish a verified company emissions inventory or numerical reduction target.
No verified company-wide energy, emissions, renewable-electricity, travel, or waste figures are published on this site. We would identify the period, organizational boundary, data sources, and calculation method before publishing results.
A project-specific improvement should be described with the same care. For example, a faster workflow is a performance result; an environmental benefit would need its own measurement and a stated comparison.
Our approach
Tell us which environmental requirements matter to your organization so they can be discussed with the other project requirements.
Corporate responsibility
Ask us about a specific project requirement or information on this page.