1 of 8

Antaris Docs

User Guide

This guide supports those directly working within the Antaris Cloud Platform (ACP) to develop and operate satellites. Please use this document to learn about core platform concepts and workflows.

If you have any questions or comments, please contact the Antaris support team via email at [email protected].

1. Glossary

Term

Meaning

ACP

Acronym for “Antaris Cloud Platform”

Design Studio

Section of ACP used to configure missions, satellites, and other resources

Tenant

Isolated space within ACP, typically scoped to a real world organization

User

Auth context used to represent a real person within ACP, scoped to a Tenant

Mission

Specific set of objectives for a satellite, including system scope and operational goals

Ground Station

Earth-based communications node that facilitates satellite operation

Satellite

Space vehicle that can be designed, tested, and operated within ACP

Bus

Set of satellite system components that support foundational operations, such as guidance, navigation, and power management

Bus Design

Template object in ACP representing a complete Bus and its individual components

Payload

Mission-specific device installed in a satellite along with its control software

SatOS™

Onboard software responsible for orchestrating satellite activities (i.e. the “operating system” of the satellite)

Task

Meaningful unit of work that a satellite may execute

Task Plan

Reusable template of satellite tasks, along with requirements such as geography and repetition

Scenario

Virtual sandbox constructed to test a satellite in a fully simulated space environment

HWIL

Acronym for "Hardware in the loop"

GSP

Acronym for "Ground Station Provider"

HUD

Acronym for "Heads-Up Display"

2. Satellite Design

This section describes the core satellite design process, which focuses primarily on satellite system architecture. Operational configuration and planning are addressed elsewhere.

2.1 Create a Satellite

From the DESIGN dashboard, simply click on the Create Satellite action. Give the Satellite a unique name and proceed on to the next step:

Unique Satellites may be created for many reasons, and users should feel free to use them to explore alternate design decisions. Each operational space vehicle in a constellation is represented by a unique Satellite object.

Proceed by entering a title for your satellite. Then, specify the satellite's orbital altitude and inclination

2.2 Configure Payloads

A satellite is defined primarily by the set of payloads intended to operate within it. This is critical input, as it defines the “load” to be supported by core satellite systems.

Iterate through the “Add Payload” process once for each desired payload. Components that support core system functions such as RF communication or power management are included in the satellite bus, which will come later in this process.

Selection of a payload category and subcategory allows ACP to provide more contextual filters that help identify the most appropriate Payload Device from the catalog.

The “Average Active Duration per Orbit” field helps calculate the power demand during a representative orbit. Similarly, "Required Pointing Accuracy" states the precision, allowing the payload to accurately target and capture specific areas.

If an appropriate Payload Device does not yet exist in the catalog, it may be defined using the “Add Payload Device” action:

By the end of this process, a summary of the load to be supported by the satellite will be presented in the form of “Size”, “Mass” and “Power” meters:

These requirements feed directly into the upcoming Bus Design selection process.

2.3 Configure Edge Devices

Payloads may access a nominal amount of onboard CPU, memory, and persistent storage. Satellites may optionally include Edge Devices to provide additional compute capacity to resident payloads. Edge Devices commonly contain GPUs or other hardware accelerators for specialized data processing.

To configure an Edge Device, choose from the supported components, indicate an average amount of time per orbit it will be active, and choose a quantity of SSDs to attach to it:

2.4 Choose Bus Design

When arriving at this stage, you can select different bus vendors, and ACP will have gathered enough input about the satellite to recommend an appropriate Bus Design based on the selected vendors:

As soon as you click on a Bus Design at this stage of the workflow, the load meters at the top will indicate how utilized the chosen Bus will be in each dimension. This feedback can be used to help understand how “full” the bus will be.

2.5 Configure 3D Model

To upload your own 3D model of the satellite, click on the 3D Model option. This will allow you to select and upload your model, replacing the current satellite 3D model with your custom version.

After making your selection, click “Save Satellite” and the Satellite is now ready to be used!

3. Satellite Designer

Enabling users to define and build a satellite’s profile by configuring the onboard objects. This includes specifying parameters like mass, moment of inertia (MoI), and orientation, as well as adding sensors or payloads.

To begin, click on the Satellite on the Satellite Designer. On the left panel, users will find options to add and configure sensors—currently supporting sun sensors, star trackers, and payloads. At the center of the interface, the satellite’s 3D model is visualized, allowing users to interact and understand the physical layout. The right panel displays the satellite's mass, orientation, and MoI details. At any point, clicking the satellite logo in the center will return you to the homepage.

3.1 Control Mode Configuration

Control modes define how the satellite should orient itself during different phases. These are critical for running meaningful analysis. Users can either select a predefined control mode or create a custom one.

To add a control mode, click the plus icon and enter a name for it. If your mode requires only a specific orientation, simply provide the RPY values. For more advanced control, define a vector-based control, specify the reference vector and the target entity. Once configured, your new control mode can be used in any future analysis.

3.2 Payload and Sensor Configuration

After selecting a payload, its corresponding mass and size will be displayed. Next, configure the orientation vector by defining how the payload should be aligned on the satellite bus. Set the horizontal and vertical FOV along with exclusion angles where angular limits beyond which sensor orientation should be avoided. These are set in relation to the defined entities (e.g., Earth, Sun)

The sensor analysis follows a similar workflow to payloads. Choose a sensor from the bus list, configure its properties and vector.

3.3 Analysis

This allows users to evaluate visibility and effectiveness under different scenarios. Once payload and sensor configuration is complete, move to the analysis phase. Select the duration for the analysis starting from the current UTC time, this would use the specified satellite’s orbital details as defined in the Satellite Designer. Then, add the relevant control modes that the satellite will perform during this period. You can add multiple control modes to compare results across different mission conditions. When ready, click Analyse.

3.4 Reports

After an analysis is complete, users can view detailed results in the Reports section. Each report includes both input configurations and output results. Specific to the payload or sensor used, as well as the selected control mode and entity. Users can filter or modify reports by switching between entities and control modes, enabling a flexible comparison of results.

4. Payload Development

Prior to physical satellite integration, application software must be developed to connect the SatOS™ control services to each payload. This development process utilizes ACP along with the SatOS Payload SDK. It is important that application developers review the SatOS Payload Developer Guide, as it describes the technical architecture and interfaces used to conduct this development activity.

The following diagram represents the high-level relationship between ACP and the elements operating outside of ACP:

The remainder of this section focuses on the ACP portion of the payload development process described above. It is vital that developers review the SatOS Payload Developer Guide before continuing.

4.1 Define Payload Sequence

Each Payload object contains a discrete set of Payload Sequences. Sequences represent individual requests that may be handled by Payload Application software. Individual sequences typically maps to a logical mode of operation.

Payload Sequences may also receive parameters. The “Default Sequence Parameter” field is used to set the default value sent to Payload Applications when executing a sequence. These parameters may be overridden later, as needed.

The “Data Generated” represents an estimated data that will be generated while handling the sequence. This helps in initial data modeling of the full satellite system and will be improved once representative values can be measured.

To manage Payload Sequences, first start at the DESIGN dashboard. Click on a Satellite, then choose one of its Payloads. Under the "Sequences" section, you can add a new sequence or use the available actions on each existing sequence to edit/destroy them.

4.2 Test Payload Sequence

To test a Payload Sequence, go to the "SIMULATE" and start by clicking 'Create New Scenario' Call to Action (CTA) selecting a Scenario with a HWIL instance for the target satellite. Be sure to configure all required payload interfaces correctly.

When prompted, click the "Download Remote Config" button to retrieve the required config bundle. Use this file locally with the SatOS Payload SDK to run your payload application software. The SDK will automate connecting the payload application to the ACP:

Once your payload application is successfully connected, the screen will advance to the HUD. Open the Console, and under TT&C, select the Command Type as Payload. Choose the target payload and then select a payload sequence to test. Default parameters will be set, but they may be overridden. The “Duration” represents a maximum amount of time granted to the payload application to handle the sequence before timing out. After deciding on this input, click “Execute now”:

The sequence will be encoded using an appropriate telecommand and sent for processing. then the telecommand will be acknowledged and logged in the output pane. The sequence will be forwarded by the ACP to the connected payload application for processing.

Any data that is staged for downlink by the payload application is automatically downloaded into ACP for review:

Note that the remote payload application may be restarted while its running, which can help to quickly develop application software.

5. GeoFeatures

Users can draw a fence or link a target over a specific region. These are used when creating satellite task plans, which is discussed later in this document.

5.1 Creating a GeoFeature

To define an area, users can use the Polygon tool to outline the desired region, or create a Target Track linked to that region. Alternatively, users can use the Upload option to import shapefiles in .zip format. Supported file formats include TopoJSON, GeoJSON, and KML.

Users can schedule payloads to the GeoFeatures, which will help in generating the satellite’s schedule.

6. Ground Communications

Within ACP, an operator may configure both the network of ground stations used for a mission as well as the radios employed onboard their satellites. ACP will automatically schedule ground contacts for Satellites operating on the platform, including both onboard scheduling as well as API-based scheduling via ground station provider APIs.

Users can identify which ground stations can support their mission through the "Ground Stations" section of the DESIGN dashboard.

6.1 Adding a GSP

ACP supports two main ground station providers: Atlas and Leafspace. To add them to your mission, go to the Map View, select the ground stations available under these providers, and click Add to include them in your GSP list.

6.2 Creating a Custom GSP with Ground Stations

Using the Map View and Direct Input feature users can create a Create a Custom GSP with Ground Stations

6.2.1 Creating Custom GSP via Map View

Creating GSPs through the Map View is a fast and efficient process, allowing users to quickly set up a provider and add ground stations with just a few essential details.

Go to Map View and add a ground station by providing all the required inputs. Under the Provider field, select Other, name your custom provider, and add the ground station. A new provider will be created automatically along with the ground station. Once you have configured the custom GSP with all the required ground stations for your mission, simply click Save to complete the setup.

Once you have configured the custom GSP with all the required ground stations for your mission, simply click Save to complete the setup.

6.2.2 Creating Custom GSP via Direct Input

Using the Direct Input, allows users to define the GSP in a more granular way. This level of detail is helpful later when operating the satellite.

Under the Ground Stations, click on "Add GS Provider" and choose Custom as the provider. You can then configure important details such as the API, MQTT topics, login credentials, and test configuration. Setting this up will help predict the upcoming ground passes for the ground stations added under the provider.

Once the GSP is added, you can assign individual ground stations to it.

6.3 Configuring Ground Stations within a GSP

Inside a specific GSP, users can add ground stations either by selecting them from the Map View or via direct input. Users can configure individual ground stations under their chosen GSP through either method.

6.4 MQTT Topic Configuration

Defines the ground links over which the satellite will downlink telemetry data and uplink telecommands. Setting up MQTT topics is essential for operating the satellite, Start by Specifying the the satellite ID (ideally provided by the GSP) then configure the ground links. These are defined within the scope of a Satellite object

7. Task Planning

Operational scheduling of a satellite begins with a Task Plan, which contains a prioritized set of Tasks. Each Task describes some desired activity with optional repetition and geographic requirements. Task Plans are considered generally reusable and tend to represent the “concept of operations” (ConOps) of a given satellite.

A Task Schedule is generated from a Task Plan for a desired period of time, which spans anywhere from a single orbit up to a few days. The operational state of the satellite (e.g. power level, physical location, previous activity, etc) is also considered during the scheduling process. The schedule will contain an optimized set of Tasks that will be executed onboard at specific times.

Once generated, a Task Schedule can be deployed to a target satellite during a ground station contact. Task Schedules can also be used within a Scenario to simulate mission operations, which is discussed later in this document.

7.1 Managing Tasks

Tasks must be defined before a Task Plan can be constructed. Navigate to DESIGN, choose a Satellite, click on Operations and then click on "Tasks":

Each Task represents a logical unit of work that can be scheduled. Each Task is defined by a single Payload Sequence, parametric overrides, and any relevant timing requirements.

The minimum duration field defines the minimal amount of time required for the scheduler to consider the Task for execution. The maximum duration will prevent scheduling of the Task longer than the indicated amount of time.

7.2 Managing Task Plans

Task Plans are templates of prioritized Tasks that can be used to repeatedly generate schedules for a Satellite:

It is common to define multiple Task Plans for each Satellite, typically modeling the nominal operations as well as one or more alternate plans.

When creating Task Plan, you are constructing a prioritized set of Tasks and their respective scheduling requirements.

Tasks are created ahead of time, then added to a Task Plan with additional scheduling requirements.

Several controls are available to influence when a Payload Task may be executed. The following screenshot demonstrates a "Geofence" geo-trigger.

The "Geo-Trigger" options are described below in detail:

Use None when the task has no ground-based requirements.
Use the Target Track option to require the satellite point towards a specific location on the ground during Task execution. Locations are defined using WGS84 latitude and longitude (decimal degrees) along with an altitude (km). The minimum elevation will limit which ground passes are considered, ensuring that Tasks are only scheduled when the satellite maintains the required elevation above the horizon as measured from the target location.
The Geofence option limits Task execution to time periods when the satellite passes through some geographic area. A bounding box is used to define the area, represented by two WGS84 coordinates (the upper left and lower right points of the box).

The "Sun Exposure" defines lighting conditions under which the task should be executed:

The task with Sunlit will only be executed when the satellite is in sunlight (i.e., not in Earth's shadow). This is useful for operations that rely on solar power or require illumination for imaging
The task with Eclipse will only be executed when the satellite is in Earth's shadow (i.e., during orbital eclipse). This can be useful for observing celestial phenomena or reducing light interference.
The task with Both can be executed regardless of whether the satellite is sunlit or in eclipse.

The "Orbit Direction" defines which part of the satellite’s orbit the task should occur in:

The Ascending task will only be executed when the satellite is moving from the Southern Hemisphere to the Northern Hemisphere (i.e., increasing latitude).
The Descending task will only be executed when the satellite is moving from the Northern Hemisphere to the Southern Hemisphere (i.e., decreasing latitude).
The task with Both can be executed during either orbit direction.

In certain cases, an “Attitude Control Mode” must be selected:

The Ground Track mode causes the satellite to maintain a stable orientation with respect to the earth. This can be useful for payloads that scan the ground such as IoT receivers or push-broom imaging sensors.
The Sun Track mode allows the satellite to maintain a solar-oriented attitude during the Task. This can be useful for Tasks that are not sensitive to earth-relative orientation.

The "Satellite Orientation" defines how the satellite should be oriented during task execution:

The Nadir makes the satellite points directly down toward the Earth’s surface (toward the center of the Earth). This is ideal for most Earth observation tasks like imaging, mapping, or remote sensing
The Custom makes the satellite is oriented based on user-defined parameters, such as specific roll, pitch, and yaw angles. This is useful for specialized tasks like pointing at off-nadir targets

Use the “Frequency” controls to define the preferred number of times the Task should be scheduled within a given period of time.

8. Executing Scenarios

"SIMULATE" allows satellite developers and operators to explore a variety of real world scenarios and test how a given satellite will act.

8.1 Creating a Scenario

If you are creating the scenario for first time, Under "SIMULATE", use 'Create New Scenario' Call to Action (CTA) and select the Deployment mode as Scenario Simulation. For subsequent scenario creations, click the 'New' button in top right corner to create new scenario.

The first “Scenario Details” step prompts the user for a Scenario Title. This is a human-readable name that can be referenced later. Typically, this describes the purpose or scope of the Scenario.

8.1.1 Operation - ConOps

Choose ConOps or LEOP based on the type of operation you want to simulate Under Start Time, specify the scenario start time. This start time will later be aligned with the satellite's actual launch parameters, meaning the scenario reflects the satellite’s current state based on those inputs.

The Time Scaling Factor allows the simulation to run till 2X speed, enabling users to observe satellite operations, including onboard schedule execution, in accelerated time. This is helpful for quickly reviewing and validating tasks.

Next, add the Satellite Group that users want to include in the simulation. Once added, click on Orbital Details to configure the Initial Epoch and define the satellite’s orbital position using a timestamp and Keplerian elements. This input allows users to accurately place the satellite in orbit, ensuring that tasks can be executed and observed as intended.

Next, a user may configure the set of available Ground Stations for the Scenario. The Ground Stations listed in the interface are those that have been pre-configured for the mission. While the scheduler will automatically choose the best ground contact, it is useful to enable or disable access to certain ground stations to facilitate specific operational testing.

Users can import their own task schedule into the scenario. First, download a generated schedule—this process will be explained later in the document. Users can then modify the schedule to match specific mission requirements. Once the changes are complete, click on the Import button to upload the modified schedule to the scenario.

The final stage enables users to construct a relevant “Task Schedule” (This can be Optional) to execute within the Scenario. Choose a pre-existing Task Plan and a desired amount of simulated time:

ACP will generate a schedule, then snap the scenario (i.e. advance the simulation epoch). Drag or resize the time slider on the bottom of the screen to align it to a desired time period. In the example below, the slider has been shifted to match the two later tasks in the schedule rather than running for a large period of time between tasks:

Go to the Settings located at the bottom right of the screen to access various map options. From here, you can view eclipse zones, zoom in or out, resize the map, switch to a 3D Earth view, or change the map style to suit your preferences.

8.1.2 On-Board Schedule

This button opens a window displaying the onboard satellite schedule. It presents a sequential list of scheduled events, including telemetry and payload downlinks, payload operations, and planned uplinks.

The schedule status indicates whether each task will be executed as planned. It also highlights if a task is being preempted by a higher-priority activity, occurs outside the simulation window, or if the task’s execution conditions (as defined in the task plan) are not met due to orbital constraints.

8.2 Operation - LEOP

LEOP focuses on simulating the satellite’s initial deployment during the critical early moments following launch.Start by specifying the exact simulation start time, then proceed by adding the satellites involved in the LEOP scenario.

LEOP supports the Satellite's detumbling simulation. Following this, configure the Initial Epoch and Keplerian Elements accurately, ensuring the simulation reflects real post-launch conditions.

Define the satellite’s initial attitude conditions with Orentation and Angular rates then proceed with a desired amount of simulated time

8.2.1 Prediction Analysis

8.2.1.1 ConOps

After generating the schedule from ConOps ACP performs Prediction Analysis for a quick simulation preview to help users validate and refine their schedule efficiently

Explore satellite metrics generated after the Prediction Analysis by clicking on the Power, ADCS and Data Flow panels. This saves time and helps ensure your schedule is optimized accordingly before running full real-time simulations.

For example, if users observe that AOI scheduling or revisit times can be optimized, they can adjust the scenario metrics such as orbital parameters or simulation timeframe accordingly. These changes can be made quickly, allowing users to return to the Prediction window and reassess their impact within the simulation.

8.2.1.2 LEOP

After completing the Post-LEOP configuration, ACP performs a Prediction Analysis similar to the ConOps. You can explore the satellite metrics generated during this analysis by reviewing the Power and ADCS panels.

Once you are confident with the results of the prediction analysis, proceed to deploy the scenario.

8.3 Scenario Execution

Prior to deployment, review the Tasks in more detail using the "Schedule" action on the right side of the Task timeline: Once all inputs are set, proceed to deploy which begins execution of the Scenario

8.3.1 HUD

The Heads-Up Display offers a clear and concise view of your satellite, highlighting current tasks and upcoming events. Designed to support efficient real-time monitoring and informed decision-making.

Users can open multiple secondary windows using on-screen buttons. Each window can be dragged or pinned anywhere on the screen for ease of use.

Top Left: Includes a Home button to return to the previous screen. Users can switch between satellite groups and individual satellites within the group using dropdown menu. The Orbital Details section provides specific orbital parameters of the selected satellite.
Top Right: Contains 4 Quick Actions Panels: Onboard Schedule, Console, Telemetry, File Queue. Allowing full access to satellite operations directly from the HUD, ensuring operators can manage tasks efficiently in real time.

8.3.1.2 On-Board Schedule

Displays the detailed sequence of satellite events, including operations related to the Payload Server, Application, and Payload activity, followed by any changes in the ADCS control mode.

8.3.1.3 Console

The Command Console provides a real-time table of the most recent tele-commands and telemetry messages sent and received. Each entry includes whether the message is a TC or TM message, and uses color coding to indicate the message status.

Clicking on a message reveals more detailed information, including the undecoded hex data and the decoded JSON packet. These details help users analyze message behavior and system responses.

Message Colors:

Yellow : A successful tele-command that triggered a telemetry response from the satellite
Green : A telemetry response received in reply to a tele-command
Blue : Beacon telemetry not triggered by any tele-command
None : A tele-command that did not induce a detectable telemetry response by ACP

8.3.1.3.1 Commanding through the Console

The left side of the window features the Command Console, an interface that allows the user to send manual commands to the satellite. The operator can select the TT&C option to issue individual commands from the command database. Commands can be filtered by subsystem or by using the editable text field to search by command ID or command number.

Once a command is selected and configured, clicking "Execute" will send the command immediately. The corresponding telemetry related to the executed command will then be displayed to the user.

8.3.2 Plan

In addition to the HUD, the Plan and Monitor tabs, offers expanded details found in the Onboard Schedule, Ground Contacts, and Telemetry Displays.

The Plan tab contains two subtabs: Onboard Schedule and Ground Contacts.

The Onboard Schedule presents a more comprehensive list of schedule events, along with detailed information for each. Users can use the buttons in the top-right corner to manually import or generate satellite schedules.

The Ground Contacts lists all available ground stations in a table format, showing both upcoming and past ground contacts. Selecting a contact reveals additional details on the right side of the screen, including contact type, duration, start time, and a map image showing the ground station’s location.

8.3.3 Monitor

The Monitor tab offers an expanded graphical view of the satellite’s historical telemetry data, similar to what is available via the Telemetry Quick Action button, but in a larger and more detailed format.

These graphs include the same subsystem filters and analytical tools, allowing operators to efficiently analyze trends and performance metrics over time. At the top of the tab, users can switch between grid or list view based on their preference for organizing and viewing the telemetry data.

9. Mission Models

The Mission Models helps users design Satellite missions tailored to their specific needs, providing a flexible environment to design. Users can configure satellites, geofeatures, and ground stations to build their scenarios. This supports various analysis types, such as coverage, ground contact, and propulsion budget. With a visual interface and interactive tools, help users optimize and generate meaningful reports

9.1 Active Model

Users can create and manage mission elements like satellites, geofeatures, and ground stations. It provides intuitive tools to add, edit, and organize using a structured panel view. Each object type comes with flexible configuration options, allowing users to define orbital parameters, areas of interest, or ground station details. The Active Model serves for running analysis and generating reports

9.1.1 Satellites

To create new satellites, start by clicking the "+" icon under the Satellites section. You will be presented with three options: you can create a Single Satellite, set up a Group of Satellites, or import Satellites from TLE files. Each option allows for flexible configuration depending on your mission needs.

9.1.1.1 Creating Satellite

To begin, enter a name for your satellite. Next, choose the orbit type based on your mission requirements. You can select Custom to manually configure all orbital parameters, SSO which typically has an inclination of around 98°, or Polar Orbit with a fixed inclination of 90°. After selecting the orbit type, set the remaining orbital parameters as needed and click Create to add the satellite to your mission.

After a satellite is created, it will appear in the "SATELLITES" list. Click on the ellipses next to the satellite to explore more options. Use Edit to modify the satellite’s name and update its orbit configuration. Users can also duplicate, or delete the satellite using the corresponding buttons. The Config option allows users to update parameters such as the current swath, thruster configuration, and orbit color to suit their mission requirements.

9.1.1.2 Creating Group

Start by setting a reference orbit using the same steps as you would for creating a single satellite. Under Group Configuration, choose Single Plane, all satellites will share the same orbital plane. By default, satellites are spaced evenly within the plane. If you want to manually control the spacing, uncheck the "space evenly" option and enter your desired values.

Alternatively, choose Multi Plane to distribute satellites across multiple orbital planes. In this case, configure the total number of planes and the number of satellites in each plane. Use the plane separation angle to define the spacing between each plane, and apply inter-plane phasing as needed to adjust the relative positions of satellites between planes. Once all configurations are complete, click Create to generate the satellite group. In the active model, click on the group to view all the satellites associated with that group.

9.1.1.3 Creating TLE Track

Click the TLE Track option to create satellites from TLE data. Upload your TLE file, which can contain data for a single satellite or multiple satellites in bulk. If needed, you can download a sample format from ACP to help ensure your file is correctly formatted. Once the file is uploaded, ACP will automatically create satellites based on the TLE information provided.

To differentiate between manually created satellites and those uploaded via TLE, look for the launch symbol next to the satellite group. This icon indicates that the group was created using a TLE upload, helping users easily identify the source of satellite data within the active model.

You can double-click any object to rename it for better identification. Use the eye icon to hide or show objects on the map, helping reduce visual clutter during mission planning. Hover over any object to highlight its position on the map.

9.1.2 Geofeatures

Geofeatures represent AOI's on Earth. To add a new geofeature, click the “+” icon, and choose either a polygon or a point depending on your requirement. Once created, the geofeature will appear in the current list and will also be saved under the main Geofeatures section for future use.

9.1.3 Ground Stations

Displays all ground stations which are predined and user-created stations and stations available under the GSP. To add a new ground station, simply click the “+” icon and configure the necessary details. If any ground station associated with the GSP is deleted from this section, it will no longer be part of the GSP. Instead, it will appear as a standalone ground station on the "Ground Stations" page

9.2 Analysis

Enables users to evaluate their mission models. It offers tools like Coverage Analysis, Ground Contact Analysis, and Propulsion Budget Analysis. By selecting configured objects such as satellites, ground stations, and geofeatures, users can run detailed analysis over custom time durations and conditions. Each analysis provides actionable insights through reports and visual overlays.

9.2.1 Coverage Analysis

To analyze how effectively satellites observe an AOI. Start by selecting the relevant satellites and geofeatures, then define the start time and duration of the analysis period. You can specify the lighting conditions as Sunlit only, Eclipse only, or Both, depending on your mission requirements.

9.2.2 Ground Contact Analysis

This evaluates contact windows between satellites and ground stations. To perform the analysis, select the relevant satellites and ground stations, then specify the start time and duration for the analysis period.

9.2.3 Propulsion Budget Analysis

This calculates mission fuel requirements, thrust, delta-V and many more for a satellite. Start by selecting a satellite, then click the “+” icon to add a thruster, if not added already. Configure the thruster parameters based on your mission requirements. Next, define the orbit environment, satellite properties, and any perturbation forces.

9.3 Reports

All analyses generate detailed reports that include the user-configured inputs, computed outputs, and a map visualization of the relevant objects. You can filter reports by analysis type and easily differentiate them based on specific objects or configurations used.

Platform Access

Access to ACP is limited to parties authorized directly by Antaris, Inc. Individuals that are associated with an active customer or partner of Antaris should work with the appropriate ACP Tenant Admin to provision a new user account.

For those with existing user accounts, simply navigate to https://app.antaris.cloud in a web browser and provide individual credentials to log in. After logging in, users will be able to access to a shared Tenant.

The maximum number of satellites and concurrently running Scenarios in a mission is capped. This configuration can be customised upon prior request to Antaris Support Team.

If you are having trouble logging in, you can click on “Forgot Password?” at the ACP login page to trigger a password reset. You should contact the support team [email protected] for further assistance, if needed.

Those not associated with active customers can contact the Antaris sales team at [email protected] to discuss licensing.

Quickstart

This article quickly drives a user through the key workflows in ACP. This describes how a user with limited experience can quickly orient themselves within ACP.

After establishing an ACP user account, the first task is to define a Mission. This input is used to inform later design choices and satellite operations:

If you are not prompted to set up your Mission, it is likely another member of your team has already done so. You can always edit the mission from the DESIGN dashboard if updates are required.

Next, create a Satellite based on the necessary spacecraft design requirements. During this process, you will define satellite payloads, add edge compute resources, then choose an appropriate Bus Design. Decisions need not be final before walking through this process, as a design can be modified later:

After creating a Satellite, proceed to deploy it with TrueTwin™. Jump over SIMULATE tab and click 'Create New Scenario' to deploy the scenario. Be sure to select HWIL option and provide necessary options which causes ACP to automatically launch the new TrueTwin into your mission’s orbit:

At this point, you now have a fully functional TrueTwin satellite. Familiarize yourself with the Satellite Console and the Telemetry interface, and review the satellite’s orbital trajectory:

When finished, simply use the “Retire” action in the bottom right hand corner of the screen to tear down the running TrueTwin satellite.

Now that you have completed this Quickstart, you are encouraged to explore the rest of this guide and continue your journey with the Antaris Cloud Platform!

TrueTwin Technology

TrueTwin enables high fidelity simulation of entire space missions. This encompasses all relevant physical entities, the software components deployed within them, and the environmental effects that impact them. This article describes the TrueTwin architecture, and how TrueTwin capabilities can be used to effectively simulate your own missions.

Concepts

TrueTwin Satellites represent discrete spacecraft participating in simulated mission segments. Each TrueTwin Satellite may act as a direct digital twin of a real spacecraft or represent planned capabilities yet to be launched on orbit.

TrueTwin Satellites are deployed using integrated software models that represent logical software and hardware components operating within a satellite system. Satellites may also incorporate user-provided software and hardware components collocated in an ACP environment or remotely connected from locations anywhere in the world.

In all deployment models, TrueTwin Satellites operate real flight software. It is architecturally just another model operating within a virtual satellite, which happens to control other components. Users may decide to use Antaris SatOS flight software to fill this role, but any other flight software solution may also be integrated into a simulation.

TrueTwin Ground Stations offer communications capabilities to TrueTwin Satellites using RF or optical infrastructure. Each Ground Station may be defined to represent real world capabilities, or simply provide some potential capability.

TrueTwin Scenarios describe the overall scope and content of a simulation. Scenarios act as a simulation runtime that hosts all elements in the same universe of existence so they can carry out a relevant mission segment.

TrueTwin Scenarios may represent a future mission segment that has yet to happen, or a segment that has occurred in the past. This allows users to better diagnose anomalies, evaluate alternate onboard schedules, or simply explore mission solutions.

Scenarios may be executed in realtime or in accelerated time. Realtime scenarios are typically used to perform distributed simulations with some hardware in the loop. Accelerated time is used when all elements are deployed using pure software models in a collocated environment, and operator interaction is not desired.

Satellite Simulation

TrueTwin Satellites directly represent real satellite systems, abstracting subsystems and components such that software-based models may be easily configured to represent real world elements. The same abstraction enables users to dynamically incorporate distributed hardware and software components into a common simulation. This powerful satellite virtualization capability enables users to execute simulations at any point in a mission lifecycle with whatever level of fidelity is desired.

System Design

The TrueTwin Satellite architecture is comprised of three primary layers:

Flight Software operates within a TrueTwin Satellite in a semiautonomous mode, receiving commands over a simulated TT&C link while also handling automated onboard operations. Antaris SatOS is integrated natively into TrueTwin and can be used through the entire mission lifecycle, including the operational phase. Users may also decide to integrate other flight software solutions.

Space Vehicle systems are abstracted through a set of carefully-designed APIs exposed to the onboard flight software. These elements are all simulated within physical space connected to a common structure. This is a critical aspect of TrueTwin, as any operations carried out by an individual actuator such as a reaction wheel will accurately affect the space vehicle, and will also affect measurements through relevant sensors such as angular rates from an IMU and power draw from a battery.

Space Environment represents elements like celestial bodies (Earth, Sun, Moon), physical forces (drag, gravity), and even other orbiting objects. Just as an explicit actuator operation will have a physical impact on a space vehicle, so will the models operating within the space environment. For example, the spacecraft attitude and its position relative to the Sun will influence the output of the solar panels.

Sensors & Actuators

Below is a description of the simulated bus sensors and actuators within a TrueTwin Satellite. Note that much of the configuration is provided automatically through the bus configured from the device catalog.

Name

Config

Notes

Coarse Sun Sensor

* Field of view * Orientation * Measurement bias * Measurement noise * Scale factor

Configuration values provided per sensor

Magnetometer

* Orientation * Measurement bias * Measurement noise * Scale factor

Configuration values provided per sensor

Star Tracker

* Measurement noise * Rate error modeling * Sun and Earth Keep-out triggers

Configuration values provided per sensor

IMU

* Orientation * Gyro and Accelerometer noise * Measurement bias * Scale factor

GNSS

* Refresh Rate * Latency * Acquisition Time * Position, Velocity, and Time Noise

Torque Rod

* Orientation * Dipole

Configuration values provided per actuator

Reaction Wheel

* Wheel layout (3- or 4-wheel orientation) * Maximum speed * Maximum momentum * Maximum torque * Static/dynamic imbalances

Configuration values applied per wheel

Thruster

* Location * Orientation * Maximum thrust * Nozzle area * ISP * Propellant consumption

Power

TrueTwin Satellites contain a complete power system. This includes power generation via solar panels, storage within battery packs, and distribution to simulated devices.

Power generated through solar panels is configured using the following inputs:

Total panel area
Charging efficiency
Panel orientation

Onboard power storage relies on configurable battery packs. A satellite may contain a configurable number of cells, each with its own defined storage capacity.

Power consumption is configured per component with static voltage and current parameters. The power status of each component can be toggled during TrueTwin simulations.

Reaction wheel power consumption is modeled based on the current speed of each wheel.

Environmental Models

Below is a description of the models configured within the space environment that have an effect on the simulated space vehicle independently of any flight software control path:

Name

Configuration

Celestial Body Gravity

N/A

Earth Magnetic Field

N/A

Atmospheric Drag

* Surface area * Drag coefficient

Solar Radiation Pressure

* Surface area * Reflection coefficient

Gravity Gradient Torque

* Moment of inertia * Center of mass

Orbit Propagation

TrueTwin simulation uses a high-fidelity orbit propagation method to propagate satellite orbits. This is not configurable by end users.

Distributed Simulation

TrueTwin supports engineers in the development of satellites using physically distributed systems. This enables a variety of simulation modes across individual bus components, vendor-provided simulators, payload devices, and more. The TrueTwin architecture allows this wherever a common network is available, typically facilitated through secure tunneling over the public internet or through a private corporate network.

Bus Components

Any bus component described in the TrueTwin Satellite System Design may be connected to a simulation remotely. This capability is typically used in support of the integration of a specific hardware component a flight software solution.

Payload Devices

Payload devices are further generalized than bus components, as the operation of a given payload is more open ended. Integration of any payload is governed by an SDK, which is available in the SatOS-Payload-SDK repository.

ACP SatOS Operations Manual

1. ACP Operational Overview

1.1. ACP Operate General Information

The Operate tab provides the interface for satellite operators to interact with the satellite. Upon entering the tab, the list of promoted satellites will be provided on the side, with a map of the globe in the center. Upon selecting a satellite, the operator will enter the Heads-up Display (HUD).

1.1.1. HUD

The HUD shows the operator the most important information about your satellites in a clear and easy-to-understand way. This information includes:

· The current location and orbit of a satellite (or a fleet of satellites).

· The tasks your satellites are currently working on and any upcoming events.

· Any warnings or alerts that need attention

From the HUD the operator can access multiple windows using buttons to assist their work. Each of these buttons opens up a secondary window that can be dragged or pinned on the screen. The top left has a home button to return to the previous screen, as well as the satellite name and TLE details. By accessing the TLE details the operator can view the TLE currently uploaded to the satellite, the date it was updated, and potentially manually update the TLE.

In the top right the operator will find the quick actions panel with 4 more buttons: Onboard Schedule, Console, Telemetry, and File Queue.

1.1.2. Onboard Schedule

This button opens a window showing the schedule onboard the satellite. It shows the details for each event in sequence for the satellite, including telemetry and payload downlinks, payload events, and scheduled uplinks.

1.1.3. Console

This button opens up the command console and messages for the operator.

Viewing Live Telemetry through the Console

A table with the most recent command and telemetry messages sent and received will populate. The command field indicates whether the message was a command (TC) or telemetry (TM) message, and the message color indicates whether the message was successful or not. Selecting the message will display additional information about the message in the space below, including the undecoded hex data and the decoded JSON packet details of the message. Each message is unique in the packet details and more information can be found in the telemetry and command database.

Message Colors:

Yellow: Successful command that induced a corresponding telemetry response from the satellite
Green: Telemetry response from a corresponding command
Blue: Beacon or health metric telemetry
Red: Incomplete, potentially corrupted message
None: Command that did not induce a telemetry response detected by ACP

Manual Telemetry and Raw Bytes

At the top of the console window, in addition to the typical minimize, pin, and close buttons found on most windows, there is a toggle for raw bytes and a button to upload a file. The raw bytes toggle will show only the raw bytes for each message but may also display messages that were partially corrupted due to loss of data. The upload file button allows an operator to manually import a telemetry file in the event that telemetry is not visible in ACP.

From this window the operator can select a band type, ground station ID, and epoch to upload the file to the satellite. The file itself can be dragged onto the section once that information has been filled out, or the operator can select it manually. Once the telemetry is imported, a success message will be displayed and the file will be visible in the command telemetry messages window.

Commanding and Uploading Files through the Console

The left side of the window offers the command console, an interface for the operator to send manual commands to the satellite. Starting from the top, the operator may select TT&C to send single manual commands from the database, or TASK to send ad hoc tasks or upload a schedule. The TASK window can also be used to manually upload files to the satellite, like payload firmware updates. The operator can select “Upload File” from the task type window and select a file to upload or provide the information manually. Once everything is confirmed, the file upload and corresponding details will appear in the file queue window.

If TT&C is selected, the operator can filter the tasks using selections for bus, payload, or raw input components, as well as filtering based on subsystem or an editable text field for command id or command number. After the operator has selected a command or group of commands to upload, it needs to be assigned to a contact. This can be done at the bottom of the contact window. By default, the next contact appears showing the location and time until the start of the contact window. The operator can also select the calendar button below, to select a specific contact window instead. Once the contact is selected, the operator can hit “Schedule Now” and the command or commands will be added to the queue of telecommands for the satellite in that contact window. These telecommands will have a Bytes Length of 0 until they are sent during their scheduled contact. If the operator selects a contact window for which the satellite is already in, the “Schedule Now” button will instead say, “Execute”, and the command will be sent immediately.

If an operator would like to send commands or downlink telemetry on a specific band (UHF or SBand), the operator should select the contact that has the desired configuration. No explicit telecommands are needed to configure the communications link.

It is possible to send raw commands in the form of undecoded hex data by selecting Raw Input as the Command Type. This is useful for sending commands that are complicated to modify within the JSON view. Typically, these raw commands are provided by a subsystem specialist. The operator will need to specify whether or not the packet header is included in their provided byte stream.

1.1.4. Telemetry

The 3^rd button in the quick action panel provides a quick option to display some of the more important historical telemetry of the satellite. This display provides graphical information that is easy to digest for each of the satellite subsystems. The operator can select which subsystem from a drop-down menu at the top. From each graph, the operator can use hover their cursor over a location to provide more information. The operator can also click and drag over an area to home in on key ranges. The information provided here is a subset of the information provided on the Monitor tab.

1.1.5. Contacts and Events

The HUD also provides the operator with important upcoming information for contacts and events. Ground contact opportunities are provided by the ground station provider as inputs into ACP and then will be displayed in several locations. The bottom of the screen shows a running window of the satellite schedule, that can be configured between 30 minutes and 3 hours. In it the operator is able to visualize any upcoming, current, or previous events as well as look further ahead or back by selecting arrows at the far right or left respectively. On the left side, the operator can filter the events displayed by selecting drop down and choosing between ground contacts, onboard schedule, or both options. Above the dropdown, the HUD displays the most recent completed contact and the next upcoming contact as well as some information about each.

1.1.6. Settings

The settings button in the bottom right allows the operator to configure the display of the Earth to their preference. This gives the operator the ability to zoom in and out of the map, toggle a 2d or 3d view, change the mapbox style to a satellite/dark/light view, as well as an eclipse toggle to show the light and dark sides of the Earth.

1.1.7. Plan

In addition, the HUD tab, there is also the Plan and Monitor tab. Both of these tabs provide expanded information for that is displayed in the Onboard Schedule, Ground Contact, and Telemetry Displays. The Plan tab has two subtabs for Onboard Schedule and Ground Contacts. This Onboard Schedule subtab provides a larger number of schedule events as well as additional information about each event. The operator can also use the buttons at the top right of the display to manually import or generate schedules for the satellite.

The Ground Contacts subtab displays all available ground stations in a table with their scheduled and previous ground contacts. The operator can select a ground contact to display additional information about it on the right-side including contact type, duration, start time, and an image of the location of the ground station on the world map.

1.1.8. Monitor

The Monitor tab provides the similar graphical views of historical telemetry of the satellite as the telemetry quick action button in a larger format. These graphs have the same subsystem filters as well as the same analytical capabilities. The operator may change the view to grid or list in the top right, as well as filter based on date range.

2. Operating a Satellite

2.1 Satellite Behavior

The satellite often experiences repeated behavior while on orbit. While this behavior may change, it is intended to help the operator with some activities, observations, and operational procedures performed during the daily monitoring of a satellite.

2.2.1. Orbit Characteristics

The satellite operates in a Sun-Synchronous Orbit (SSO) at an approximate altitude of 450 km. It will complete one Earth revolution every ~90 minutes, maintaining consistent local solar time for surface overpasses. During each orbit it will experience sunlight ~55-60 minutes and eclipse ~30-35 minutes. It will also undergo the following during an orbit:

· Battery systems alternate between charging (sunlight) and discharging (eclipse)

· Elevated Battery Discharge during payload and propulsion states

· Thermal states fluctuate with sunlight exposure

· Attitude control systems maintain nadir pointing or payload-specific orientations

2.2.2. Ground Contacts

The satellite will pass within view of a ground station while it is in orbit. With sufficient pass parameters (time, elevation, weather) the satellite can communicate with the ground station in a contact. These contacts are usually 5-10 minutes and occur roughly 3-6 times per station per day. These contacts serve as the only way to uplink and downlink data from the satellite. While the satellite is not in a contact window, it is operating autonomously and collecting and storing payload and telemetry data. Then during a contact window, this data can be downloaded from the satellite. The longer the satellite goes without downlinking the data stored onboard, the more data it has stored within and there can be issues with both data storage as well as downlink bandwidth to address. These contact windows are also where the operator can communicate through a ground station with the satellite to issue commands or update the satellite firmware. These commands can be scheduled ahead of time or run manually during a contact.

2.2.3. Beacons

The satellite will automatically emit beacons at regular cadences that are predetermined in the SatOS software. These beacons contain top-level satellite health information and will appear in the Console regularly, and are not induced by any telecommand. Beacons are emitted from both the UHF and S-Band modules at different cadences, but contain the same information

TM-815 = OBC beacon transmitted via UHF (4 packets emitted every 1 minute)
TM-411 = OBC beacon transmitted via SBand (2 packets emitted every 2 minutes)

Beacons are a good way to passively verify the ground receive/satellite transmit path as well as gather onboard information prior to executing any activity.

2.2.4. Day-in-the-Life Operator Tasks

Common operator tasks for a satellite vary by mission and by the phase that mission is in, but in general some procedures would include the following:

· Review and trend downlinked telemetry to monitor long term satellite subsystem health.

· Prepare command loads and scheduling updates for upcoming passes.

· Plan and verify payload tasking for upcoming daylight passes.

· Identify and address anomalous behavior

Please see Section 3.1 and 3.2 for examples of pre-launch and post-launch operator tasks

2.3. Upload Files

in Operate > HUD open the Console
Go to the Task tab in the left pane
Choose Task Type = Upload File
Select Choose File to upload a locally-stored file to ACP
Use the following parameters
1. App ID: 134
  1. ID 134 = PS (Payload Server)
2. File ID: same as file name
3. Destination ID: 134
4. Max Transmission Unit: 1300
5. Delay: 200
6. Activity Timeout: 200
7. Connection Timeout: 200
8. Loss Detection: Enabled
Click Upload File
Look for a pop-up message indicating success or failure

2.4. Command Sequencing with Adhoc Tasks

ACP can automate sending a set of commands from the ground with relative delays (in seconds) between each telecommand. While they does not completely remove the operator from the loop, adhoc tasks significantly reduce operator error and bandwidth when taking contacts.

Create Task

Go to Design > Satellites and click on your desired satellite
Go to Operations > Tasks and click Create Task
Enter a Task Name
Choose Task Type Adhoc
Click + Telecommand
Add your desired Telecommand based on Input Type
1. Use Telecommand Builder for telecommands that can be sent with their default values
  1. Component: Subsystem to send telecommand to
  2. Telecommand: Telecommand ID and string
    Can use ID in dropdown for easier search
  3. Preview: Telecommand JSON with default values (cannot be modified)
2. Use Raw Input for telecommands that need their default values modified
  1. Copy and paste your desired telecommand JSON into the input box
Add Delay (in sec) at the bottom of the Task Creation window
1. It is recommended to add at least 7 seconds of delay for each telecommand to avoid undesired OBC resets
Add the telecommand
Repeat steps 5-8 for all telecommands
To rearrange the order of telecommands, click the 6 dots to the left of the telecommand and drag to the desired order
Save the Task Plan

Execute Task

Go to Operate and click on the desired promoted satellite
In the top right of the HUD view, click on Console
In the Console, go to the Task tab
Choose
1. Task Type: Adhoc Task
2. Task: Title of desired task
In the bottom left of the console, click on the calendar icon next to Schedule Now
Choose the contact to deploy this adhoc task to
A highlighted box with the contact info will appear. Make sure that this is the desired contact
Click Schedule Now
Check to see if the telecommands are in the queue by cross-checking TC IDs. These queued telecommands will have a Bytes Length of 0
1. You may need to close and re-open the Console to see the queued telecommands
The AdHoc tasks will begin 15 seconds after expected AOS. One can verify that telecommands are being sent by watching each Bytes Length field change to a nonzero value.

3. Common Operational Tasks Using ACP

3.1. Examples of Pre-Launch Tasks

Common flatsat activities performed before launch can be broken down into functional tasks which focus on validating subsystem behavior, and mission planning tasks which focus on higher-level operations and flight team readiness.

Functional Tasks
- Test subsystem commissioning and health checkouts (EPS, ADCS, OBC, TT&C, Propulsion, and Payload)
- Validate command execution and telemetry generation
- End-to-end communication verification between ACP, ground software services, and the flatsat or
- Power modeling (e.g., boot, safe, nominal)
- ADCS Modeling (Detumble, Sun pointing, Nadir Pointing, Target Pointing)
Mission Planning
- Verify automated LEOP sequences and scripts
- Verify LEOP procedures that require operator intervention
- Train operators and familiarize them with the satellite, procedures, tooling, and operational workflow and intuition
- Rehearse LEOP procedures with subsystem specialists and greater flight team

3.2. Examples of Post-Launch Tasks

Flatsat activities commonly performed after launch focus on recreating and debugging anomalies that transpired in the production environment, verification of future activities, and further software development.

Anomaly response analysis and verification
Onboard schedule and adhoc task acceptance testing
Software development and acceptance testing

3.3. How to Execute Routine Operator Tasks

3.3.1. Induce an Automated Health Metric Dump

The OBC logs predefined telemetry from various subsystems. To access this stored telemetry, one can induce a health metric dump in three ways:

Send any TC at least 2.5 minutes after the last TC has been sent. This will dump all historical telemetry across all subsystems
Send TC - 621 Get Health Data of All Submodule All Queue to explicitly dump all historical telemetry across all subsystems
- If inducing over UHF over-the-air, it may take up to 2 minutes to receive all telemetry. Commanding may be limited during this downlink period
Send TC-621 for your desired subsystem
1. The operator can look up the appropriate command string for TC-621 when using Console or Ad-Hoc Task Creation (ex: for OBC-specific health metrics, choose 621 - Get OBC Health Telemetry Configuration)

The Submodule IDs and Queue IDs for each health metric packet is located on the far right side of the Console under Info. The Submodule ID’s are listed below as reference:

0 = EPS
1 = ADCS
2 = COMMS SBAND
3 = COMMS UHF
4 = SENSORS
5 = OBC
6 = ERROR HANDLER

If an operator would like to downlink health metrics on a specific band (UHF or SBand), the operator should perform this downlink over a contact that has the desired configuration. No explicit telecommands are needed to configure the communications link.

3.3.2. Disable an Automated Health Metric Dump

Sometimes, the automated health metric dump can impede operations in several ways:

Makes commanding impossible during the downlink during bi-directional UHF operations (since UHF is half-duplex)
Takes a non-trivial amount of power to transmit all health metric data, especially over S-Band
Crowds the telemetry logs, impeding time-sensitive decision-making

To disable this feature, send TC-622 Change Queue Priority of All Submodules

CurPriority = 0
IsSingle = 3
Priority = 2
QueueID = 255
SubmoduleID = 255

To re-enable automated health metric dumps, send TC-622 Change Queue Priority of All Submodules again with the following parameters:

CurPriority = 2
IsSingle = 3
Priority = 0
QueueID = 255
SubmoduleID = 255

3.3.3. Query EPS Power State

To query the current power state of the batteries, boards, and solar panels, send TC-200
To query historical power states, induce an EPS health metric dump with TC 621 - Get EPS Health Telemetry Configuration

3.3.4. Payload/Edge Application Upgrade

Build application artifacts (upgrade_artifact.tar) with Docker
1. Create .tar images of the “factory” version and the “updated” version. command: docker save -o <image_name> <image>:<tag>
  - “Factory” version should be available at <payload directory prefix>/factory_image/ directory on PS
  - ex) satos-payload-antaris:factory is the name of the docker image of factory version. docker save -o satos-payload-antaris-app_factory.tar satos-payload-antaris-app:factory
  - ex) satos-payload-antaris:latest is the name of the docker image of updated version.
    docker save -o satos-payload-antaris-app_latest.tar satos-payload-antaris-app:latest
2. Generate upgrade_artifact.tar using the factory image tarball and the updated app image tarball
  - Use the bash script create_docker_artifact_tar.sh to generate the app artifacts. This script assumes that docker version being used is >=25.0.0
  - Run the bash script with bash create_upgrade_docker_artifacts_tar.sh -f <factory image tarball> -u <updated image tarball>
Upload upgrade_artifact.tar with the parameters (refer to section 2.3)
1. App ID = 134
2. Destination ID = 134
Send TC-609 (app id = 136) to confirm the current app image tag on the flatsat
Send TC-610 (app id =136) to upgrade the app image to the new tag
- This upgraded image will be stored under the factory_image directory with the tarball titled "<PAYLOAD_IMAGE_NAME>_update.tar"
Verify in TM-610 that Response = 0 (success)
1. IF Response != 0: Skip to step 8
Send TC-611 (app id = 136) to upgrade the factory image to the latest update tag
Verify in TM-611 that Response = 0 (success)
IF app image response was not successful, restore the previous factory image with TC-612 (app id = 136)
Send TC-609 (app id = 136) to confirm that the current app image tag is the updated tag

Ground Communications

This article describes how the Antaris Cloud Platform (ACP) facilitates ground-based communications with satellites. The diagram below illustrates the conceptual architecture:

The Ground Segment encompasses everything operating on the earth in support of a satellite mission. This includes, for example, Ground Station hardware, ACP software, and supporting services such as Space Situational Awareness (SSA) providers.

Satellites communicate with the Ground Segment during scheduled Ground Contacts. Many distributed components may be coordinated during a Ground Contact in order to establish a connection, typically including active tracking of the satellite by ground station antennae. The satellite may also need to actively track the ground station.

Individual Ground Contacts typically fit one of three use cases:

TT&C (Telemetry, Tracking & Command): primary communications path used to control the satellite. These are typically lower bandwidth, bidirectional communications links using S-Band or UHF transceivers
Teledata: used to download payload data using high bandwidth communication paths like X-Band, Ka-Band, and Optical links
Beacon: critical health telemetry transmitted over highly resilient, low bandwidth links like UHF

ACP takes the ultimate responsibility to orchestrate Ground Contacts but can rely on external services to handle individual elements of the overall solution as needed. For example, ACP can build a tracking model for a satellite, or it can fetch a TLE from an external source like space-track.org. ACP can also control ground station infrastructure and coordinate SDR software/hardware, or delegate that responsibility to a third party GSaaS provider.

Contact Scheduling

ACP orchestrates the Ground Contact schedule for all satellites under management. The scheduling process generally works like so:

Build a set of contact opportunities for a given satellite using recent orbital ephemeris and configured ground station access requirements
Fetch prescheduled contacts from ground station providers, if available
Optimize the ground contact schedule based on operator-defined policies, pending control tasks, and projected data downlink requirements
Publish contact schedule back to ground station providers
Upload contact schedule to satellite at next opportunity

Some ground stations may be fully under the control of ACP and used only by a single satellite. Many additional operational capabilities are available:

Support for multiple satellites within ACP, even shared across missions and tenants
Scheduling exceptions for satellites managed outside of ACP (i.e. facilitating external multi-tenant operation)
Externally controlled contact scheduling, delegating decision-making to a third party

ACP directly manages all of these complexities and gives users effective controls over when and how ground contacts are ultimately executed.

Contact Execution

Once a Ground Contact has been scheduled, ACP will wait until it is ready for execution then take the appropriate action.

For TT&C contacts, ACP will take the following approach:

Initiate all required data plane connections to the provider
Begin listening for telemetry through the data plane. Parse received messages and aggregate them into necessary telemetry dashboards
Enable the message console so users can send Telecommands directly to the connected satellite
Automatically process any pending control tasks, such as deploying an updated schedule and uploading files

For Teledata contacts, ACP orchestrates ground contact scheduling but delegates data plane responsibilities to the Ground Station Provider. Payload data is routed directly into storage services rather than ingested into ACP.

For Beacon contacts, the uplink capabilities of ACP are simply not enabled. The contact is executed in a “listen-only” mode. Any received telemetry is still ingested as would be done for a full TT&C contact.

Ground Station Providers

ACP uses the “Ground Station Provider” abstraction to define ground station capabilities and relevant access parameters. Each provider includes the following:

A set of physical ground station locations and the available communications capabilities
An API endpoint that can be used to manage Ground Contact scheduling for the configured Ground Stations
Service endpoints that host relevant data plane APIs

This abstraction is applied to both first- and third-party ground stations.

First Party Ground Station Integration

Users are able to directly integrate ACP with first party ground station software and hardware through a simple API-driven abstraction. This allows users to bring their own ground station infrastructure online in support of production satellite operations with minimal overhead. An SDK is available to assist in implementation of these APIs, and users are free to implement them directly in whatever software is most appropriate.

Ground contact schedules are managed through a simple JSON-based API, while the data plane is connected through a simple set of MQTT topics.

Supported Ground Station Services

Below is a description of the “Ground Station as a Service” (GSaaS) integrations available in ACP. Each of these requires a user to establish a commercial relationship with a third party, then ACP can integrate with the services offered by that third party.

ATLAS Space Operations

Users may configure a Ground Station Provider with access to the ATLAS Freedom API. This requires that the user already has a support agreement in place with ATLAS Space Operations.

This integration supports:

Ground contact scheduling, syncing in both directions between ACP and the Freedom API
Data plane access using the websocket endpoint offered by the Freedom API

Leaf Space

Users may configure a Ground Station Provider with access to the Leaf Space API and MQTT broker. This requires that the user already has a support agreement in place with Leaf Space.

This integration supports:

Ground contact scheduling, syncing in both directions between ACP and the Leaf Space API
Data plane access using the Leaf Space MQTT broker

Release Notes

v24.7 Release Date: November 14, 2024

Updates

Mission-scope GeoFeature (geospatial feature) management
Schedule Predictions describing estimated performance of satellites before TrueTwin Scenario deployment (must recreate scenario for this feature to be available)
Raw message mode in TT&C console
User-provided 3D model upload per Satellite

Known Issues

PM-79: Telecommands for VM Power ON (545) and OFF (546) fail due to issue with OBC software
PM-93: If a Payload Task is updated after creating a Task Plan, the updates do not carry through to the existing Task Plan
PM-94: User may experience issues in scenario simulation if orbital eccentricity is between 0.04 and 0.05 and if the scenarios are re-run.
PM-96: Frequency input in Task Plan is not yet supported
PM-128: Payload Server memory usage and CPU usage telemetry is not observed in some cases

v24.6 Release Date: September 18, 2024

Updates

Integrated SatOS v1.8.7
More effective UX supporting production satellite operations and simulations.
New HUD giving users a summarized view of onboard and ground schedules, active satellite tracking information, and a quick view of system telemetry.
Comprehensive ground contact schedule interface.
Historical TT&C console with per-message introspection.

Known Issues

PM-79: Telecommands for VM Power ON (545) and OFF (546) fail due to issue with OBC software.
PM-93: If a Payload Task is updated after creating a Task Plan, the updates do not carry through to the existing Task Plan.
PM-94: User may experience issues in scenario simulation if orbital eccentricity is between 0.04 and 0.05 and if the scenarios are re-run.
PM-96: Frequency input in Task Plan is not yet supported.
PM-128: Payload Server memory usage and CPU usage telemetry is not observed in some cases.

v24.5 Release Date: August 15, 2024

Updates

Payload and EPS Current discrepancy issue has been resolved.
Data generation configuration moved to payload sequences from payload devices.

Known Issues

PM-79: Tele commands for VM Power ON (545) and OFF (546) fail due to issue with OBC software.
PM-93: If a Payload Task is updated after creating a Task Plan, the updates do not carry through to the existing Task Plan.
PM-94: User may experience issues in scenario simulation if orbital eccentricity is between 0.04 and 0.05 and if the scenarios are re-run.
PM-96: Frequency input in Task Plan is not yet supported.
PM-127: While cloning a scenario, user may need to reselect ground stations manually, if it is not automatically populated.
PM-128: Payload Server memory usage and CPU usage telemetry is not observed in some cases.

v24.4 Release Date: July 19, 2024

Updates

Replay of simulated scenarios Information displayed when hovering over ground station in simulation.
Filtering vendors during bus design selection.

Known Issues

PM-79: Telecommands for VM Power ON (545) and OFF (546) fail due to issue with OBC software
PM-93: If a Payload Task is updated after creating a Task Plan, the updates do not carry through to the existing Task Plan
PM-94: User may experience issues in scenario simulation if orbital eccentricity is between 0.04 and 0.05 and if the scenarios are re-run.
PM-95: Discrepancy in Payload and EPS Current Value if channel and payload voltage do not match
PM-96: Frequency input in Task Plan is not yet supported

v24.3 Release Date: July 4, 2024

Updates

Integrated SatOS v1.8.6
Added tele command support for manual TrueTwin thruster control via console
Exposing additional telemetry for ADCS subsystem: sun sensor and magnetic field vectors, angular rate and reaction wheel speed
Changed reference frame of spacecraft attitude telemetry to velocity frame from inertial frame
Support introduced for configuration of Ground Station Providers: Leaf Space, ATLAS, and a user-defined "custom" type.

Known Issues

PM-79: Telecommands for VM Power ON (545) and OFF (546) fail due to issue with OBC software
PM-93: If a Payload Task is updated after creating a Task Plan, the updates do not carry through to the existing Task Plan
PM-94: User may experience issues in scenario simulation if orbital eccentricity is between 0.04 and 0.05 and if the scenarios are re-run.
PM-95: Discrepancy in Payload and EPS Current Value if channel and payload voltage do not match
PM-96: Frequency input in Task Plan is not yet supported

v24.2 Release Date: May 24, 2024

Updates

Enhanced the schedule generator to produce schedules for 24-hour period.
Implemented additional visual controls within Scenario runtime: dark and light vector basemaps, eclipse visualization, and zoom controls.
Expanded details available in Scenario Task Queue with individual telecommand details.
Added Payload Sequences to all pre-existing Payloads in catalog.

Known Issues

PM-79: Telecommands for VM Power ON (545) and OFF (546) fail due to issue with OBC software.
PM-93: If a Payload Task is updated after creating a Task Plan, the updates do not carry through to the existing Task Plan.
PM-94: User may experience issues in scenario simulation if orbital eccentricity is between 0.04 and 0.05 and if the scenarios are re-run.
PM-95: Discrepancy in Payload and EPS Current Value if channel and payload voltage do not match
PM-96: Frequency input in Task Plan is not yet supported.

v24.1 Release Date: Feb 18, 2024

Updates

TrueTwin Scenario creation UX redesigned for more interactive feedback
Upgraded TT&C support for SatOS v1.6
Improved precision of TrueTwin ADCS and EPS subsystems

Known Issues

PM-79: Telecommands for VM Power ON (545) and OFF (546) fail due to issue with OBC software.
PM-93: If a Payload Task is updated after creating a Task Plan, the updates do not carry through to the existing Task Plan.

Terms of Service

Last updated December 12, 2022

THESE TERMS OF SERVICE (THE "TERMS") ARE A LEGAL AGREEMENT BETWEEN YOU ("CUSTOMER") AND ANTARIS, INC. ("ANTARIS"). BY EXECUTING A PROJECT AGREEMENT (AS DEFINED BELOW) THAT INCLUDES THESE TERMS BY REFERENCE OR BY USING THE ANTARIS PLATFORM, CUSTOMER ACKNOWLEDGES THAT CUSTOMER HAS REVIEWED AND ACCEPTS THESE TERMS. IF YOU ARE AGREEING TO THESE TERMS AS AN INDIVIDUAL, “CUSTOMER” REFERS TO YOU INDIVIDUALLY.  IF YOU ARE AGREEING TO THESE TERMS AS A REPRESENTATIVE OF AN ENTITY, YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO BIND THAT ENTITY AND “CUSTOMER” REFERS TO THAT ENTITY.  IF CUSTOMER DOES NOT AGREE WITH ALL OF THESE TERMS, DO NOT ACCESS OR OTHERWISE USE THE ANTARIS PLATFORM.  

In consideration of the mutual promises and agreements set forth in these Terms, the parties agree as follows: 

1. DEFINITIONS. 

1.1. “Antaris Platform” means the Antaris satellite design and testing platform provided by Antaris; provided that such definition excludes the Spacecraft Software and any Open Source Software that may be used to provide such platform. 

1.2. “Authorized Purposes” means, unless otherwise permitted in an applicable Project Agreement, use of the Antaris Platform solely for Customer’s internal purposes in designing satellites and testing virtual simulations of such designs, and not for the provision of services to any third party. For avoidance of doubt, Authorized Purposes includes use of the Antaris Platform to demonstrate its capabilities to potential clients but not, unless otherwise permitted in an appliable Project Agreement, to provide services to such potential clients.  

1.3. “Authorized Users” means Customer’s employees, consultants, contractors, and/or agents: (a) who are authorized by Customer to access and use the Antaris Platform on Customer’s behalf, and (b) who have been supplied user identifications and passwords for such purpose by Customer (or by Antaris at Customer’s request). 

1.4. “Confirmed Client” means a third party with whom Customer has contracted to design and build one or more satellites (as set forth in an applicable Project Agreement) and with whom Antaris has entered into a written agreement to use the Antaris Platform and Spacecraft Software. Antaris must provide written confirmation that a Customer client is a Confirmed Client before Customer is permitted to use the Antaris Platform to provide services to such client. 

1.5. “Customer Data” means all Customer and Confirmed Client data submitted, stored, posted, displayed, or otherwise transmitted by or on behalf of Customer or its Authorized Users, and received and analyzed by the Antaris Platform. 

1.6. “Customer System” means Customer’s internal computers, servers and other equipment and software used to access and use the Antaris Platform. 

1.7. “Documentation” means the printed or electronic user instructions and help files made available by Antaris for use with the Antaris Platform, as may be updated from time to time by Antaris. 

1.8. “Spacecraft Software” means those binary software images made available for download from the Antaris Platform for installation on satellites designed on the Antaris Platform and built by Customer.  

1.9. “Intellectual Property Rights” means all intellectual property rights or similar proprietary rights, including (a) patent rights and utility models, (b) copyrights and database rights, (c) trademarks, trade names, domain names and trade dress and the goodwill associated therewith, (d) trade secrets, (e) mask works, and (f) industrial design rights; in each case, including any registrations of, applications to register, and renewals and extensions of, any of the foregoing in any jurisdiction in the world. 

1.10. “Malicious Code” means viruses, worms, time bombs, Trojan horses and other harmful or malicious code, files, scripts, agents or programs. 

1.11. “Open Source Software” means open source, public source or freeware software made available under or otherwise subject to any license that (a) is considered an open source software license by the Open Source Initiative or a free software license by the Free Software Foundation, or any license substantially similar to any of the foregoing. 

1.12. “Project Agreement” means the Antaris ordering documents required for the purchase of Services and use of the Spacecraft Software and that are executed by the parties from time to time, including any mutually acceptable modifications, supplements, and addenda thereto. Project Agreements are incorporated herein.  

1.13. “Services” means the Antaris Platform and Support Services. 

1.14. “Subscription Term” means the period for which Customer is permitted to access and use the Antaris Platform. The applicable Subscription Term shall be set forth in a Project Agreement. 

1.15. “Support Services” means the support and maintenance services provided by Antaris to Antaris Platform subscribers, as further described in Customer’s Project Agreement (if applicable). 

2. PROJECT AGREEMENTS; LICENSES; RESTRICTIONS.   

2.1. Project Agreements.  Subject to the terms of this Agreement, Customer may order Services and Spacecraft Software by entering into one or more Project Agreements. Customer agrees that its purchases hereunder are neither contingent on the delivery of any future functionality or features nor dependent on any oral or written public comments made by Antaris regarding any future functionality or features 

2.2. Access and Use License.  Subject to Customer’s compliance with the terms and conditions contained in these Terms, Antaris, during the relevant Subscription Term, hereby grants Customer and, if applicable its Authorized Users, a limited, non-exclusive, non-transferable right to access and use the Antaris Platform in accordance with the Documentation in each case solely for Customer’s Authorized Purposes and not for the benefit of any other person or entity. Customer’s use of the Antaris Platform may be subject to certain limitations – for example, certain functionality of the Antaris Platform may be limited, as further described in the applicable Project Agreement.    

2.3. No License to Spacecraft Software.  For avoidance of doubt, the license set forth in Section 2.2 does not permit Customer to download, install or use Spacecraft Software. Customers license to use the Spacecraft Software, if any, will be as set forth in an appliable Project Agreement. 

2.4. Confirmed Clients.  If Customer desires to utilize the Antaris Platform to design, test and build satellites for a Confirmed Client, both Customer and the applicable Confirmed Client must have entered into Project Agreements for that specific satellite project. Once Antaris has confirmed both Project Agreements and all appliable fees have been paid by both Customer and the Confirmed Client, then, subject to Customer’s compliance with the terms and conditions contained in these Terms, Antaris, during the relevant Subscription Term, hereby grants Customer and, if applicable its Authorized Users, a limited, non-exclusive, non-transferable right to access and use the Antaris Platform in accordance with the Documentation for both Customer’s Authorized Purposes and for purposes of providing satellite design and testing services to the applicable Confirmed Client under the applicable Project Agreement. 

2.5. Restrictions.  Customer shall not, directly or indirectly, and Customer shall not permit any Authorized User or third party to:  (a) reverse engineer, decompile, disassemble or otherwise attempt to discover the object code, source code or underlying ideas or algorithms of the Antaris Platform or the Spacecraft Software; (b) modify, translate, or create derivative works based on any element of the Antaris Platform, the Spacecraft Software or any related Documentation; (c) rent, lease, distribute, sell, resell, assign, or otherwise transfer its rights to use the Antaris Platform or Spacecraft Software; (d) except as otherwise expressly permitted herein, use the Antaris Platform or Spacecraft Software for timesharing purposes or otherwise for the benefit of any person or entity other than for the benefit of Customer and Authorized Users; (e) remove any proprietary notices from the Documentation or Spacecraft Software; (f) use the Antaris Platform or Spacecraft Software for any purpose other than its intended purpose; (g) interfere with or disrupt the integrity or performance of the Antaris Platform; (h) introduce any Open Source Software into the Antaris Platform or Spacecraft Software; or (i) attempt to gain unauthorized access to the Antaris Platform, the Spacecraft Software, Antaris’ related systems or networks, or to the content and data uploaded by other users. 

2.6. Reservation of Rights.  Except as expressly granted in these Terms, there are no other licenses granted to Customer or any Authorized User, express, implied or by way of estoppel. All rights not granted in these Terms are reserved by Antaris. 

3. THIRD PARTY PRODUCTS AND HOSTING.   

3.1. Third Party Products.  Customer understands that the successful design and build of a satellite will require the procurement of hardware and software components not provided by Antaris (“Third-Party Products”). Customer shall procure such items solely at its cost and in a timely manner to avoid project delays. The Antaris Platform may permit Customer to incorporate certain Third-Party Products into Customer’s satellite design and may facilitate the purchase of such Third-Party Products by Customer. Any images of such Third-Party Products on the Antaris Platform are for illustrative purposes only. Although Antaris makes every effort to provide accurate information about such Third-Party Products, we cannot guarantee that the third-party provider has provided correct information to us or that it will not change the Third-Party Products without notice to us. Therefore, Customer understands and agrees that the Third-Party Products it receives may have different specifications from those displayed on the Antaris Platform. All Third-Party Products shown on the Platform are subject to availability and Antaris does not provide any guarantee of any Third-Party Product’s availability or performance.  

3.2. Third Party Hosting.  Antaris may use the services of one or more third parties to deliver all or part of the Antaris Platform.  Antaris will pass through any warranties to the extent that Antaris receives any from its then current third-party service provider that it can provide to Customer. Customer agrees to comply with any acceptable use policies and other terms of any third-party service provider that are provided or otherwise made available to Customer from time to time. 

4. ACCOUNTS AND PASSWORDS. 

4.1. Accounts.  Customer and all Authorized Users will be required to have an account with Antaris before being permitted to access and use the Antaris Platform. To create an account, the user must complete the registration process by providing Antaris with current, complete, and accurate information. All the information provided when registering for an account must be accurate, complete, and up to date. Users may change, correct, or remove their account information by logging into the account directly and making the desired changes. Antaris reserves the right to terminate any account for which the provided information is untrue, inaccurate, incomplete, or not current. 

4.2. Passwords.  Customer and its Authorized Users shall be responsible for maintaining the confidentiality of all user logins and passwords and for ensuring that each user login and password is used only by the person to which it was issued. Customer is solely responsible for any and all access and use of the Antaris Platform that occurs using any Authorized User’s account. Customer shall not share, and shall restrict its Authorized Users from sharing, passwords. Customer agrees to immediately notify Antaris of any unauthorized use of any account or login and password issued to Customer and/or its Authorized Users.  Antaris shall have no liability for any loss or damage arising from Customer’s or its Authorized Users failure to comply with the terms set forth in this Section. 

4.3. No Circumvention of Security.  Neither Customer nor any Authorized User may circumvent or otherwise interfere with any user authentication or security of the Antaris Platform. Customer will immediately notify Antaris of any breach, or attempted breach, of security known to Customer.   

5. CUSTOMER OBLIGATIONS. 

5.1. Customer System.  Customer is responsible for (a) obtaining, deploying and maintaining the Customer System; (b) contracting with third party ISP, telecommunications and other service providers to access and use the Antaris Platform via the Internet; and (c) paying all third party fees and access charges incurred in connection with the foregoing.  Except as specifically set forth in these Terms or a separate agreement between Customer and Antaris referencing these Terms, Antaris shall not be responsible for supplying any hardware, software or other equipment to Customer under these Terms. 

5.2. Acceptable Use.  Customer shall be solely responsible for its actions and the actions of its Authorized Users while using the Antaris Platform and Spacecraft Software.  Customer acknowledges and agrees: (a) to abide by all local, state, national, and international laws and regulations applicable to Customer’s use of the Antaris Platform and Spacecraft Software, including without limitation the provision and storage of Customer Data; (b) not to send or store data on or to the Antaris Platform which violates the rights of any individual or entity established in any jurisdiction; (c) not to upload in any way any information or content that contain Malicious Code or data that may damage the operation of the Antaris Platform or another's computer or mobile device; (d) not to use the Antaris Platform or Spacecraft Software for illegal, fraudulent, unethical or inappropriate purposes; (e) not to interfere or disrupt networks connected to the Antaris Platform or interfere with others’ ability to access or use the Antaris Platform; (f) not to distribute, promote or transmit through the Antaris Platform any unlawful, harmful, obscene, pornographic or otherwise objectionable material of any kind or nature; (g) not to transmit or post any material that encourages conduct that could constitute a criminal offense or give rise to civil liability; (h) to comply with all regulations, policies and procedures of networks connected to the Antaris Platform and Antaris’ service providers; and (i) to use the Antaris Platform and Spacecraft Software only in accordance with the Documentation.  Customer acknowledges and agrees that Antaris neither endorses any Customer communications or Customer Data, nor does Antaris assume any responsibility for any offensive material contained therein, any infringement of third party Intellectual Property Rights arising therefrom or any crime facilitated thereby.  Antaris may, but is not required to, remove any violating content posted or stored using the Antaris Platform or transmitted through the Antaris Platform, without notice to Customer.  Notwithstanding the foregoing, Antaris does not guarantee and is not obligated to verify, authenticate, monitor, or edit the Customer Data, or any other information or data input into or stored in the Antaris Platform for completeness, integrity, legality, quality, accuracy or otherwise.  Customer shall be responsible and liable for the completeness, integrity, legality, quality and accuracy of Customer Data and other information input into the Antaris Platform.  Customer shall be solely responsible for ensuring compliance with applicable laws and regulations in its use of the Antaris Platform.  

5.3. Accuracy of Customer’s Contact Information; Email Notices. Customer agrees to provide accurate, current, and complete information as necessary for Antaris to communicate with Customer from time to time regarding the Services, issue invoices or accept payment, or contact Customer for other account-related purposes. Customer agrees to keep any online account information current and inform Antaris of any changes in Customer’s legal business name, address, email address and phone number. Customer agrees to accept emails from Antaris at the e-mail addresses specified by it for login purposes. In addition, Customer agrees that Antaris may rely and act on all information and instructions provided to Antaris by Authorized Users from such e-mail addresses. 

5.4. Temporary Suspension.  Antaris may temporarily suspend Customer’s or its Authorized Users’ access to the Antaris Platform in the event that either Customer or any of its Authorized Users is engaged in, or Antaris in good faith suspects Customer or any of its Authorized Users is engaged in, any unauthorized conduct (including, but not limited to any violation of these Terms). Antaris will attempt to contact Customer prior to or contemporaneously with such suspension; provided, however, that Antaris’ exercise of the suspension rights herein shall not be conditioned upon Customer’s receipt of any notification. A suspension may take effect for Customer’s entire account and Customer understands that such suspension would therefore include its Authorized Users’ accounts. Customer agrees that Antaris shall not be liable to Customer, Authorized Users, or any third party if Antaris exercises its suspension rights as permitted by this Section. Upon determining that Customer has ceased the unauthorized conduct leading to the temporary suspension to Antaris’ reasonable satisfaction, Antaris shall reinstate Customer’s and its Authorized Users’ access to and use of the Antaris Platform. Notwithstanding anything in this Section to the contrary, Antaris’ suspension of access to the Antaris Platform is in addition to any other remedies that Antaris may have under these Terms or otherwise, including but not limited to termination of these Terms for cause. Additionally, if there are repeated incidences of suspension, regardless of the same or different cause and even if the cause or conduct is ultimately cured or corrected, Antaris may, in its reasonable discretion, determine that such circumstances, taken together, constitute a material breach. 

6. AVAILABILITY; SECURITY. 

6.1. Availability.  Subject to the terms and conditions of these Terms, Antaris will use commercially reasonable efforts to make the Antaris Platform available with minimal downtime 24 hours a day, 7 days a week; provided, however, that the following are excepted from availability commitments: (a) planned downtime, or (b) unavailability caused by circumstances beyond Antaris’ reasonable control, including without limitation, acts of God, acts of government, flood, fire, earthquakes, civil unrest, acts of terror, strikes or other labor problems or Internet service provider failures or delays. Antaris may make changes to the Antaris Platform and/or Spacecraft Software at any time and without notice to Customer. Certain enhancements to the Antaris Platform and Spacecraft Software made generally available at no cost to all users during the applicable Term will be made available to Customer at no additional charge.  However, the availability of some new enhancements to the Antaris Platform and Spacecraft Software may require the payment of additional fees, and Antaris will determine in its sole discretion whether access to any other such new enhancements will require an additional fee. These Terms will apply to, and the Antaris Platform and Spacecraft Software include, any enhancements, updates, upgrades and new modules to the Antaris Platform provided in connection therewith and subsequently provided by Antaris to Customer hereunder. 

6.2. Security; Privacy Policy.  Antaris will use commercially reasonable efforts to maintain appropriate administrative, physical, and technical safeguards for protection of the security, confidentiality and integrity of Customer Data in a in a manner consistent with what Antaris supplies generally to its other users.  Please review Antaris’ privacy policy, which is available on the Antaris Website (the “Privacy Policy”) and which further explains how Antaris collects and uses the Customer Data and other information that Antaris collects through users’ use of the Antaris Platform.  

7. FEES AND PAYMENT. 

7.1. Fees. Customer agrees to pay all applicable fees using one of the payment methods Antaris supports. Except as otherwise specified in these Terms, (a) fees are based on Services and software licenses purchased, regardless of actual usage, and (b) payment obligations are non-cancelable and fees paid are non-refundable.  Subscription fees are based on annual periods that begin on the Subscription Term start date and each anniversary thereof. All amounts payable under these Terms will be made without setoff or counterclaim, and without any deduction or withholding. 

7.2. Payment. Antaris will invoice customer for the amounts set forth in applicable Project Agreements and payment of such invoices is due upon the date set forth for such payment in the Project Agreement.  Customer agrees that Antaris may invoice Customer for any unpaid fees, including without limitation any amounts owed by Customer that cannot be processed.  Customer is responsible for providing complete and accurate billing and contact information to Antaris and notifying Antaris of any changes to such information. Customer agrees to pay all invoiced amounts within thirty (30) calendar days of the invoice date.   

7.3. AUTOMATIC RENEWAL. UNLESS CUSTOMER CANCELS SUCH SUBSCRIPTIONS AT LEAST THIRTY (30) DAYS PRIOR TO THE END OF THE THEN-CURRENT SUBSCRIPTION TERM, ANTARIS WILL AUTOMATICALLY RENEW SUBSCRIPTIONS FOR SERVICES ON THE FIRST BUSINESS DAY FOLLOWING THE END OF THE SUBSCRIPTION TERM AND INVOICE CUSTOMER FOR SUCH RENEWAL SUBSCRIPTION(S).  

7.4. CUSTOMER MAY CANCEL ITS SUBSCRIPTION BY PROVIDING NOTICE WITHING 30 DAYS OF THE END OF THE THEN CURRENT SUBSCRIPTION TERM. SUBSCRIPTION FEES ARE NOT REFUNDABLE.  IF CUSTOMER CANCELS ITS SUBSCRIPTION FEWER THAN THIRTY (30) DAYS PRIOR TO THE LAST DAY OF THE THEN-CURRENT SUBSCRIPTION TERM, THE SUBCRIPTION WILL AUTOMATICALLY RENEW AND CUSTOMER WILL NOT RECEIVE A REFUND, BUT WILL CONTINUE TO ENJOY ITS SUBSCRIPTION BENEFITS FOR THE REMAINDER OF THE SUBSCRIPTION(S) FOR WHICH IT HAS PAID. 

7.5. Overdue Charges.  If Antaris does not receive fees by the due date, then at Antaris’ discretion, (a) such charges may accrue late interest at the rate of 1.5% of the outstanding balance per month, or the maximum rate permitted by law, whichever is lower, from the date such payment was due until the date paid; and (b) Antaris may condition future purchases of Services on payment terms shorter than those specified in Section 8.2 (Payment). 

7.6. Suspension of Service. If any amounts owed by Customer for the Services are more than thirty (30) days overdue, Antaris may, without limiting Antaris’ other rights and remedies, suspend Customer’s and its Authorized Users’ access to the Antaris Platform until such amounts are paid in full; provided that Antaris agrees that it will not exercise its rights under this Section if the applicable charges are under reasonable and good-faith dispute and Customer is cooperating diligently to resolve the dispute. 

7.7. Taxes. The fees applicable to Customer’s and its Authorized Users’ use of the Antaris Platform are exclusive of all sales, use, value added, and other taxes or duties and Customer shall pay all such taxes (excluding taxes based on Antaris’ net income).  

8. REPRESENTATIONS AND WARRANTIES; DISCLAIMER. 

8.1. Mutual Representations and Warranties.  Each party represents, warrants, and covenants that: (a) it has the full power and authority to enter into these Terms and to perform its obligations hereunder; and (b) its acceptance of and performance under these Terms shall not breach any oral or written agreement with any third party or any obligation owed by it to any third party to keep any information or materials in confidence or in trust.  

8.2. Disclaimer.  EXCEPT FOR THE WARRANTIES SET FORTH IN THIS SECTION 9, THE ANTARIS PLATFORM, SPACECRAFT SOFTWARE AND SUPPORT SERVICES ARE PROVIDED ON AN AS-IS BASIS. CUSTOMER’S USE AND RECEIPT OF THE ANTARIS PLATFORM, SPACECRAFT SOFTWARE AND SUPPORT SERVICES IS AT ITS OWN RISK.  ANTARIS DOES NOT MAKE, AND HEREBY DISCLAIMS, ANY AND ALL OTHER EXPRESS, STATUTORY AND IMPLIED REPRESENTATIONS AND WARRANTIES, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT AND TITLE, QUALITY, SUITABILITY, OPERABILITY, CONDITION, SYSTEM INTEGRATION, NON-INTERFERENCE, WORKMANSHIP, TRUTH, ACCURACY (OF DATA OR ANY OTHER INFORMATION OR CONTENT), ABSENCE OF DEFECTS, WHETHER LATENT OR PATENT, AND ANY WARRANTIES ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.  THE EXPRESS WARRANTIES MADE BY ANTARIS IN SECTION 8 ARE FOR THE BENEFIT OF CUSTOMER ONLY AND NOT FOR THE BENEFIT OF ANY THIRD PARTY. ANY SOFTWARE PROVIDED THROUGH THE ANTARIS PLATFORM IS LICENSED AND NOT SOLD. 

ANY WARRANTY FOR THIRD-PARTY PRODUCTS WILL BE THE WARRANTY PROVIDED BY THE MANUFACTURER OF SUCH THIRD-PARTY PRODUCT DIRECTLY TO CUSTOMER.  ANTARIS DOES NOT MAKE, AND HEREBY DISCLAIMS, ANY AND ALL EXPRESS, STATUTORY AND IMPLIED REPRESENTATIONS AND WARRANTIES WITH RESPECT TO THE THIRD-PARTY PRODUCTS, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT AND TITLE, QUALITY, SUITABILITY, OPERABILITY, CONDITION, SYSTEM INTEGRATION, NON-INTERFERENCE, WORKMANSHIP, TRUTH, ACCURACY, ABSENCE OF DEFECTS, WHETHER LATENT OR PATENT, AND ANY WARRANTIES ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.   

NO AGENT OF ANTARIS IS AUTHORIZED TO ALTER OR EXPAND THE WARRANTIES OF ANTARIS AS SET FORTH HEREIN. ANTARIS DOES NOT WARRANT THAT: (A) THE USE OF THE ANTARIS PLATFORM OR SPACECRAFT SOFTWARE WILL BE SECURE, TIMELY, UNINTERRUPTED OR ERROR-FREE OR THAT IT WILL OPERATE IN COMBINATION WITH ANY OTHER HARDWARE, SOFTWARE, SYSTEM OR DATA; (B) THE SERVICES OR SPACECRAFT SOFTWARE WILL MEET CUSTOMER’S REQUIREMENTS OR EXPECTATIONS; (C) ANY STORED DATA WILL BE ACCURATE OR RELIABLE; (D) THE QUALITY OF ANY INFORMATION OR OTHER MATERIAL OBTAINED BY CUSTOMER THROUGH THE ANTARIS PLATFORM WILL MEET CUSTOMER’S REQUIREMENTS OR EXPECTATIONS; (E) THE SERVICES OR SPACECRAFT SOFTWARE WILL BE ERROR-FREE OR THAT ERRORS OR DEFECTS IN THE ANTARIS PLATFORM OR SPACECRAFT SOFTWARE WILL BE CORRECTED; OR (F) THE SERVER(S) THAT MAKE THE ANTARIS PLATFORM AVAILABLE ARE FREE OF VIRUSES OR OTHER HARMFUL COMPONENTS. THE SERVICES MAY BE SUBJECT TO LIMITATIONS, DELAYS, AND OTHER PROBLEMS INHERENT IN THE USE OF THE INTERNET AND ELECTRONIC COMMUNICATIONS. ANTARIS IS NOT RESPONSIBLE FOR ANY DELAYS, DELIVERY FAILURES, OR OTHER DAMAGES RESULTING FROM SUCH PROBLEMS. 

CUSTOMER ACCEPTS FULL RESPONSIBILITY FOR ANY AND ALL DECISIONS OR TRANSACTIONS (INCLUDING, WITHOUT LIMITATION, ANY PURCHASES) MADE BY CUSTOMER AND ITS AUTHORIZED USERS IN USING THE SERVICES.  CUSTOMER ACKNOWLEDGES AND AGREES THAT (A) USE OF THE SERVICES IS AT THE SOLE RISK OF CUSTOMER AND ITS AUTHORIZED USERS; (B) ANTARIS SHALL NOT BE RESPONSIBLE FOR ANY INTERRUPTION IN USE OF THE SERVICES, DELAYS OR ERRORS CAUSED BY CUSTOMER'S USE OF THE SERVICES, OR ANY PART THEREOF; (C) ANTARIS IS NOT THE MANUFACTURER OF ANY THIRD-PARTY PRODUCT AND CUSTOMER IS NOT RELYING ON ANTARIS TO PROVIDE ANY SATELLITE DESIGN ADVICE OR SERVICES; AND (D) ANTARIS SHALL NOT BE RESPONSIBLE FOR (i) MISREPRESENTATIONS OF ANY THIRD-PARTY PRODUCT MANUFACTURER OR (ii) THE FULFILLMENT OF ANY THIRD-PARTY PRODUCT ORDERS PLACED BY CUSTOMER, INCLUDING, WITHOUT LIMITATION, THE CANCELLATION OF ANY SUCH ORDERS AND/OR THE RETURN OR SERVICING OF ANY THIRD-PARTY PRODUCTS. CUSTOMER SHALL HOLD ANTARIS AND ITS DIRECTORS, MEMBERS, SHAREHOLDERS, OFFICERS, EMPLOYEES AND AGENTS HARMLESS FROM AND AGAINST ANY AND ALL CLAIMS, LOSSES, DAMAGES, LIABILITIES, COSTS AND/OR EXPENSES (INCLUDING REASONABLE LEGAL FEES) ARISING OUT OF CUSTOMER'S USE OF THE SERVICES. 

9. INDEMNIFICATION.  

9.1. Antaris Indemnity.   

9.1.a. General.  During the Term, Antaris, at its expense, shall defend Customer and its officers, directors and employees (the “Customer Indemnified Parties”) from and against all actions, proceedings, claims and demands by a third party (a “Third-Party Claim”) alleging that the Antaris Platform or Spacecraft Software infringes any copyright or misappropriates any trade secret and shall pay all damages, costs and expenses, including attorneys’ fees and costs (whether by settlement or award of by a final judicial judgment) paid to the third party bringing such Third-Party Claim.  Antaris’ obligations under this Section are conditioned upon (i) Antaris being promptly notified in writing of any Third-Party Claim under this Section, (ii) Antaris having the sole and exclusive right to control the defense and settlement of the Third-Party Claim, and (iii) Customer providing all reasonable assistance (at Antaris’ expense and reasonable request) in the defense of such Third-Party Claim.  In no event shall Antaris settle any such Third-Party Claim without Customer’s prior written approval.  Customer may, at its own expense, engage separate counsel to advise Customer regarding a Third-Party Claim and to participate in the defense of the Third-Party Claim, subject to Antaris’ right to control the defense and settlement. 

9.1.b. Mitigation.  If any claim which Antaris is obligated to defend has occurred, or in Antaris’ determination is likely to occur, Antaris may, in its sole discretion and at its option and expense (a) obtain for Customer the right to use the Antaris Platform and/or Spacecraft Software, (b) substitute a functionality equivalent, non-infringing replacement for the Antaris Platform and/or Spacecraft Software, (c) modify the Antaris Platform and/or Spacecraft Software to make it non-infringing and functionally equivalent, or (d) terminate these Terms and refund to Customer any prepaid amounts attributable the period of time between the date Customer was unable to use the Antaris Platform and/or Spacecraft Software due to such claim and the remaining days in the then-current Subscription Term. 

9.1.c. Exclusions.  Notwithstanding anything to the contrary in these Terms, the foregoing obligations shall not apply with respect to a claim of infringement if such claim arises out of (i) Customer’s use of infringing Customer Data; (ii) use of the Antaris Platform and/or Spacecraft Software in combination with any software, hardware, network or system not supplied by Antaris where the alleged infringement relates to such combination, (iii) any modification or alteration of the Antaris Platform and/or Spacecraft Software other than by Antaris, (iv) Customer’s continued use of the Antaris Platform and/or Spacecraft Software after Antaris notifies Customer to discontinue use because of an infringement claim, (v) Customer’s violation of applicable law; and/or (vi) the Customer System. 

9.1.d. Sole Remedy.  THE FOREGOING STATES THE ENTIRE LIABILITY OF ANTARIS WITH RESPECT TO THE INFRINGEMENT OF ANY INTELLECTUAL PROPERTY OR PROPRIETARY RIGHTS BY THE ANTARIS PLATFORM, SPACECRAFT SOFTWARE OR OTHERWISE, AND CUSTOMER HEREBY EXPRESSLY WAIVES ANY OTHER LIABILITIES OR OBLIGATIONS OF ANTARIS WITH RESPECT THERETO. 

9.2. Customer Indemnity.  Customer shall defend Antaris and its affiliates, licensors and their respective officers, directors and employees (“Antaris Indemnified Parties”)  from and against any and all actions, proceedings, claims and demands by a third party (each a “Third-Party Claim”) which arise out of or relate to: (a) a claim or threat that the Customer Data or Customer System (and the exercise by Antaris of the rights granted herein with respect thereto) infringes, misappropriates or violates any third party’s Intellectual Property Rights or privacy rights; (b) Customer’s use or alleged use of the Antaris Platform in violation of applicable law or other than as permitted under these Terms or (c) Customer’s use of any Third-Party Products. Customer shall pay all damages, costs and expenses, including attorneys’ fees and costs (whether by settlement or award of by a final judicial judgment) paid to the Third Party bringing any such Third-Party Claim. Customer’s obligations under this Section are conditioned upon (x) Customer being promptly notified in writing of any Third-Party Claim under this Section, (y) Customer having the sole and exclusive right to control the defense and settlement of the Third-Party Claim, and (z) Antaris providing all reasonable assistance (at Customer’s expense and reasonable request) in the defense of such Third-Party Claim. In no event shall Customer settle any such Third-Party Claim without Antaris’ prior written approval.  Antaris may, at its own expense, engage separate counsel to advise Antaris regarding a Third-Party Claim and to participate in the defense of the claim, subject to Customer’s right to control the defense and settlement. 

10. CONFIDENTIALITY.  

10.1. Confidential Information.  Each party (the “Receiving Party”) hereby understands and acknowledges that the other party (the “Disclosing Party”) has disclosed or may disclose business, technical or financial information relating to the Disclosing Party’s or its suppliers’ or Confirmed Clients’ business or products (hereinafter referred to as “Confidential Information” of the Disclosing Party). Confidential Information of Antaris shall include the Spacecraft Software any and all non-public information regarding features, functionality and performance of the Antaris Platform and the Third-Party Products. The Receiving Party agrees: (i) to take reasonable precautions to protect such Confidential Information, and (ii) not to use (except in performance of the Services or as otherwise permitted herein) or divulge to any third person any such Confidential Information. The Disclosing Party agrees that the foregoing shall not apply with respect to any information after five (5) years following the termination of this Agreement or any information that the Receiving Party can document (a) is or becomes generally available to the public; (b) was in its possession or known by it, prior to receipt from the Disclosing Party; (c) was rightfully disclosed to it without restriction by a third party; or (d) was independently developed without use of any Confidential Information of the Disclosing Party. Nothing in this Agreement shall prevent the Receiving Party from disclosing Confidential Information to the extent the Receiving Party is legally compelled to do so by any governmental investigative or judicial agency pursuant to proceedings over which such agency has jurisdiction; provided, however, that prior to any such disclosure, the Receiving Party shall (x) assert the confidential nature of the Confidential Information to the agency; (y) immediately notify the Disclosing Party in writing of the agency’s order or request to disclose; and (z) cooperate fully with the Disclosing Party in protecting against any such disclosure and in obtaining a protective order narrowing the scope of the compelled disclosure and protecting its confidentiality. 

10.2. Injunctive Relief.  The Parties agree that any unauthorized disclosure of Confidential Information may cause immediate and irreparable injury to the Disclosing Party and that, in the event of such breach, the Receiving Party will be entitled, in addition to any other available remedies, to seek immediate injunctive and other equitable relief, without bond and without the necessity of showing actual monetary damages. 

11. PROPRIETARY RIGHTS.  

11.1. Antaris Platform and Antaris Spacecraft Software.  As between Antaris and Customer, all right, title and interest in the Antaris Platform, the Spacecraft Software and any other Antaris materials furnished or made available hereunder, and all modifications and enhancements thereof, and all suggestions, ideas and feedback proposed by Customer regarding the Antaris Platform or Spacecraft Software, including all copyright rights, patent rights and other Intellectual Property Rights in each of the foregoing, belong to and are retained solely by Antaris or Antaris’ licensors and providers, as applicable. Customer hereby does and will irrevocably assign to Antaris all evaluations, ideas, feedback and suggestions made by Customer to Antaris regarding the Antaris Platform (collectively, “Feedback”) and all Intellectual Property Rights in the Feedback.   

11.2. Customer Data.  As between Antaris and Customer, all right, title and interest in the Customer Data, belongs to and is retained solely by Customer. By posting, displaying, sharing, or distributing Customer Data on or through the Antaris Platform, Customer hereby grants to Antaris a limited, sublicensable non-exclusive, royalty-free, worldwide license to reproduce, display, publicly perform, distribute, and otherwise use the Customer Data, and perform all acts with respect to the Customer Data as may be necessary for Antaris to provide the Services to Customer. Antaris may modify, copy, translate or make any derivative works of Customer Data in connection with its provision of the Antaris Platform as required to format such Customer Data for presentation within the Antaris Platform, to continually improve the Antaris Platform and to develop new services and offerings. 

11.3. Aggregated Statistics.  Notwithstanding anything else in these Terms or otherwise, Antaris may monitor Customer’s use of the Services and use Customer Data and other data and information related to such use, in an aggregate and anonymous manner, including to compile statistical and performance information related to Antaris Platform and its users (“Aggregated Statistics”). As between Antaris and Customer, all right, title and interest in the Aggregated Statistics and all Intellectual Property Rights therein, belong to and are retained solely by Antaris. Customer acknowledges that Antaris will be compiling Aggregated Statistics based on Customer Data and information input by other customers into the Antaris Platform and Customer agrees that Antaris may (a) make such Aggregated Statistics publicly available, and (b) use such information to the extent and in the manner required by applicable law or regulation and for purposes of data gathering, analysis, service enhancement and marketing, provided that such data and information does not identify Customer or its Confidential Information. 

12. LIMITATION OF LIABILITY. 

12.1. No Consequential Damages.  NEITHER ANTARIS NOR ITS LICENSORS OR SUPPLIERS SHALL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, OR ANY DAMAGES FOR LOST DATA, BUSINESS INTERRUPTION, LOST PROFITS, LOST REVENUE OR LOST BUSINESS, ARISING OUT OF OR IN CONNECTION WITH THESE TERMS, EVEN IF ANTARIS OR ITS LICENSORS OR SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, INCLUDING WITHOUT LIMITATION, ANY SUCH DAMAGES ARISING OUT OF THE LICENSING, PROVISION OR USE OF THE ANTARIS PLATFORM, ANCILLARY SERVICES, SUPPORT SERVICES AND/OR THE RESULTS THEREOF.  ANTARIS WILL NOT BE LIABLE FOR THE COST OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES. 

12.2. Limits on Liability.  NEITHER ANTARIS NOR ITS LICENSORS OR SUPPLIERS SHALL BE LIABLE FOR CUMULATIVE, AGGREGATE DAMAGES GREATER THAN AN AMOUNT EQUAL TO THE AMOUNTS PAID OR PAYABLE BY CUSTOMER TO ANTARIS UNDER THESE TERMS DURING THE PERIOD OF SIX (6) MONTHS PRECEDING THE DATE ON WHICH THE CLAIM FIRST ACCRUED. 

12.3. Essential Purpose.  CUSTOMER ACKNOWLEDGES THAT THE TERMS IN THIS SECTION 13 (LIMITATION OF LIABILITY) SHALL APPLY TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW AND SHALL APPLY EVEN IF AN EXCLUSIVE OR LIMITED REMEDY STATED HEREIN FAILS OF ITS ESSENTIAL PURPOSE WITHOUT REGARD TO WHETHER SUCH CLAIM IS BASED IN CONTRACT, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE. 

13. TERM AND TERMINATION.   

13.1. Term.  The term of these Terms commence upon the execution of an applicable Project Agreement and continues until the expiration or termination of all Subscription Term(s), unless earlier terminated as provided in these Terms or in an applicable separate agreement between Customer and Antaris referencing these Terms 

13.2. Termination for Cause.  A party may terminate these Terms upon written notice to the other party in the event the other party (a) files a petition for bankruptcy or has a petition for bankruptcy filed against it that is not dismissed within sixty (60) days after filing  or admits its inability to pay its debts as they mature, makes an assignment for the benefit of its creditors or ceases to function as a going concern or to conduct its operations in the normal course of business and such termination shall occur immediately upon notice; or (b) commits a material breach of any provision of these Terms and does not remedy such breach within thirty (30) days after receipt of notice from the other party or such other period as the parties may agree.  Antaris may terminate these Terms upon notice to Customer if the country in which Customer or an applicable Confirmed Client intends to use the Antaris Platform or Spacecraft Software becomes an Embargoed Country (as defined in Section 15.5), if Customer, an applicable Confirmed Client, or any of their Authorized Users is determined to be a Designated National (as defined in Section 15.5), or if, in Antaris’ determination, Customer, an applicable Confirmed Client, or any of their Authorized Users is otherwise no longer legally permitted to use the Antaris Platform and/or Spacecraft Software.  In no event shall any termination relieve Customer of the obligation to pay any fees payable to Antaris for the period prior to the effective date of termination. 

13.3. Effects of Termination.  Upon expiration or termination of these Terms, (a) Customer’s use of and access to the Antaris Platform and Antaris’ performance of all Support Services and Ancillary Services shall cease; (b) Customer and its Authorized Users shall cease all use of and destroy any copies of images shared by other users of the Antaris Platform that Customer has downloaded; and (c) all fees and other amounts owed to Antaris shall be immediately due and payable by Customer. Antaris shall have no obligation to maintain or provide any Customer Data and may thereafter, unless legally prohibited, delete or retain all Customer Data in its systems or otherwise in its possession or under its control. In addition, within ten (10) days of the effective date of termination each Receiving Party shall: (a) return to the Disclosing Party, or at the Disclosing Party’s option, the Receiving Party shall destroy, all items of Confidential Information (other than the Customer Data) then in the Receiving Party’s possession or control, including any copies, extracts or portions thereof, and (b) upon request shall certify in writing to Disclosing Party that it has complied with the foregoing.  

13.4. Survival.  This Section and Sections 1, 2.5, 2.6, 5.2, 8.2, 9, 10, 11, 12, 13.3, 14 and 15 shall survive any termination or expiration of these Terms.  

14. DISPUTES BETWEEN USERS; INTELLECTUAL PROPERTY INFRINGEMENT. 

14.1. No Agency or Partnership.  No agency, partnership, joint venture, or employment is created as a result of these Terms or Customer’s use of any part of the Antaris Platform. Customer does not have any authority whatsoever to bind Antaris in any respect. The parties agree that Antaris is a technology company whose primary business is providing a platform upon which users can design satellites and test virtual simulations of those satellites, and operate those satellites on orbit. Neither Antaris nor any users of the Antaris Platform may direct or control the day-to-day activities of the other, or create or assume any obligation on behalf of the other.   

14.2. Disputes Between Users. 

14.2.a. Customer’s interactions with individuals and/or organizations found on or through the Antaris Platform, including Customer’s decision to use Third-Party Products, materials, advice or other information provided by such individuals and/or organizations is Customer’s decision for which Customer alone is responsible. Customer understands and agrees that Antaris does not and cannot make representations as to the suitability of (i) any images, information and/or data Customer may access via the Antaris Platform; (ii) any individual or entity Customer may decide to interact with on or through the Antaris Platform and/or (iii) the accuracy or suitability of any advice, information, or recommendations made by any user. 

14.2.b. IF THERE IS A DISPUTE BETWEEN USERS OF THE ANTARIS PLATFORM, OR BETWEEN ANY USER OF THE ANTARIS PLATFORM AND ANY OTHER THIRD PARTY, CUSTOMER ACKNOWLEDGES AND AGREES THAT ANTARIS IS UNDER NO OBLIGATION TO BECOME INVOLVED. IN THE EVENT THAT A DISPUTE ARISES BETWEEN CUSTOMER AND ANY OTHER USER OR THIRD PARTY, CUSTOMER HEREBY RELEASES ANTARIS, ITS OFFICERS, MANAGERS, MEMBERS, DIRECTORS, EMPLOYEES, ATTORNEYS, AGENTS, AND SUCCESSORS IN RIGHTS FROM ANY CLAIMS, DEMANDS, AND DAMAGES (ACTUAL AND CONSEQUENTIAL) OF EVERY KIND OR NATURE, KNOWN OR UNKNOWN, SUSPECTED OR UNSUSPECTED, FORESEEABLE OR UNFORESEEABLE, DISCLOSED OR UNDISCLOSED, ARISING OUT OF OR IN ANY WAY RELATED TO SUCH DISPUTES. IF CUSTOMER IS A CALIFORNIA RESIDENT, CUSTOMER WAIVES CALIFORNIA CIVIL CODE §1542, WHICH SAYS: "A GENERAL RELEASE DOES NOT EXTEND TO CLAIMS THAT THE CREDITOR OR RELEASING PARTY DOES NOT KNOW OR SUSPECT TO EXIST IN HIS FAVOR AT THE TIME OF EXECUTING THE RELEASE, WHICH IF KNOWN BY HIM MUST HAVE MATERIALLY AFFECTED HIS SETTLEMENT WITH THE DEBTOR OR RELEASED PARTY." 

15. MISCELLANEOUS. 

15.1. Notices.  All notices which any party to these Terms may be required or may wish to give may be given by addressing them to the other party at the address set forth in the preamble to these Terms (as updated by the parties from time to time pursuant to this Section) by: (a) personal delivery, (b) sending such notices by commercial overnight courier with written verification of actual receipt, (c) by email, effective (A) when the sender receives an automated message from the recipient confirming delivery or (B) one hour after the time sent (as recorded on the device from which the sender sent the email) unless the sender receives an automated message that the email has not been delivered, whichever happens first, but if the delivery or receipt is on a day which is not a business day or is after 5:00 pm (addressee’s time) it is deemed to be received at 9:00 am on the following business day, or (d) sending them by registered or certified mail. If so mailed or otherwise delivered, such notices shall be deemed and presumed to have been given on the earlier of the date of actual receipt or three (3) days after mailing or authorized form of delivery. All communications and notices to be made or given pursuant to these Terms shall be in the English language. 

15.2. Governing Law and Venue.  These Terms and the rights and obligations of the parties to and under this agreement shall be governed by and construed under the laws of the United States and the State of California as applied to agreements entered into and to be performed in such State without giving effect to conflicts of laws rules or principles. The parties agree that the United Nations Convention on Contracts for the International Sale of Goods is specifically excluded from application to these Terms. The parties further agree to waive and opt-out of any application of the Uniform Computer Information Transactions Act (UCITA), or any version thereof, adopted by any state of the United States in any form.  Any dispute arising out of or in connection with these Terms, including but not limited to any question regarding its existence, interpretation, validity, performance, or termination, or any dispute between the parties arising from the parties' relationship created by these Terms, shall be referred to and finally resolved by arbitration administered by the American Arbitration Association under its rules. The number of arbitrators shall be one (1). The parties shall endeavor to agree upon the sole arbitrator and jointly nominate the arbitrator. If the parties cannot agree upon the sole arbitrator within a time prescribed by AAA, the parties shall request the AAA to propose five (5) arbitrators and each party shall rank the proposed arbitrators. The AAA shall appoint an arbitrator from the list of five (5), based upon the parties' rankings. The seat, or legal place of arbitration shall be Santa Clara County, California. Notwithstanding the foregoing, Antaris has the right to pursue equitable relief in the state and federal courts located California, and Customer agrees to the exclusive jurisdiction and venue of such courts. 

15.3. Publicity. Antaris has the right to reference and use Customer’s name and trademarks and disclose the nature of the Services provided hereunder in each case in Antaris business development and marketing efforts, including without limitation Antaris’ web site. 

15.4. U.S. Government Customers.  If Customer is a Federal Government entity, Supplier provides the Antaris Platform and Spacecraft Software, including related software and technology, for ultimate Federal Government end use solely in accordance with the following:  Government technical data rights include only those rights customarily provided to the public with a commercial item or process and Government software rights related to the Supplier Service and Spacecraft Software include only those rights customarily provided to the public, as defined in these Terms. The technical data rights and customary commercial software license is provided in accordance with FAR 12.211 (Technical Data) and FAR 12.212 (Software) and, for Department of Defense transactions, DFAR 252.227-7015 (Technical Data – Commercial Items) and DFAR 227.7202-3 (Rights in Commercial Computer Software or Computer Software Documentation). If greater rights are needed, a mutually acceptable written addendum specifically conveying such rights must be included in these Terms. 

15.5. Export.  The Antaris Platform and Spacecraft Software utilize software and technology that may be subject to United States and foreign export controls. Customer acknowledges and agrees that the Antaris Platform and Spacecraft Software shall not be used, and none of the underlying information, software, or technology may be transferred or otherwise exported or re-exported to countries as to which the United States maintains an embargo (collectively, “Embargoed Countries”), or to or by a national or resident thereof, or any person or entity on the U.S. Department of Treasury’s List of Specially Designated Nationals or the U.S. Department of Commerce’s Table of Denial Orders (collectively, “Designated Nationals”). The lists of Embargoed Countries and Designated Nationals are subject to change without notice. By using the Antaris Platform and/or Spacecraft Software, Customer represents and warrants that it is not located in, under the control of, or a national or resident of an Embargoed Country or Designated National. The Antaris Platform and/or Spacecraft Software may use encryption technology that is subject to licensing requirements under the U.S. Export Administration Regulations, 15 C.F.R. Parts 730-774 and Council Regulation (EC) No. 1334/2000. Customer agrees to comply strictly with all applicable export laws and assume sole responsibility for obtaining licenses to export or re-export as may be required. Antaris and its licensors make no representation that the Antaris Platform or Spacecraft Software is appropriate or available for use in other locations. No information acquired through the use of the Antaris Platform and/or Spacecraft Software, may be used by Customer or any Confirmed Client for nuclear activities, chemical or biological weapons, or missile projects. 

15.6. General.  Customer shall not assign its rights hereunder, or delegate the performance of any of its duties or obligations hereunder, whether by merger, acquisition, sale of assets, operation of law, or otherwise, without the prior written consent of Antaris. Any purported assignment in violation of the preceding sentence is null and void. Subject to the foregoing, these Terms shall be binding upon, and inure to the benefit of, the successors and assigns of the parties thereto. There are no third-party beneficiaries to these Terms. Except as otherwise specified in these Terms, these Terms may be amended or supplemented only by a writing that refers explicitly to these Terms and that is signed on behalf of both parties. No waiver will be implied from conduct or failure to enforce rights. No waiver will be effective unless in a writing signed on behalf of the party against whom the waiver is asserted. If any of these Terms is found invalid or unenforceable that term will be enforced to the maximum extent permitted by law and the remainder of the Terms will remain in full force. The parties are independent contractors, and nothing contained herein shall be construed as creating an agency, partnership, or other form of joint enterprise between the parties. These Terms constitute the entire agreement between the parties relating to this subject matter and supersedes all prior or simultaneous understandings, representations, discussions, negotiations, and agreements, whether written or oral. Except for Customer’s payment obligations hereunder, neither party shall be liable to the other party or any third party for failure or delay in performing its obligations under these Terms when such failure or delay is due to any cause beyond the control of the party concerned, including, without limitation, acts of God, governmental orders or restrictions, fire, or flood, provided that upon cessation of such events such party shall thereupon promptly perform or complete the performance of its obligations hereunder.

User Guide

This guide supports those directly working within the Antaris Cloud Platform (ACP) to develop and operate satellites. Please use this document to learn about core platform concepts and workflows.

If you have any questions or comments, please contact the Antaris support team via email at [email protected].

1. Glossary

Term

Meaning

ACP

Acronym for “Antaris Cloud Platform”

Design Studio

Section of ACP used to configure missions, satellites, and other resources

Tenant

Isolated space within ACP, typically scoped to a real world organization

User

Auth context used to represent a real person within ACP, scoped to a Tenant

Mission

Specific set of objectives for a satellite, including system scope and operational goals

Ground Station

Earth-based communications node that facilitates satellite operation

Satellite

Space vehicle that can be designed, tested, and operated within ACP

Bus

Set of satellite system components that support foundational operations, such as guidance, navigation, and power management

Bus Design

Template object in ACP representing a complete Bus and its individual components

Payload

Mission-specific device installed in a satellite along with its control software

SatOS™

Onboard software responsible for orchestrating satellite activities (i.e. the “operating system” of the satellite)

Task

Meaningful unit of work that a satellite may execute

Task Plan

Reusable template of satellite tasks, along with requirements such as geography and repetition

Scenario

Virtual sandbox constructed to test a satellite in a fully simulated space environment

HWIL

Acronym for "Hardware in the loop"

GSP

Acronym for "Ground Station Provider"

HUD

Acronym for "Heads-Up Display"

2. Satellite Design

This section describes the core satellite design process, which focuses primarily on satellite system architecture. Operational configuration and planning are addressed elsewhere.

2.1 Create a Satellite

From the DESIGN dashboard, simply click on the Create Satellite action. Give the Satellite a unique name and proceed on to the next step:

Proceed by entering a title for your satellite. Then, specify the satellite's orbital altitude and inclination

2.2 Configure Payloads

A satellite is defined primarily by the set of payloads intended to operate within it. This is critical input, as it defines the “load” to be supported by core satellite systems.

Selection of a payload category and subcategory allows ACP to provide more contextual filters that help identify the most appropriate Payload Device from the catalog.

If an appropriate Payload Device does not yet exist in the catalog, it may be defined using the “Add Payload Device” action:

By the end of this process, a summary of the load to be supported by the satellite will be presented in the form of “Size”, “Mass” and “Power” meters:

These requirements feed directly into the upcoming Bus Design selection process.

2.3 Configure Edge Devices

To configure an Edge Device, choose from the supported components, indicate an average amount of time per orbit it will be active, and choose a quantity of SSDs to attach to it:

2.4 Choose Bus Design

When arriving at this stage, you can select different bus vendors, and ACP will have gathered enough input about the satellite to recommend an appropriate Bus Design based on the selected vendors:

2.5 Configure 3D Model

To upload your own 3D model of the satellite, click on the 3D Model option. This will allow you to select and upload your model, replacing the current satellite 3D model with your custom version.

After making your selection, click “Save Satellite” and the Satellite is now ready to be used!

3. Satellite Designer

3.1 Control Mode Configuration

3.2 Payload and Sensor Configuration

The sensor analysis follows a similar workflow to payloads. Choose a sensor from the bus list, configure its properties and vector.

3.3 Analysis

3.4 Reports

4. Payload Development

The following diagram represents the high-level relationship between ACP and the elements operating outside of ACP:

The remainder of this section focuses on the ACP portion of the payload development process described above. It is vital that developers review the SatOS Payload Developer Guide before continuing.

4.1 Define Payload Sequence

4.2 Test Payload Sequence

Any data that is staged for downlink by the payload application is automatically downloaded into ACP for review:

Note that the remote payload application may be restarted while its running, which can help to quickly develop application software.

5. GeoFeatures

Users can draw a fence or link a target over a specific region. These are used when creating satellite task plans, which is discussed later in this document.

5.1 Creating a GeoFeature

Users can schedule payloads to the GeoFeatures, which will help in generating the satellite’s schedule.

6. Ground Communications

Users can identify which ground stations can support their mission through the "Ground Stations" section of the DESIGN dashboard.

6.1 Adding a GSP

6.2 Creating a Custom GSP with Ground Stations

Using the Map View and Direct Input feature users can create a Create a Custom GSP with Ground Stations

6.2.1 Creating Custom GSP via Map View

Creating GSPs through the Map View is a fast and efficient process, allowing users to quickly set up a provider and add ground stations with just a few essential details.

Once you have configured the custom GSP with all the required ground stations for your mission, simply click Save to complete the setup.

6.2.2 Creating Custom GSP via Direct Input

Using the Direct Input, allows users to define the GSP in a more granular way. This level of detail is helpful later when operating the satellite.

Once the GSP is added, you can assign individual ground stations to it.

6.3 Configuring Ground Stations within a GSP

6.4 MQTT Topic Configuration

7. Task Planning

7.1 Managing Tasks

Tasks must be defined before a Task Plan can be constructed. Navigate to DESIGN, choose a Satellite, click on Operations and then click on "Tasks":

Each Task represents a logical unit of work that can be scheduled. Each Task is defined by a single Payload Sequence, parametric overrides, and any relevant timing requirements.

7.2 Managing Task Plans

Task Plans are templates of prioritized Tasks that can be used to repeatedly generate schedules for a Satellite:

It is common to define multiple Task Plans for each Satellite, typically modeling the nominal operations as well as one or more alternate plans.

When creating Task Plan, you are constructing a prioritized set of Tasks and their respective scheduling requirements.

Tasks are created ahead of time, then added to a Task Plan with additional scheduling requirements.

Several controls are available to influence when a Payload Task may be executed. The following screenshot demonstrates a "Geofence" geo-trigger.

The "Geo-Trigger" options are described below in detail:

Use None when the task has no ground-based requirements.
Use the Target Track option to require the satellite point towards a specific location on the ground during Task execution. Locations are defined using WGS84 latitude and longitude (decimal degrees) along with an altitude (km). The minimum elevation will limit which ground passes are considered, ensuring that Tasks are only scheduled when the satellite maintains the required elevation above the horizon as measured from the target location.
The Geofence option limits Task execution to time periods when the satellite passes through some geographic area. A bounding box is used to define the area, represented by two WGS84 coordinates (the upper left and lower right points of the box).

The "Sun Exposure" defines lighting conditions under which the task should be executed:

The task with Sunlit will only be executed when the satellite is in sunlight (i.e., not in Earth's shadow). This is useful for operations that rely on solar power or require illumination for imaging
The task with Eclipse will only be executed when the satellite is in Earth's shadow (i.e., during orbital eclipse). This can be useful for observing celestial phenomena or reducing light interference.
The task with Both can be executed regardless of whether the satellite is sunlit or in eclipse.

The "Orbit Direction" defines which part of the satellite’s orbit the task should occur in:

The Ascending task will only be executed when the satellite is moving from the Southern Hemisphere to the Northern Hemisphere (i.e., increasing latitude).
The Descending task will only be executed when the satellite is moving from the Northern Hemisphere to the Southern Hemisphere (i.e., decreasing latitude).
The task with Both can be executed during either orbit direction.

In certain cases, an “Attitude Control Mode” must be selected:

The Ground Track mode causes the satellite to maintain a stable orientation with respect to the earth. This can be useful for payloads that scan the ground such as IoT receivers or push-broom imaging sensors.
The Sun Track mode allows the satellite to maintain a solar-oriented attitude during the Task. This can be useful for Tasks that are not sensitive to earth-relative orientation.

The "Satellite Orientation" defines how the satellite should be oriented during task execution:

The Nadir makes the satellite points directly down toward the Earth’s surface (toward the center of the Earth). This is ideal for most Earth observation tasks like imaging, mapping, or remote sensing
The Custom makes the satellite is oriented based on user-defined parameters, such as specific roll, pitch, and yaw angles. This is useful for specialized tasks like pointing at off-nadir targets

Use the “Frequency” controls to define the preferred number of times the Task should be scheduled within a given period of time.

8. Executing Scenarios

"SIMULATE" allows satellite developers and operators to explore a variety of real world scenarios and test how a given satellite will act.

8.1 Creating a Scenario

8.1.1 Operation - ConOps

8.1.2 On-Board Schedule

8.2 Operation - LEOP

LEOP supports the Satellite's detumbling simulation. Following this, configure the Initial Epoch and Keplerian Elements accurately, ensuring the simulation reflects real post-launch conditions.

Define the satellite’s initial attitude conditions with Orentation and Angular rates then proceed with a desired amount of simulated time

8.2.1 Prediction Analysis

8.2.1.1 ConOps

After generating the schedule from ConOps ACP performs Prediction Analysis for a quick simulation preview to help users validate and refine their schedule efficiently

8.2.1.2 LEOP

Once you are confident with the results of the prediction analysis, proceed to deploy the scenario.

8.3 Scenario Execution

8.3.1 HUD

Users can open multiple secondary windows using on-screen buttons. Each window can be dragged or pinned anywhere on the screen for ease of use.

Top Left: Includes a Home button to return to the previous screen. Users can switch between satellite groups and individual satellites within the group using dropdown menu. The Orbital Details section provides specific orbital parameters of the selected satellite.
Top Right: Contains 4 Quick Actions Panels: Onboard Schedule, Console, Telemetry, File Queue. Allowing full access to satellite operations directly from the HUD, ensuring operators can manage tasks efficiently in real time.

8.3.1.2 On-Board Schedule

Displays the detailed sequence of satellite events, including operations related to the Payload Server, Application, and Payload activity, followed by any changes in the ADCS control mode.

8.3.1.3 Console

Clicking on a message reveals more detailed information, including the undecoded hex data and the decoded JSON packet. These details help users analyze message behavior and system responses.

Message Colors:

Yellow : A successful tele-command that triggered a telemetry response from the satellite
Green : A telemetry response received in reply to a tele-command
Blue : Beacon telemetry not triggered by any tele-command
None : A tele-command that did not induce a detectable telemetry response by ACP

8.3.1.3.1 Commanding through the Console

Once a command is selected and configured, clicking "Execute" will send the command immediately. The corresponding telemetry related to the executed command will then be displayed to the user.

8.3.2 Plan

In addition to the HUD, the Plan and Monitor tabs, offers expanded details found in the Onboard Schedule, Ground Contacts, and Telemetry Displays.

The Plan tab contains two subtabs: Onboard Schedule and Ground Contacts.

8.3.3 Monitor

9. Mission Models

9.1 Active Model

9.1.1 Satellites

9.1.1.1 Creating Satellite

9.1.1.2 Creating Group

9.1.1.3 Creating TLE Track

9.1.2 Geofeatures

9.1.3 Ground Stations

9.2 Analysis

9.2.1 Coverage Analysis

9.2.2 Ground Contact Analysis

9.2.3 Propulsion Budget Analysis

9.3 Reports

Terms of Service

Last updated December 12, 2022

THESE TERMS OF SERVICE (THE "TERMS") ARE A LEGAL AGREEMENT BETWEEN YOU ("CUSTOMER") AND ANTARIS, INC. ("ANTARIS"). BY EXECUTING A PROJECT AGREEMENT (AS DEFINED BELOW) THAT INCLUDES THESE TERMS BY REFERENCE OR BY USING THE ANTARIS PLATFORM, CUSTOMER ACKNOWLEDGES THAT CUSTOMER HAS REVIEWED AND ACCEPTS THESE TERMS. IF YOU ARE AGREEING TO THESE TERMS AS AN INDIVIDUAL, “CUSTOMER” REFERS TO YOU INDIVIDUALLY.  IF YOU ARE AGREEING TO THESE TERMS AS A REPRESENTATIVE OF AN ENTITY, YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO BIND THAT ENTITY AND “CUSTOMER” REFERS TO THAT ENTITY.  IF CUSTOMER DOES NOT AGREE WITH ALL OF THESE TERMS, DO NOT ACCESS OR OTHERWISE USE THE ANTARIS PLATFORM.  

In consideration of the mutual promises and agreements set forth in these Terms, the parties agree as follows: 

1. DEFINITIONS. 

1.1. “Antaris Platform” means the Antaris satellite design and testing platform provided by Antaris; provided that such definition excludes the Spacecraft Software and any Open Source Software that may be used to provide such platform. 

1.2. “Authorized Purposes” means, unless otherwise permitted in an applicable Project Agreement, use of the Antaris Platform solely for Customer’s internal purposes in designing satellites and testing virtual simulations of such designs, and not for the provision of services to any third party. For avoidance of doubt, Authorized Purposes includes use of the Antaris Platform to demonstrate its capabilities to potential clients but not, unless otherwise permitted in an appliable Project Agreement, to provide services to such potential clients.  

1.3. “Authorized Users” means Customer’s employees, consultants, contractors, and/or agents: (a) who are authorized by Customer to access and use the Antaris Platform on Customer’s behalf, and (b) who have been supplied user identifications and passwords for such purpose by Customer (or by Antaris at Customer’s request). 

1.4. “Confirmed Client” means a third party with whom Customer has contracted to design and build one or more satellites (as set forth in an applicable Project Agreement) and with whom Antaris has entered into a written agreement to use the Antaris Platform and Spacecraft Software. Antaris must provide written confirmation that a Customer client is a Confirmed Client before Customer is permitted to use the Antaris Platform to provide services to such client. 

1.5. “Customer Data” means all Customer and Confirmed Client data submitted, stored, posted, displayed, or otherwise transmitted by or on behalf of Customer or its Authorized Users, and received and analyzed by the Antaris Platform. 

1.6. “Customer System” means Customer’s internal computers, servers and other equipment and software used to access and use the Antaris Platform. 

1.7. “Documentation” means the printed or electronic user instructions and help files made available by Antaris for use with the Antaris Platform, as may be updated from time to time by Antaris. 

1.8. “Spacecraft Software” means those binary software images made available for download from the Antaris Platform for installation on satellites designed on the Antaris Platform and built by Customer.  

1.9. “Intellectual Property Rights” means all intellectual property rights or similar proprietary rights, including (a) patent rights and utility models, (b) copyrights and database rights, (c) trademarks, trade names, domain names and trade dress and the goodwill associated therewith, (d) trade secrets, (e) mask works, and (f) industrial design rights; in each case, including any registrations of, applications to register, and renewals and extensions of, any of the foregoing in any jurisdiction in the world. 

1.10. “Malicious Code” means viruses, worms, time bombs, Trojan horses and other harmful or malicious code, files, scripts, agents or programs. 

1.11. “Open Source Software” means open source, public source or freeware software made available under or otherwise subject to any license that (a) is considered an open source software license by the Open Source Initiative or a free software license by the Free Software Foundation, or any license substantially similar to any of the foregoing. 

1.12. “Project Agreement” means the Antaris ordering documents required for the purchase of Services and use of the Spacecraft Software and that are executed by the parties from time to time, including any mutually acceptable modifications, supplements, and addenda thereto. Project Agreements are incorporated herein.  

1.13. “Services” means the Antaris Platform and Support Services. 

1.14. “Subscription Term” means the period for which Customer is permitted to access and use the Antaris Platform. The applicable Subscription Term shall be set forth in a Project Agreement. 

1.15. “Support Services” means the support and maintenance services provided by Antaris to Antaris Platform subscribers, as further described in Customer’s Project Agreement (if applicable). 

2. PROJECT AGREEMENTS; LICENSES; RESTRICTIONS.   

2.1. Project Agreements.  Subject to the terms of this Agreement, Customer may order Services and Spacecraft Software by entering into one or more Project Agreements. Customer agrees that its purchases hereunder are neither contingent on the delivery of any future functionality or features nor dependent on any oral or written public comments made by Antaris regarding any future functionality or features 

2.2. Access and Use License.  Subject to Customer’s compliance with the terms and conditions contained in these Terms, Antaris, during the relevant Subscription Term, hereby grants Customer and, if applicable its Authorized Users, a limited, non-exclusive, non-transferable right to access and use the Antaris Platform in accordance with the Documentation in each case solely for Customer’s Authorized Purposes and not for the benefit of any other person or entity. Customer’s use of the Antaris Platform may be subject to certain limitations – for example, certain functionality of the Antaris Platform may be limited, as further described in the applicable Project Agreement.    

2.3. No License to Spacecraft Software.  For avoidance of doubt, the license set forth in Section 2.2 does not permit Customer to download, install or use Spacecraft Software. Customers license to use the Spacecraft Software, if any, will be as set forth in an appliable Project Agreement. 

2.4. Confirmed Clients.  If Customer desires to utilize the Antaris Platform to design, test and build satellites for a Confirmed Client, both Customer and the applicable Confirmed Client must have entered into Project Agreements for that specific satellite project. Once Antaris has confirmed both Project Agreements and all appliable fees have been paid by both Customer and the Confirmed Client, then, subject to Customer’s compliance with the terms and conditions contained in these Terms, Antaris, during the relevant Subscription Term, hereby grants Customer and, if applicable its Authorized Users, a limited, non-exclusive, non-transferable right to access and use the Antaris Platform in accordance with the Documentation for both Customer’s Authorized Purposes and for purposes of providing satellite design and testing services to the applicable Confirmed Client under the applicable Project Agreement. 

2.5. Restrictions.  Customer shall not, directly or indirectly, and Customer shall not permit any Authorized User or third party to:  (a) reverse engineer, decompile, disassemble or otherwise attempt to discover the object code, source code or underlying ideas or algorithms of the Antaris Platform or the Spacecraft Software; (b) modify, translate, or create derivative works based on any element of the Antaris Platform, the Spacecraft Software or any related Documentation; (c) rent, lease, distribute, sell, resell, assign, or otherwise transfer its rights to use the Antaris Platform or Spacecraft Software; (d) except as otherwise expressly permitted herein, use the Antaris Platform or Spacecraft Software for timesharing purposes or otherwise for the benefit of any person or entity other than for the benefit of Customer and Authorized Users; (e) remove any proprietary notices from the Documentation or Spacecraft Software; (f) use the Antaris Platform or Spacecraft Software for any purpose other than its intended purpose; (g) interfere with or disrupt the integrity or performance of the Antaris Platform; (h) introduce any Open Source Software into the Antaris Platform or Spacecraft Software; or (i) attempt to gain unauthorized access to the Antaris Platform, the Spacecraft Software, Antaris’ related systems or networks, or to the content and data uploaded by other users. 

2.6. Reservation of Rights.  Except as expressly granted in these Terms, there are no other licenses granted to Customer or any Authorized User, express, implied or by way of estoppel. All rights not granted in these Terms are reserved by Antaris. 

3. THIRD PARTY PRODUCTS AND HOSTING.   

3.1. Third Party Products.  Customer understands that the successful design and build of a satellite will require the procurement of hardware and software components not provided by Antaris (“Third-Party Products”). Customer shall procure such items solely at its cost and in a timely manner to avoid project delays. The Antaris Platform may permit Customer to incorporate certain Third-Party Products into Customer’s satellite design and may facilitate the purchase of such Third-Party Products by Customer. Any images of such Third-Party Products on the Antaris Platform are for illustrative purposes only. Although Antaris makes every effort to provide accurate information about such Third-Party Products, we cannot guarantee that the third-party provider has provided correct information to us or that it will not change the Third-Party Products without notice to us. Therefore, Customer understands and agrees that the Third-Party Products it receives may have different specifications from those displayed on the Antaris Platform. All Third-Party Products shown on the Platform are subject to availability and Antaris does not provide any guarantee of any Third-Party Product’s availability or performance.  

3.2. Third Party Hosting.  Antaris may use the services of one or more third parties to deliver all or part of the Antaris Platform.  Antaris will pass through any warranties to the extent that Antaris receives any from its then current third-party service provider that it can provide to Customer. Customer agrees to comply with any acceptable use policies and other terms of any third-party service provider that are provided or otherwise made available to Customer from time to time. 

4. ACCOUNTS AND PASSWORDS. 

4.1. Accounts.  Customer and all Authorized Users will be required to have an account with Antaris before being permitted to access and use the Antaris Platform. To create an account, the user must complete the registration process by providing Antaris with current, complete, and accurate information. All the information provided when registering for an account must be accurate, complete, and up to date. Users may change, correct, or remove their account information by logging into the account directly and making the desired changes. Antaris reserves the right to terminate any account for which the provided information is untrue, inaccurate, incomplete, or not current. 

4.2. Passwords.  Customer and its Authorized Users shall be responsible for maintaining the confidentiality of all user logins and passwords and for ensuring that each user login and password is used only by the person to which it was issued. Customer is solely responsible for any and all access and use of the Antaris Platform that occurs using any Authorized User’s account. Customer shall not share, and shall restrict its Authorized Users from sharing, passwords. Customer agrees to immediately notify Antaris of any unauthorized use of any account or login and password issued to Customer and/or its Authorized Users.  Antaris shall have no liability for any loss or damage arising from Customer’s or its Authorized Users failure to comply with the terms set forth in this Section. 

4.3. No Circumvention of Security.  Neither Customer nor any Authorized User may circumvent or otherwise interfere with any user authentication or security of the Antaris Platform. Customer will immediately notify Antaris of any breach, or attempted breach, of security known to Customer.   

5. CUSTOMER OBLIGATIONS. 

5.1. Customer System.  Customer is responsible for (a) obtaining, deploying and maintaining the Customer System; (b) contracting with third party ISP, telecommunications and other service providers to access and use the Antaris Platform via the Internet; and (c) paying all third party fees and access charges incurred in connection with the foregoing.  Except as specifically set forth in these Terms or a separate agreement between Customer and Antaris referencing these Terms, Antaris shall not be responsible for supplying any hardware, software or other equipment to Customer under these Terms. 

5.2. Acceptable Use.  Customer shall be solely responsible for its actions and the actions of its Authorized Users while using the Antaris Platform and Spacecraft Software.  Customer acknowledges and agrees: (a) to abide by all local, state, national, and international laws and regulations applicable to Customer’s use of the Antaris Platform and Spacecraft Software, including without limitation the provision and storage of Customer Data; (b) not to send or store data on or to the Antaris Platform which violates the rights of any individual or entity established in any jurisdiction; (c) not to upload in any way any information or content that contain Malicious Code or data that may damage the operation of the Antaris Platform or another's computer or mobile device; (d) not to use the Antaris Platform or Spacecraft Software for illegal, fraudulent, unethical or inappropriate purposes; (e) not to interfere or disrupt networks connected to the Antaris Platform or interfere with others’ ability to access or use the Antaris Platform; (f) not to distribute, promote or transmit through the Antaris Platform any unlawful, harmful, obscene, pornographic or otherwise objectionable material of any kind or nature; (g) not to transmit or post any material that encourages conduct that could constitute a criminal offense or give rise to civil liability; (h) to comply with all regulations, policies and procedures of networks connected to the Antaris Platform and Antaris’ service providers; and (i) to use the Antaris Platform and Spacecraft Software only in accordance with the Documentation.  Customer acknowledges and agrees that Antaris neither endorses any Customer communications or Customer Data, nor does Antaris assume any responsibility for any offensive material contained therein, any infringement of third party Intellectual Property Rights arising therefrom or any crime facilitated thereby.  Antaris may, but is not required to, remove any violating content posted or stored using the Antaris Platform or transmitted through the Antaris Platform, without notice to Customer.  Notwithstanding the foregoing, Antaris does not guarantee and is not obligated to verify, authenticate, monitor, or edit the Customer Data, or any other information or data input into or stored in the Antaris Platform for completeness, integrity, legality, quality, accuracy or otherwise.  Customer shall be responsible and liable for the completeness, integrity, legality, quality and accuracy of Customer Data and other information input into the Antaris Platform.  Customer shall be solely responsible for ensuring compliance with applicable laws and regulations in its use of the Antaris Platform.  

5.3. Accuracy of Customer’s Contact Information; Email Notices. Customer agrees to provide accurate, current, and complete information as necessary for Antaris to communicate with Customer from time to time regarding the Services, issue invoices or accept payment, or contact Customer for other account-related purposes. Customer agrees to keep any online account information current and inform Antaris of any changes in Customer’s legal business name, address, email address and phone number. Customer agrees to accept emails from Antaris at the e-mail addresses specified by it for login purposes. In addition, Customer agrees that Antaris may rely and act on all information and instructions provided to Antaris by Authorized Users from such e-mail addresses. 

5.4. Temporary Suspension.  Antaris may temporarily suspend Customer’s or its Authorized Users’ access to the Antaris Platform in the event that either Customer or any of its Authorized Users is engaged in, or Antaris in good faith suspects Customer or any of its Authorized Users is engaged in, any unauthorized conduct (including, but not limited to any violation of these Terms). Antaris will attempt to contact Customer prior to or contemporaneously with such suspension; provided, however, that Antaris’ exercise of the suspension rights herein shall not be conditioned upon Customer’s receipt of any notification. A suspension may take effect for Customer’s entire account and Customer understands that such suspension would therefore include its Authorized Users’ accounts. Customer agrees that Antaris shall not be liable to Customer, Authorized Users, or any third party if Antaris exercises its suspension rights as permitted by this Section. Upon determining that Customer has ceased the unauthorized conduct leading to the temporary suspension to Antaris’ reasonable satisfaction, Antaris shall reinstate Customer’s and its Authorized Users’ access to and use of the Antaris Platform. Notwithstanding anything in this Section to the contrary, Antaris’ suspension of access to the Antaris Platform is in addition to any other remedies that Antaris may have under these Terms or otherwise, including but not limited to termination of these Terms for cause. Additionally, if there are repeated incidences of suspension, regardless of the same or different cause and even if the cause or conduct is ultimately cured or corrected, Antaris may, in its reasonable discretion, determine that such circumstances, taken together, constitute a material breach. 

6. AVAILABILITY; SECURITY. 

6.1. Availability.  Subject to the terms and conditions of these Terms, Antaris will use commercially reasonable efforts to make the Antaris Platform available with minimal downtime 24 hours a day, 7 days a week; provided, however, that the following are excepted from availability commitments: (a) planned downtime, or (b) unavailability caused by circumstances beyond Antaris’ reasonable control, including without limitation, acts of God, acts of government, flood, fire, earthquakes, civil unrest, acts of terror, strikes or other labor problems or Internet service provider failures or delays. Antaris may make changes to the Antaris Platform and/or Spacecraft Software at any time and without notice to Customer. Certain enhancements to the Antaris Platform and Spacecraft Software made generally available at no cost to all users during the applicable Term will be made available to Customer at no additional charge.  However, the availability of some new enhancements to the Antaris Platform and Spacecraft Software may require the payment of additional fees, and Antaris will determine in its sole discretion whether access to any other such new enhancements will require an additional fee. These Terms will apply to, and the Antaris Platform and Spacecraft Software include, any enhancements, updates, upgrades and new modules to the Antaris Platform provided in connection therewith and subsequently provided by Antaris to Customer hereunder. 

6.2. Security; Privacy Policy.  Antaris will use commercially reasonable efforts to maintain appropriate administrative, physical, and technical safeguards for protection of the security, confidentiality and integrity of Customer Data in a in a manner consistent with what Antaris supplies generally to its other users.  Please review Antaris’ privacy policy, which is available on the Antaris Website (the “Privacy Policy”) and which further explains how Antaris collects and uses the Customer Data and other information that Antaris collects through users’ use of the Antaris Platform.  

7. FEES AND PAYMENT. 

7.1. Fees. Customer agrees to pay all applicable fees using one of the payment methods Antaris supports. Except as otherwise specified in these Terms, (a) fees are based on Services and software licenses purchased, regardless of actual usage, and (b) payment obligations are non-cancelable and fees paid are non-refundable.  Subscription fees are based on annual periods that begin on the Subscription Term start date and each anniversary thereof. All amounts payable under these Terms will be made without setoff or counterclaim, and without any deduction or withholding. 

7.2. Payment. Antaris will invoice customer for the amounts set forth in applicable Project Agreements and payment of such invoices is due upon the date set forth for such payment in the Project Agreement.  Customer agrees that Antaris may invoice Customer for any unpaid fees, including without limitation any amounts owed by Customer that cannot be processed.  Customer is responsible for providing complete and accurate billing and contact information to Antaris and notifying Antaris of any changes to such information. Customer agrees to pay all invoiced amounts within thirty (30) calendar days of the invoice date.   

7.3. AUTOMATIC RENEWAL. UNLESS CUSTOMER CANCELS SUCH SUBSCRIPTIONS AT LEAST THIRTY (30) DAYS PRIOR TO THE END OF THE THEN-CURRENT SUBSCRIPTION TERM, ANTARIS WILL AUTOMATICALLY RENEW SUBSCRIPTIONS FOR SERVICES ON THE FIRST BUSINESS DAY FOLLOWING THE END OF THE SUBSCRIPTION TERM AND INVOICE CUSTOMER FOR SUCH RENEWAL SUBSCRIPTION(S).  

7.4. CUSTOMER MAY CANCEL ITS SUBSCRIPTION BY PROVIDING NOTICE WITHING 30 DAYS OF THE END OF THE THEN CURRENT SUBSCRIPTION TERM. SUBSCRIPTION FEES ARE NOT REFUNDABLE.  IF CUSTOMER CANCELS ITS SUBSCRIPTION FEWER THAN THIRTY (30) DAYS PRIOR TO THE LAST DAY OF THE THEN-CURRENT SUBSCRIPTION TERM, THE SUBCRIPTION WILL AUTOMATICALLY RENEW AND CUSTOMER WILL NOT RECEIVE A REFUND, BUT WILL CONTINUE TO ENJOY ITS SUBSCRIPTION BENEFITS FOR THE REMAINDER OF THE SUBSCRIPTION(S) FOR WHICH IT HAS PAID. 

7.5. Overdue Charges.  If Antaris does not receive fees by the due date, then at Antaris’ discretion, (a) such charges may accrue late interest at the rate of 1.5% of the outstanding balance per month, or the maximum rate permitted by law, whichever is lower, from the date such payment was due until the date paid; and (b) Antaris may condition future purchases of Services on payment terms shorter than those specified in Section 8.2 (Payment). 

7.6. Suspension of Service. If any amounts owed by Customer for the Services are more than thirty (30) days overdue, Antaris may, without limiting Antaris’ other rights and remedies, suspend Customer’s and its Authorized Users’ access to the Antaris Platform until such amounts are paid in full; provided that Antaris agrees that it will not exercise its rights under this Section if the applicable charges are under reasonable and good-faith dispute and Customer is cooperating diligently to resolve the dispute. 

7.7. Taxes. The fees applicable to Customer’s and its Authorized Users’ use of the Antaris Platform are exclusive of all sales, use, value added, and other taxes or duties and Customer shall pay all such taxes (excluding taxes based on Antaris’ net income).  

8. REPRESENTATIONS AND WARRANTIES; DISCLAIMER. 

8.1. Mutual Representations and Warranties.  Each party represents, warrants, and covenants that: (a) it has the full power and authority to enter into these Terms and to perform its obligations hereunder; and (b) its acceptance of and performance under these Terms shall not breach any oral or written agreement with any third party or any obligation owed by it to any third party to keep any information or materials in confidence or in trust.  

8.2. Disclaimer.  EXCEPT FOR THE WARRANTIES SET FORTH IN THIS SECTION 9, THE ANTARIS PLATFORM, SPACECRAFT SOFTWARE AND SUPPORT SERVICES ARE PROVIDED ON AN AS-IS BASIS. CUSTOMER’S USE AND RECEIPT OF THE ANTARIS PLATFORM, SPACECRAFT SOFTWARE AND SUPPORT SERVICES IS AT ITS OWN RISK.  ANTARIS DOES NOT MAKE, AND HEREBY DISCLAIMS, ANY AND ALL OTHER EXPRESS, STATUTORY AND IMPLIED REPRESENTATIONS AND WARRANTIES, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT AND TITLE, QUALITY, SUITABILITY, OPERABILITY, CONDITION, SYSTEM INTEGRATION, NON-INTERFERENCE, WORKMANSHIP, TRUTH, ACCURACY (OF DATA OR ANY OTHER INFORMATION OR CONTENT), ABSENCE OF DEFECTS, WHETHER LATENT OR PATENT, AND ANY WARRANTIES ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.  THE EXPRESS WARRANTIES MADE BY ANTARIS IN SECTION 8 ARE FOR THE BENEFIT OF CUSTOMER ONLY AND NOT FOR THE BENEFIT OF ANY THIRD PARTY. ANY SOFTWARE PROVIDED THROUGH THE ANTARIS PLATFORM IS LICENSED AND NOT SOLD. 

ANY WARRANTY FOR THIRD-PARTY PRODUCTS WILL BE THE WARRANTY PROVIDED BY THE MANUFACTURER OF SUCH THIRD-PARTY PRODUCT DIRECTLY TO CUSTOMER.  ANTARIS DOES NOT MAKE, AND HEREBY DISCLAIMS, ANY AND ALL EXPRESS, STATUTORY AND IMPLIED REPRESENTATIONS AND WARRANTIES WITH RESPECT TO THE THIRD-PARTY PRODUCTS, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT AND TITLE, QUALITY, SUITABILITY, OPERABILITY, CONDITION, SYSTEM INTEGRATION, NON-INTERFERENCE, WORKMANSHIP, TRUTH, ACCURACY, ABSENCE OF DEFECTS, WHETHER LATENT OR PATENT, AND ANY WARRANTIES ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.   

NO AGENT OF ANTARIS IS AUTHORIZED TO ALTER OR EXPAND THE WARRANTIES OF ANTARIS AS SET FORTH HEREIN. ANTARIS DOES NOT WARRANT THAT: (A) THE USE OF THE ANTARIS PLATFORM OR SPACECRAFT SOFTWARE WILL BE SECURE, TIMELY, UNINTERRUPTED OR ERROR-FREE OR THAT IT WILL OPERATE IN COMBINATION WITH ANY OTHER HARDWARE, SOFTWARE, SYSTEM OR DATA; (B) THE SERVICES OR SPACECRAFT SOFTWARE WILL MEET CUSTOMER’S REQUIREMENTS OR EXPECTATIONS; (C) ANY STORED DATA WILL BE ACCURATE OR RELIABLE; (D) THE QUALITY OF ANY INFORMATION OR OTHER MATERIAL OBTAINED BY CUSTOMER THROUGH THE ANTARIS PLATFORM WILL MEET CUSTOMER’S REQUIREMENTS OR EXPECTATIONS; (E) THE SERVICES OR SPACECRAFT SOFTWARE WILL BE ERROR-FREE OR THAT ERRORS OR DEFECTS IN THE ANTARIS PLATFORM OR SPACECRAFT SOFTWARE WILL BE CORRECTED; OR (F) THE SERVER(S) THAT MAKE THE ANTARIS PLATFORM AVAILABLE ARE FREE OF VIRUSES OR OTHER HARMFUL COMPONENTS. THE SERVICES MAY BE SUBJECT TO LIMITATIONS, DELAYS, AND OTHER PROBLEMS INHERENT IN THE USE OF THE INTERNET AND ELECTRONIC COMMUNICATIONS. ANTARIS IS NOT RESPONSIBLE FOR ANY DELAYS, DELIVERY FAILURES, OR OTHER DAMAGES RESULTING FROM SUCH PROBLEMS. 

CUSTOMER ACCEPTS FULL RESPONSIBILITY FOR ANY AND ALL DECISIONS OR TRANSACTIONS (INCLUDING, WITHOUT LIMITATION, ANY PURCHASES) MADE BY CUSTOMER AND ITS AUTHORIZED USERS IN USING THE SERVICES.  CUSTOMER ACKNOWLEDGES AND AGREES THAT (A) USE OF THE SERVICES IS AT THE SOLE RISK OF CUSTOMER AND ITS AUTHORIZED USERS; (B) ANTARIS SHALL NOT BE RESPONSIBLE FOR ANY INTERRUPTION IN USE OF THE SERVICES, DELAYS OR ERRORS CAUSED BY CUSTOMER'S USE OF THE SERVICES, OR ANY PART THEREOF; (C) ANTARIS IS NOT THE MANUFACTURER OF ANY THIRD-PARTY PRODUCT AND CUSTOMER IS NOT RELYING ON ANTARIS TO PROVIDE ANY SATELLITE DESIGN ADVICE OR SERVICES; AND (D) ANTARIS SHALL NOT BE RESPONSIBLE FOR (i) MISREPRESENTATIONS OF ANY THIRD-PARTY PRODUCT MANUFACTURER OR (ii) THE FULFILLMENT OF ANY THIRD-PARTY PRODUCT ORDERS PLACED BY CUSTOMER, INCLUDING, WITHOUT LIMITATION, THE CANCELLATION OF ANY SUCH ORDERS AND/OR THE RETURN OR SERVICING OF ANY THIRD-PARTY PRODUCTS. CUSTOMER SHALL HOLD ANTARIS AND ITS DIRECTORS, MEMBERS, SHAREHOLDERS, OFFICERS, EMPLOYEES AND AGENTS HARMLESS FROM AND AGAINST ANY AND ALL CLAIMS, LOSSES, DAMAGES, LIABILITIES, COSTS AND/OR EXPENSES (INCLUDING REASONABLE LEGAL FEES) ARISING OUT OF CUSTOMER'S USE OF THE SERVICES. 

9. INDEMNIFICATION.  

9.1. Antaris Indemnity.   

9.1.a. General.  During the Term, Antaris, at its expense, shall defend Customer and its officers, directors and employees (the “Customer Indemnified Parties”) from and against all actions, proceedings, claims and demands by a third party (a “Third-Party Claim”) alleging that the Antaris Platform or Spacecraft Software infringes any copyright or misappropriates any trade secret and shall pay all damages, costs and expenses, including attorneys’ fees and costs (whether by settlement or award of by a final judicial judgment) paid to the third party bringing such Third-Party Claim.  Antaris’ obligations under this Section are conditioned upon (i) Antaris being promptly notified in writing of any Third-Party Claim under this Section, (ii) Antaris having the sole and exclusive right to control the defense and settlement of the Third-Party Claim, and (iii) Customer providing all reasonable assistance (at Antaris’ expense and reasonable request) in the defense of such Third-Party Claim.  In no event shall Antaris settle any such Third-Party Claim without Customer’s prior written approval.  Customer may, at its own expense, engage separate counsel to advise Customer regarding a Third-Party Claim and to participate in the defense of the Third-Party Claim, subject to Antaris’ right to control the defense and settlement. 

9.1.b. Mitigation.  If any claim which Antaris is obligated to defend has occurred, or in Antaris’ determination is likely to occur, Antaris may, in its sole discretion and at its option and expense (a) obtain for Customer the right to use the Antaris Platform and/or Spacecraft Software, (b) substitute a functionality equivalent, non-infringing replacement for the Antaris Platform and/or Spacecraft Software, (c) modify the Antaris Platform and/or Spacecraft Software to make it non-infringing and functionally equivalent, or (d) terminate these Terms and refund to Customer any prepaid amounts attributable the period of time between the date Customer was unable to use the Antaris Platform and/or Spacecraft Software due to such claim and the remaining days in the then-current Subscription Term. 

9.1.c. Exclusions.  Notwithstanding anything to the contrary in these Terms, the foregoing obligations shall not apply with respect to a claim of infringement if such claim arises out of (i) Customer’s use of infringing Customer Data; (ii) use of the Antaris Platform and/or Spacecraft Software in combination with any software, hardware, network or system not supplied by Antaris where the alleged infringement relates to such combination, (iii) any modification or alteration of the Antaris Platform and/or Spacecraft Software other than by Antaris, (iv) Customer’s continued use of the Antaris Platform and/or Spacecraft Software after Antaris notifies Customer to discontinue use because of an infringement claim, (v) Customer’s violation of applicable law; and/or (vi) the Customer System. 

9.1.d. Sole Remedy.  THE FOREGOING STATES THE ENTIRE LIABILITY OF ANTARIS WITH RESPECT TO THE INFRINGEMENT OF ANY INTELLECTUAL PROPERTY OR PROPRIETARY RIGHTS BY THE ANTARIS PLATFORM, SPACECRAFT SOFTWARE OR OTHERWISE, AND CUSTOMER HEREBY EXPRESSLY WAIVES ANY OTHER LIABILITIES OR OBLIGATIONS OF ANTARIS WITH RESPECT THERETO. 

9.2. Customer Indemnity.  Customer shall defend Antaris and its affiliates, licensors and their respective officers, directors and employees (“Antaris Indemnified Parties”)  from and against any and all actions, proceedings, claims and demands by a third party (each a “Third-Party Claim”) which arise out of or relate to: (a) a claim or threat that the Customer Data or Customer System (and the exercise by Antaris of the rights granted herein with respect thereto) infringes, misappropriates or violates any third party’s Intellectual Property Rights or privacy rights; (b) Customer’s use or alleged use of the Antaris Platform in violation of applicable law or other than as permitted under these Terms or (c) Customer’s use of any Third-Party Products. Customer shall pay all damages, costs and expenses, including attorneys’ fees and costs (whether by settlement or award of by a final judicial judgment) paid to the Third Party bringing any such Third-Party Claim. Customer’s obligations under this Section are conditioned upon (x) Customer being promptly notified in writing of any Third-Party Claim under this Section, (y) Customer having the sole and exclusive right to control the defense and settlement of the Third-Party Claim, and (z) Antaris providing all reasonable assistance (at Customer’s expense and reasonable request) in the defense of such Third-Party Claim. In no event shall Customer settle any such Third-Party Claim without Antaris’ prior written approval.  Antaris may, at its own expense, engage separate counsel to advise Antaris regarding a Third-Party Claim and to participate in the defense of the claim, subject to Customer’s right to control the defense and settlement. 

10. CONFIDENTIALITY.  

10.1. Confidential Information.  Each party (the “Receiving Party”) hereby understands and acknowledges that the other party (the “Disclosing Party”) has disclosed or may disclose business, technical or financial information relating to the Disclosing Party’s or its suppliers’ or Confirmed Clients’ business or products (hereinafter referred to as “Confidential Information” of the Disclosing Party). Confidential Information of Antaris shall include the Spacecraft Software any and all non-public information regarding features, functionality and performance of the Antaris Platform and the Third-Party Products. The Receiving Party agrees: (i) to take reasonable precautions to protect such Confidential Information, and (ii) not to use (except in performance of the Services or as otherwise permitted herein) or divulge to any third person any such Confidential Information. The Disclosing Party agrees that the foregoing shall not apply with respect to any information after five (5) years following the termination of this Agreement or any information that the Receiving Party can document (a) is or becomes generally available to the public; (b) was in its possession or known by it, prior to receipt from the Disclosing Party; (c) was rightfully disclosed to it without restriction by a third party; or (d) was independently developed without use of any Confidential Information of the Disclosing Party. Nothing in this Agreement shall prevent the Receiving Party from disclosing Confidential Information to the extent the Receiving Party is legally compelled to do so by any governmental investigative or judicial agency pursuant to proceedings over which such agency has jurisdiction; provided, however, that prior to any such disclosure, the Receiving Party shall (x) assert the confidential nature of the Confidential Information to the agency; (y) immediately notify the Disclosing Party in writing of the agency’s order or request to disclose; and (z) cooperate fully with the Disclosing Party in protecting against any such disclosure and in obtaining a protective order narrowing the scope of the compelled disclosure and protecting its confidentiality. 

10.2. Injunctive Relief.  The Parties agree that any unauthorized disclosure of Confidential Information may cause immediate and irreparable injury to the Disclosing Party and that, in the event of such breach, the Receiving Party will be entitled, in addition to any other available remedies, to seek immediate injunctive and other equitable relief, without bond and without the necessity of showing actual monetary damages. 

11. PROPRIETARY RIGHTS.  

11.1. Antaris Platform and Antaris Spacecraft Software.  As between Antaris and Customer, all right, title and interest in the Antaris Platform, the Spacecraft Software and any other Antaris materials furnished or made available hereunder, and all modifications and enhancements thereof, and all suggestions, ideas and feedback proposed by Customer regarding the Antaris Platform or Spacecraft Software, including all copyright rights, patent rights and other Intellectual Property Rights in each of the foregoing, belong to and are retained solely by Antaris or Antaris’ licensors and providers, as applicable. Customer hereby does and will irrevocably assign to Antaris all evaluations, ideas, feedback and suggestions made by Customer to Antaris regarding the Antaris Platform (collectively, “Feedback”) and all Intellectual Property Rights in the Feedback.   

11.2. Customer Data.  As between Antaris and Customer, all right, title and interest in the Customer Data, belongs to and is retained solely by Customer. By posting, displaying, sharing, or distributing Customer Data on or through the Antaris Platform, Customer hereby grants to Antaris a limited, sublicensable non-exclusive, royalty-free, worldwide license to reproduce, display, publicly perform, distribute, and otherwise use the Customer Data, and perform all acts with respect to the Customer Data as may be necessary for Antaris to provide the Services to Customer. Antaris may modify, copy, translate or make any derivative works of Customer Data in connection with its provision of the Antaris Platform as required to format such Customer Data for presentation within the Antaris Platform, to continually improve the Antaris Platform and to develop new services and offerings. 

11.3. Aggregated Statistics.  Notwithstanding anything else in these Terms or otherwise, Antaris may monitor Customer’s use of the Services and use Customer Data and other data and information related to such use, in an aggregate and anonymous manner, including to compile statistical and performance information related to Antaris Platform and its users (“Aggregated Statistics”). As between Antaris and Customer, all right, title and interest in the Aggregated Statistics and all Intellectual Property Rights therein, belong to and are retained solely by Antaris. Customer acknowledges that Antaris will be compiling Aggregated Statistics based on Customer Data and information input by other customers into the Antaris Platform and Customer agrees that Antaris may (a) make such Aggregated Statistics publicly available, and (b) use such information to the extent and in the manner required by applicable law or regulation and for purposes of data gathering, analysis, service enhancement and marketing, provided that such data and information does not identify Customer or its Confidential Information. 

12. LIMITATION OF LIABILITY. 

12.1. No Consequential Damages.  NEITHER ANTARIS NOR ITS LICENSORS OR SUPPLIERS SHALL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, OR ANY DAMAGES FOR LOST DATA, BUSINESS INTERRUPTION, LOST PROFITS, LOST REVENUE OR LOST BUSINESS, ARISING OUT OF OR IN CONNECTION WITH THESE TERMS, EVEN IF ANTARIS OR ITS LICENSORS OR SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, INCLUDING WITHOUT LIMITATION, ANY SUCH DAMAGES ARISING OUT OF THE LICENSING, PROVISION OR USE OF THE ANTARIS PLATFORM, ANCILLARY SERVICES, SUPPORT SERVICES AND/OR THE RESULTS THEREOF.  ANTARIS WILL NOT BE LIABLE FOR THE COST OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES. 

12.2. Limits on Liability.  NEITHER ANTARIS NOR ITS LICENSORS OR SUPPLIERS SHALL BE LIABLE FOR CUMULATIVE, AGGREGATE DAMAGES GREATER THAN AN AMOUNT EQUAL TO THE AMOUNTS PAID OR PAYABLE BY CUSTOMER TO ANTARIS UNDER THESE TERMS DURING THE PERIOD OF SIX (6) MONTHS PRECEDING THE DATE ON WHICH THE CLAIM FIRST ACCRUED. 

12.3. Essential Purpose.  CUSTOMER ACKNOWLEDGES THAT THE TERMS IN THIS SECTION 13 (LIMITATION OF LIABILITY) SHALL APPLY TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW AND SHALL APPLY EVEN IF AN EXCLUSIVE OR LIMITED REMEDY STATED HEREIN FAILS OF ITS ESSENTIAL PURPOSE WITHOUT REGARD TO WHETHER SUCH CLAIM IS BASED IN CONTRACT, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE. 

13. TERM AND TERMINATION.   

13.1. Term.  The term of these Terms commence upon the execution of an applicable Project Agreement and continues until the expiration or termination of all Subscription Term(s), unless earlier terminated as provided in these Terms or in an applicable separate agreement between Customer and Antaris referencing these Terms 

13.2. Termination for Cause.  A party may terminate these Terms upon written notice to the other party in the event the other party (a) files a petition for bankruptcy or has a petition for bankruptcy filed against it that is not dismissed within sixty (60) days after filing  or admits its inability to pay its debts as they mature, makes an assignment for the benefit of its creditors or ceases to function as a going concern or to conduct its operations in the normal course of business and such termination shall occur immediately upon notice; or (b) commits a material breach of any provision of these Terms and does not remedy such breach within thirty (30) days after receipt of notice from the other party or such other period as the parties may agree.  Antaris may terminate these Terms upon notice to Customer if the country in which Customer or an applicable Confirmed Client intends to use the Antaris Platform or Spacecraft Software becomes an Embargoed Country (as defined in Section 15.5), if Customer, an applicable Confirmed Client, or any of their Authorized Users is determined to be a Designated National (as defined in Section 15.5), or if, in Antaris’ determination, Customer, an applicable Confirmed Client, or any of their Authorized Users is otherwise no longer legally permitted to use the Antaris Platform and/or Spacecraft Software.  In no event shall any termination relieve Customer of the obligation to pay any fees payable to Antaris for the period prior to the effective date of termination. 

13.3. Effects of Termination.  Upon expiration or termination of these Terms, (a) Customer’s use of and access to the Antaris Platform and Antaris’ performance of all Support Services and Ancillary Services shall cease; (b) Customer and its Authorized Users shall cease all use of and destroy any copies of images shared by other users of the Antaris Platform that Customer has downloaded; and (c) all fees and other amounts owed to Antaris shall be immediately due and payable by Customer. Antaris shall have no obligation to maintain or provide any Customer Data and may thereafter, unless legally prohibited, delete or retain all Customer Data in its systems or otherwise in its possession or under its control. In addition, within ten (10) days of the effective date of termination each Receiving Party shall: (a) return to the Disclosing Party, or at the Disclosing Party’s option, the Receiving Party shall destroy, all items of Confidential Information (other than the Customer Data) then in the Receiving Party’s possession or control, including any copies, extracts or portions thereof, and (b) upon request shall certify in writing to Disclosing Party that it has complied with the foregoing.  

13.4. Survival.  This Section and Sections 1, 2.5, 2.6, 5.2, 8.2, 9, 10, 11, 12, 13.3, 14 and 15 shall survive any termination or expiration of these Terms.  

14. DISPUTES BETWEEN USERS; INTELLECTUAL PROPERTY INFRINGEMENT. 

14.1. No Agency or Partnership.  No agency, partnership, joint venture, or employment is created as a result of these Terms or Customer’s use of any part of the Antaris Platform. Customer does not have any authority whatsoever to bind Antaris in any respect. The parties agree that Antaris is a technology company whose primary business is providing a platform upon which users can design satellites and test virtual simulations of those satellites, and operate those satellites on orbit. Neither Antaris nor any users of the Antaris Platform may direct or control the day-to-day activities of the other, or create or assume any obligation on behalf of the other.   

14.2. Disputes Between Users. 

14.2.a. Customer’s interactions with individuals and/or organizations found on or through the Antaris Platform, including Customer’s decision to use Third-Party Products, materials, advice or other information provided by such individuals and/or organizations is Customer’s decision for which Customer alone is responsible. Customer understands and agrees that Antaris does not and cannot make representations as to the suitability of (i) any images, information and/or data Customer may access via the Antaris Platform; (ii) any individual or entity Customer may decide to interact with on or through the Antaris Platform and/or (iii) the accuracy or suitability of any advice, information, or recommendations made by any user. 

14.2.b. IF THERE IS A DISPUTE BETWEEN USERS OF THE ANTARIS PLATFORM, OR BETWEEN ANY USER OF THE ANTARIS PLATFORM AND ANY OTHER THIRD PARTY, CUSTOMER ACKNOWLEDGES AND AGREES THAT ANTARIS IS UNDER NO OBLIGATION TO BECOME INVOLVED. IN THE EVENT THAT A DISPUTE ARISES BETWEEN CUSTOMER AND ANY OTHER USER OR THIRD PARTY, CUSTOMER HEREBY RELEASES ANTARIS, ITS OFFICERS, MANAGERS, MEMBERS, DIRECTORS, EMPLOYEES, ATTORNEYS, AGENTS, AND SUCCESSORS IN RIGHTS FROM ANY CLAIMS, DEMANDS, AND DAMAGES (ACTUAL AND CONSEQUENTIAL) OF EVERY KIND OR NATURE, KNOWN OR UNKNOWN, SUSPECTED OR UNSUSPECTED, FORESEEABLE OR UNFORESEEABLE, DISCLOSED OR UNDISCLOSED, ARISING OUT OF OR IN ANY WAY RELATED TO SUCH DISPUTES. IF CUSTOMER IS A CALIFORNIA RESIDENT, CUSTOMER WAIVES CALIFORNIA CIVIL CODE §1542, WHICH SAYS: "A GENERAL RELEASE DOES NOT EXTEND TO CLAIMS THAT THE CREDITOR OR RELEASING PARTY DOES NOT KNOW OR SUSPECT TO EXIST IN HIS FAVOR AT THE TIME OF EXECUTING THE RELEASE, WHICH IF KNOWN BY HIM MUST HAVE MATERIALLY AFFECTED HIS SETTLEMENT WITH THE DEBTOR OR RELEASED PARTY." 

15. MISCELLANEOUS. 

15.1. Notices.  All notices which any party to these Terms may be required or may wish to give may be given by addressing them to the other party at the address set forth in the preamble to these Terms (as updated by the parties from time to time pursuant to this Section) by: (a) personal delivery, (b) sending such notices by commercial overnight courier with written verification of actual receipt, (c) by email, effective (A) when the sender receives an automated message from the recipient confirming delivery or (B) one hour after the time sent (as recorded on the device from which the sender sent the email) unless the sender receives an automated message that the email has not been delivered, whichever happens first, but if the delivery or receipt is on a day which is not a business day or is after 5:00 pm (addressee’s time) it is deemed to be received at 9:00 am on the following business day, or (d) sending them by registered or certified mail. If so mailed or otherwise delivered, such notices shall be deemed and presumed to have been given on the earlier of the date of actual receipt or three (3) days after mailing or authorized form of delivery. All communications and notices to be made or given pursuant to these Terms shall be in the English language. 

15.2. Governing Law and Venue.  These Terms and the rights and obligations of the parties to and under this agreement shall be governed by and construed under the laws of the United States and the State of California as applied to agreements entered into and to be performed in such State without giving effect to conflicts of laws rules or principles. The parties agree that the United Nations Convention on Contracts for the International Sale of Goods is specifically excluded from application to these Terms. The parties further agree to waive and opt-out of any application of the Uniform Computer Information Transactions Act (UCITA), or any version thereof, adopted by any state of the United States in any form.  Any dispute arising out of or in connection with these Terms, including but not limited to any question regarding its existence, interpretation, validity, performance, or termination, or any dispute between the parties arising from the parties' relationship created by these Terms, shall be referred to and finally resolved by arbitration administered by the American Arbitration Association under its rules. The number of arbitrators shall be one (1). The parties shall endeavor to agree upon the sole arbitrator and jointly nominate the arbitrator. If the parties cannot agree upon the sole arbitrator within a time prescribed by AAA, the parties shall request the AAA to propose five (5) arbitrators and each party shall rank the proposed arbitrators. The AAA shall appoint an arbitrator from the list of five (5), based upon the parties' rankings. The seat, or legal place of arbitration shall be Santa Clara County, California. Notwithstanding the foregoing, Antaris has the right to pursue equitable relief in the state and federal courts located California, and Customer agrees to the exclusive jurisdiction and venue of such courts. 

15.3. Publicity. Antaris has the right to reference and use Customer’s name and trademarks and disclose the nature of the Services provided hereunder in each case in Antaris business development and marketing efforts, including without limitation Antaris’ web site. 

15.4. U.S. Government Customers.  If Customer is a Federal Government entity, Supplier provides the Antaris Platform and Spacecraft Software, including related software and technology, for ultimate Federal Government end use solely in accordance with the following:  Government technical data rights include only those rights customarily provided to the public with a commercial item or process and Government software rights related to the Supplier Service and Spacecraft Software include only those rights customarily provided to the public, as defined in these Terms. The technical data rights and customary commercial software license is provided in accordance with FAR 12.211 (Technical Data) and FAR 12.212 (Software) and, for Department of Defense transactions, DFAR 252.227-7015 (Technical Data – Commercial Items) and DFAR 227.7202-3 (Rights in Commercial Computer Software or Computer Software Documentation). If greater rights are needed, a mutually acceptable written addendum specifically conveying such rights must be included in these Terms. 

15.5. Export.  The Antaris Platform and Spacecraft Software utilize software and technology that may be subject to United States and foreign export controls. Customer acknowledges and agrees that the Antaris Platform and Spacecraft Software shall not be used, and none of the underlying information, software, or technology may be transferred or otherwise exported or re-exported to countries as to which the United States maintains an embargo (collectively, “Embargoed Countries”), or to or by a national or resident thereof, or any person or entity on the U.S. Department of Treasury’s List of Specially Designated Nationals or the U.S. Department of Commerce’s Table of Denial Orders (collectively, “Designated Nationals”). The lists of Embargoed Countries and Designated Nationals are subject to change without notice. By using the Antaris Platform and/or Spacecraft Software, Customer represents and warrants that it is not located in, under the control of, or a national or resident of an Embargoed Country or Designated National. The Antaris Platform and/or Spacecraft Software may use encryption technology that is subject to licensing requirements under the U.S. Export Administration Regulations, 15 C.F.R. Parts 730-774 and Council Regulation (EC) No. 1334/2000. Customer agrees to comply strictly with all applicable export laws and assume sole responsibility for obtaining licenses to export or re-export as may be required. Antaris and its licensors make no representation that the Antaris Platform or Spacecraft Software is appropriate or available for use in other locations. No information acquired through the use of the Antaris Platform and/or Spacecraft Software, may be used by Customer or any Confirmed Client for nuclear activities, chemical or biological weapons, or missile projects. 

15.6. General.  Customer shall not assign its rights hereunder, or delegate the performance of any of its duties or obligations hereunder, whether by merger, acquisition, sale of assets, operation of law, or otherwise, without the prior written consent of Antaris. Any purported assignment in violation of the preceding sentence is null and void. Subject to the foregoing, these Terms shall be binding upon, and inure to the benefit of, the successors and assigns of the parties thereto. There are no third-party beneficiaries to these Terms. Except as otherwise specified in these Terms, these Terms may be amended or supplemented only by a writing that refers explicitly to these Terms and that is signed on behalf of both parties. No waiver will be implied from conduct or failure to enforce rights. No waiver will be effective unless in a writing signed on behalf of the party against whom the waiver is asserted. If any of these Terms is found invalid or unenforceable that term will be enforced to the maximum extent permitted by law and the remainder of the Terms will remain in full force. The parties are independent contractors, and nothing contained herein shall be construed as creating an agency, partnership, or other form of joint enterprise between the parties. These Terms constitute the entire agreement between the parties relating to this subject matter and supersedes all prior or simultaneous understandings, representations, discussions, negotiations, and agreements, whether written or oral. Except for Customer’s payment obligations hereunder, neither party shall be liable to the other party or any third party for failure or delay in performing its obligations under these Terms when such failure or delay is due to any cause beyond the control of the party concerned, including, without limitation, acts of God, governmental orders or restrictions, fire, or flood, provided that upon cessation of such events such party shall thereupon promptly perform or complete the performance of its obligations hereunder.