More mission from the same battery.

For fleets in low orbit, where every battery is discharged on every orbit. Apsia reads your satellite's telemetry and tells you how much energy you have, orbit by orbit, and what you can do with it.

Analyse your telemetry See it on real satellites
  • Sunlight
  • Shadow
  • Battery charge
  • Reserve
  • A task
Three orbits of an example 6U, forecast by Apsia: sunlight charges the battery, shadow drains it, and the imaging task takes it closest to the reserve.

Four questions before every pass.

How much battery is left?

How much capacity the battery has today, how much it loses per year and how many years it has left, measured on your own discharges. And whether it reaches the end of life your mission needs. If you change how you operate, how many years that gains.

A PDF report you can forward, with the file and its fingerprint on the page.

How it is measured
  • Battery capacity and resistance, measured in flight, each with its range.
  • Pass telemetry is enough: a few samples per pass, placed on the orbit, give the health trend of the whole fleet.
  • Each panel against the others, and the power electronics: supply voltages, converters and resets.
  • Every warning with its reason: charge in shadow, a voltage drop the orbit doesn't explain, a load that never ends.
Health trend measured on real satellites from public ground-station data, % per year with its range.

Will you have margin next month?

Every orbit of the next 30 days: shadow, generation, consumption and the lowest point of the battery. When a storm is forecast, the reserve rises and says why.

A table and a chart per orbit, warnings before the reserve, and every assumption written down.

How it is measured
  • Ageing comes from your own telemetry when you have it, and from documented defaults when you do not.
  • The orbit from a TLE, an OMM, an OEM or just the catalogue number.
  • Every figure with its range, never a single guess.

Can your plan run on the power you have?

Each task with its cost in battery. If one is not viable, Apsia proposes a window where it is and keeps every committed contact. You approve each change.

The plan checked, the plan proposed and the difference, in your planner's own format.

How it is measured
  • Your pass schedule as it comes (.ics), or the plan in CSV or JSON.
  • Two windows for one task, compared with the same check.
  • How much more you can add: the longest task each window still takes.
The example's first day: the battery through each task of its activity template.

Will there be energy to deorbit on time?

Battery and array projected year by year to the deadline: FCC 5 years, ESA Zero Debris, 25 years or yours. And the last date the plan can still start.

An energy dossier for your debris file and for a mission extension: the check re-run on the battery measured in flight, the date to file the extension, and the requirement each page answers.

What the example generates per orbit in safe mode, year by year, against what its drag-sail plan needs.

And everything around the energy.

A certificate anyone can check.

For a sale, a loan, a policy or an extension: the battery's health, how it has been used against its limits and what its own gauge says, with a number anyone can check on apsia.space/verify.

The power you have now.

How much the battery can give for as long as a load lasts, without the bus falling below its minimum. With its range.

If your plan isn't feasible, alternatives that are.

Moving tasks inside their windows, or moving and dropping the least valuable. Every variant checked like your own plan.

GEO, MEO and beyond, with their own physics.

Eclipse seasons, sun-tracking arrays, the plan for each season and the move to the graveyard orbit. Around the Moon or Mars, or on a cruise, from your trajectory file, with the sunlight of each distance from the Sun.

Arrays and power electronics too.

Lost strings, degradation and protection trips, read from the same telemetry, each with its range.

Resets: radiation or energy.

Whether a satellite's resets follow the South Atlantic Anomaly or its eclipses, and since when.

From your export to an answer.

  1. Drop your export.

    As it comes out of your ground software: Yamcs, OpenC3 COSMOS, Grafana, InfluxDB, SatNOGS, CSV or Excel. Add your mission database (XTCE, COSMOS, SCOS-2000) and every channel is recognised by your own descriptions and units.

  2. Check what we read.

    Columns, units and sign conventions, detected and shown before anything runs.

  3. Get the answer.

    On screen, as a PDF to forward, in your Grafana or as an alert by email.

Your telemetry stays yours.

We read energy, nothing else.

Volts, amps and temperatures. Never images, never your customers' data.

Nothing reaches your satellite.

Apsia recommends. Your operators decide and send.

Processed in the EU.

In Belgium, on infrastructure certified to ISO 27001 and SOC 2.

Encrypted, always.

In transit and at rest. Your server sends its export with one outbound call, or a connector reads your archive: never a command. A read-only link shares one analysis, and it expires.

You hold the keys.

One key per workspace, revocable at any time. Every access is logged.

If something happens, you will know.

Within 72 hours: what happened, what it touched and what we did.

For your security team
What we keep
The free analysis keeps neither your file nor your telemetry. Workspaces keep summaries, reports, the column mapping and alert rules per satellite; raw telemetry is never stored.
Who processes it
Google Cloud EMEA, for hosting and storage in Belgium. We add a sub-processor only with notice to workspace customers.
What we never do
Train models on your workspace data without written consent, share your data with anyone or move it outside the EU.
Certification
Apsia runs on certified infrastructure and keeps these controls in writing; our own ISO 27001 is not done yet. Questionnaires and data-processing agreements: write to us and choose “Security”.

Tested on real satellites.

The same analysis, run on public telemetry from ground stations around the world. Every number next to the method it beats.

See the results Analyse your telemetry