Frequently Asked Questions
General
What is Entropic Space?
We're developing drop-in satellite software for autonomous collision avoidance, cyber resilience, and space-weather-aware operations—no hardware changes.
Where does it run?
On common ARM/LEON-class flight computers under Linux or an RTOS; final support will be platform-specific.
How is it introduced safely?
Advisory mode first; supervised autonomy next; full autonomy when approved.
What inputs are required?
CDMs/ephemerides, platform constraints, and an operator policy file.
Do you replace ground SSA or perform orbit determination (OD)?
No. We'll consume CDMs/ephemerides from your SSA/OD provider; we won't do ground tracking or sensing.
Who is it for?
Operators (single satellite → constellations), primes/integrators, and government missions; insurers/regulators will consume evidence outputs.
Availability?
Pre-release; pilot integrations are planned. Timelines will vary by platform.
How fast are decisions?
We're targeting on-board plan times in seconds; exact figures will be published per target platform and scenario.
Regulatory & Compliance
What is the export classification?
Subject to U.S. export laws; baseline classification is expected EAR99, with final determination by configuration and jurisdiction.
How will you support deorbit regulations and timelines?
The planner will enforce Δv reserves via policy and end-of-life scheduling.
Government and defense environments?
We will deploy in approved government environments on request; contact us for specifics.
Customer & Operator
What platforms are initial targets?
ARM Cortex-A (v7/v8) and LEON3/4 families are initial targets; Linux/RTEMS/FreeRTOS are planned at launch.
What is the integration effort?
Drop-in APIs/adapters; advisory mode is intended to be brought up in weeks, subject to hardware access and test facilities.
No firmware rewrites.
How do you handle propulsion-less spacecraft?
Drag-steering and safe-attitude advisories will reduce Pc.
Risk reduction, not guarantees.
How are on-orbit updates delivered?
Signed A/B bundles with rollback are planned; no single-image downtime.
Is there an operator override?
Policy‑constrained autonomy with an immediate operator inhibit/abort will always be present.
Will it change our ground software?
Minimal changes—adapters will integrate with your existing ground tools and workflows.
How will we test before flight?
We will support digital-twin simulation and hardware-in-the-loop testing before enabling autonomy.
Support and SLAs?
Support tiers and SLAs will be offered; scope will match platform and mission phase.
Insurance & Risk
How is risk reduction quantified?
Reports will include Pc before/after, Δv budgets, and signed decision logs; independent verification tooling will be offered.
Auditability?
All maneuvers and security events will be hash-chained; independent verification tooling will be provided.
Explainability?
Each maneuver will include a human-readable rationale with the key inputs, constraints, and policy checks.
Who authorizes final burns?
You do—advisory by default; auto-execute will only run within your approved policy.
Technical
How will performance and footprint be handled?
We're engineering for tight CPU/RAM budgets on mid-class OBCs; exact figures will be published per target.
What conjunction data will be supported?
CDM v3 and private ephemerides will be supported; propagator selection will be configurable.
How will offline operation work?
Autonomous between ground contacts within policy bounds; planning horizons will be configurable.
What sensors and actuators will it use?
We will use what's on board (e.g., GNSS/IMU/star tracker, wheels, magnetorquers, thrusters) and degrade gracefully if one path is unavailable.
Who sets risk thresholds and fuel caps?
You do—via the policy file; autonomy will remain within those limits.
Space-weather handling?
Plans will protect power and thermal margins and use density-aware attitudes during storms.
Interoperability with flight-dynamics tools?
Yes—adapters/APIs will interoperate with existing FDS; your tool can remain the arbiter if desired.
Data & Privacy
What telemetry will be generated?
Integrity-protected decision logs will be generated; content and retention will be operator-configurable. No secrets in logs.
Who owns the data?
You will. We will only process what's needed for operations and evidence.
Will data leave the spacecraft?
Only what's required for ops, audit, and verification; retention and redaction will be configurable.
Pricing
How is pricing structured?
Per-satellite license with fleet tiers. Optional support/assurance add-ons.
What drives price?
Fleet size, autonomy mode (advisory → supervised → full), integration scope, and SLA.
Pilots?
Advisory-mode pilots will be available; scope-limited.
Government programs?
Contracted terms; compliance with applicable security standards.