Read
Reviews the mission.
- Home
- Solutions
- Sovereign
SOV Sovereign plan
Your mission never leaves the building
Sovereign is built to run on your own servers; deployments are scoped with each customer. Your mission data never comes to Arksa: only licence, reference-data and update checks reach Arksa, and none of them can carry mission content.
- Annual contracts from
- Six figures
- Seats included
- 10
- Air-gapped
- On request
SovereignCompute · your servers
Mission data sentNone · by design
01 The perimeter
What stays, and the only things that leave
Sovereign is built to run on your own servers; your mission data never comes to Arksa.
Stays on your servers
Everything that is the mission
- Scenarios and spacecraftOrbits, constellations, payloads, power and comms settings.
- Ground segmentStations, masks and networks.
- ResultsAccess, coverage, power, link, conjunction, Δv and every other analysis runs on your servers.
- Imported filesSTK, GMAT, CCSDS, TLE and the rest are converted inside your perimeter.
Crosses the line
Three kinds of check
Only licence, reference-data and update checks reach Arksa, and none of them can carry mission content. We walk your security team through each one in a call.
- Licence
- Reference data (the public satellite catalogue, Earth orientation and space weather)
- Updates
02 Enforced, not promised
Enforced on the server, not promised by the app
The boundary does not depend on a client behaving.
- 1Calls
No call carries mission content
Only the listed checks reach Arksa.
- 2Uploads
Mission uploads refused
Arksa's cloud will not take your mission data.
- 3Audit
Every change recorded
Changes to the boundary are written to your audit log.
03 Deployment
On your servers, scoped with you
Sovereign is built to run on your own servers; deployments are scoped with each customer.
Your servers, Arksa's reference data
The web studio connects to your own servers. Analyses run and files live there.
- Same engine, your servers. Every analysis runs on your servers.
- Your files, your servers. Missions and files stay inside your perimeter.
- Arksa's reference data. Without your mission data ever leaving.
Your organisation
# where the work lives Missions your servers Results your servers
The Arksa server, on your premises
The Arksa server is built to run the studio and the API inside your network, under your own network and security policies. Each deployment is scoped with the customer.
- Your licence. Issued for your deployment and checked on site.
- Your monitoring. Health checks for your tools, and backups your team controls.
- Your schedule. Upgrades from signed builds, when you choose.
Server host
# on your premises run the Arksa server licence checked on site upgrade on your schedule
Air-gapped, by arrangement
For a site with no route to the internet, how reference data and signed updates arrive is agreed with each customer, and licences verify on site.
- Reference data inside the perimeter. Delivery agreed per deployment.
- Licences on site. Signed licence files verify on site.
Air-gapped site
# no route to the internet reference data inside the perimeter updates signed builds licences verified on site
FIG. 01Your servers
Nothing of the mission at Arksa
Missions, files and results are stored and computed on your own servers. Arksa receives only licence, reference-data and update checks.
04 Identity and accountability
Roles, audit and signed licences
Roles for every person on the programme, and an audit log your admins can export.
Build
Builds and runs the mission.
Govern
Runs the organisation.
Own
Holds the licence.
Audit log and export
Every sign-in and every change, recorded. Admins can export it.
Signed licences
Signed licence files verify on site.
Security documentation
Security documentation in preparation; we answer questionnaires in a call. Request a briefing.
What Arksa can see
We tell your security team exactly what Arksa can see: your account and organisation records, and nothing of the mission. We walk them through the full list in a call.
05 The plan
Sovereign, in numbers
Sales-led: contact us. Annual contracts from six figures, scoped per deployment. Air-gapped by arrangement. Every analysis module is included.
Sovereign Sales-led
For agencies and regulated operators.
Contact us
Annual contracts from six figures, scoped per deployment. 10 seats included · air-gapped by arrangement
- Compute and files stay on your servers
- Only licence, reference-data and update checks reach Arksa
- Missions, files and results stored on your servers
- Signed licence files and audit export
- Deployment on your own servers, scoped with you; air-gapped by arrangement
- Direct line to the founder; support terms agreed per contract
Under NDA
Bring your hardest question. We show it on your mission in a briefing.
Request a Sovereign briefingExport control
Export-control law may apply to how customers use or transfer mission-analysis software. The Arksa licence terms require customers to comply with the export-control laws that apply to them. Arksa is developed in the EU.
06 Questions
Asked by security teams
No. The same engine that runs on Arksa's servers runs on yours, and every analysis module is included in Sovereign. Heavy studies run on your own servers.
Reference data stays available inside your perimeter. For an air-gapped site, by arrangement, its delivery is agreed per deployment.
Signed licence files verify on site.
No. Results are validated against published references and independent tools, not certified. Verify them independently before safety-of-flight or regulatory decisions. See the validation results.
Sovereign is sales-led, scoped per deployment
Bring Arksa inside the perimeter
Tell us about your programme and your deployment constraints. We walk your security team through every request.