One prime.
The whole arc.

Segal Aerospace

Spacecraft, launch, and the ground system that flies the mission.

Segal Aerospace builds the spacecraft, the payload, and the operations system as one mission.

One family of spacecraft.

One family of spacecraft.

Spacecraft

The SF series runs from rideshare CubeSats to GEO-class platforms, on a common avionics and payload interface.

SF-12 covers 12U to 27U. SF-150 is the ESPA-class spacecraft. SF-500 carries higher-power payloads. SF-GEO is built for a long mission, with electric propulsion. Structure, power, thermal control, and software are designed with the payload.

  • Common interfaces

    Avionics and payload interfaces are shared across the family.

  • Integrated design

    Structure, power, and heat are sized together.

  • The mission

    Orbit, payload, and operating life decide which spacecraft flies.

The payload sets the spacecraft.

The payload sets the spacecraft.

Payloads

Imaging and communications payloads are designed with the power, pointing, and data of the vehicle.

ClearView is electro-optical imaging. SAR-X is radar. PA-Ka is a steered Ka-band terminal. Hyperspectral imaging, optical crosslinks, and wideband radio sensing complete the set. The observation or the link decides the payload.

  • Observation

    Optical, radar, and hyperspectral payloads for the collection the mission needs.

  • Communication

    Phased-array terminals and optical crosslinks for the link.

  • The fit

    Mechanical, thermal, power, and data interfaces are defined with the bus.

Flight software for the family.

Flight software for the family.

Avionics

Foundry Edge is the avionics architecture for guidance, fault management, and mission autonomy.

The software plans collection, schedules the downlink, and detects faults within what the spacecraft can do. Authentication, updates, and recovery sit in the command path.

  • Guidance and control

    The software follows the dynamics and the control the vehicle needs.

  • Autonomy

    Task planning stays inside the limits of the vehicle and the mission.

  • Command

    Authorization, software integrity, and recovery are part of the design.

The path to orbit.

The path to orbit.

Launch

Launch and integration are designed with the spacecraft and the mission.

Ascend-1 is medium-lift. Ascend-Heavy carries larger payloads and station elements. Ascend-Super is the super-heavy vehicle. Skybridge is air-launch. External launch remains an option, with the adapter, the test, and the campaign planned together.

  • The vehicle

    The lift class follows the mission.

  • Other launch

    Provider interfaces, adapters, and test are part of the same plan.

  • The campaign

    Mechanical, electrical, environmental, and range interfaces are one campaign.

For the life of the mission.

For the life of the mission.

Operations

Orbital Foundry is the interface for telemetry, commanding, contact planning, and mission data.

Coverage, response time, and data delivery set the ground system. Scheduling, processing, and operator responsibility are part of that system.

  • The view

    Vehicle state, contacts, and mission activity in one interface.

  • Ground access

    Coverage and scheduling follow what the mission needs.

  • Data

    Processing and delivery follow the objective of the mission.

Stations, vehicles, and surface nodes.

Stations, vehicles, and surface nodes.

Beyond orbit

Modules, stations, transfer vehicles, and surface nodes extend the same spacecraft work.

Bastion, Keystone, Halo, and Foundry Ring are pressurized modules and habitats. Vanguard, Aegis, Helios, and Pathfinder cover transfer, crew, and deep-space flight. Terra, Selene, Ares, and Drift are surface and depot nodes, where assembly, utilities, and local resources are part of the design.

  • Habitats

    Life support, shielding, assembly, and maintenance are one system.

  • Vehicles

    Transfer, crew transport, and deep-space flight are separate vehicles.

  • Nodes

    The site and its resources set the infrastructure.

Products

Spacecraft, payloads, and the ride to orbit.

Buses, instruments, launchers, and habitats, specified around the mission you need to fly.

Bus family

Four buses, by class.

  1. SF-12Rideshare
  2. SF-150ESPA-class
  3. SF-500Microsat
  4. SF-GEOGEO-class

Payloads

ClearView

Electro-optical

SAR-X

X-band radar

PA-Ka

Ka-band array

Past the bus

Vanguard

Orbital transfer

Aegis

Crew module

Helios

Deep space

Pathfinder

Autonomous probe

Class, from a rideshare stack to a GEO platform. The width is the class: rideshare, ESPA, microsat, GEO.

Spacecraft

Payloads

Flight software

Launch

Vehicles

Stations

Missions

Spacecraft systems

The SF family shares structures, power, avionics, and payload interfaces from small satellites through GEO-class missions.

Launch integration

Launch is planned with the spacecraft: orbit, loads, separation, and the campaign.

Mission architecture

Flight software, ground systems, and habitats connect the vehicle with the people and the infrastructure of the mission.

Deployed

  • Orbital Foundry

    Mission planning, spacecraft information, and operations in one workspace.

  • Spacecraft configurator

    A spacecraft configuration interface for comparing bus and payload requirements before discussing a mission with Segal Aerospace.

On the homepage

Orbital systems

Work with Aerospace

Share the mission objective, payload requirements, target orbit and intended lifetime to establish an initial technical scope.

Build the frontier
with us.

Share the objective, the requirements, and the business you want to reach. Project and partnership enquiries all come through the same form.

Discuss a Project