# Atmosphere Energy OS: technology overview

Version 1.0 | Published 12 August 2026

## Purpose

Atmosphere is presented as an orchestration layer between distributed energy assets, portfolio operators, delivery partners, and wider energy-system workflows. This note describes the public architecture model. It is not a deployment design or a statement that every capability is enabled in every environment.

## Public architecture layers

1. Edge and device integration
   - Connect approved controllers, product clouds, site systems, and available device interfaces.
   - Retain authoritative ownership for identity, permissions, configuration, and safety boundaries.
2. Energy data
   - Normalise telemetry, events, asset relationships, site context, and operational state.
   - Make approved data available to portfolio and partner workflows.
3. Intelligence and decision support
   - Combine forecasts, tariffs, constraints, customer settings, and service requirements.
   - Preview an intended operation before it is approved.
4. VPP and portfolio orchestration
   - Qualify assets, organise portfolios, forecast flexibility, coordinate approved action, and verify delivery.
5. Grid, market, and partner interfaces
   - Connect the operating model with authorised external workflows and records.

## Integration boundary

An integration assessment identifies the authoritative systems, available APIs or protocols, telemetry quality, safe command set, credential model, recovery path, and evidence required for approval. Connection alone does not establish service eligibility.

## Deployment responsibility

Cloud, hybrid, and site-resident responsibilities are selected against control, connectivity, recovery, security, and data-residency requirements. The accountable parties and operational boundary must be agreed before implementation.

For a scoped technical review, contact hello@myatmosphere.co.uk.