Bring your hardest question. We show it on your mission in a briefing.
Under NDA, with the founder who builds Arksa.
Request a briefingEarth observation
Design the sun-synchronous orbit, prove revisit over the places you image, find every imaging opportunity and land the data. Downlink, power and lifetime are checked in the same mission.
01The imaging problem
Get a valid orbit back, timed to the light you need. Design
Draw your areas and read revisit, gaps and response time. Coverage
Every imaging pass over a target, with the Sun angle, counted honestly. Operate
Station passes, margins and data volume for every contact. Link budget
Eclipses, battery and lifetime against the disposal rules. Power
Tell the wizard how many revolutions in how many days, and it solves an orbit whose track closes on itself.
Validated: sun-synchronous design, with the nodal rate matched to the Sun’s →
Pick the local time of every picture, and watch the eclipse season move as you drag.
FIG 03Revisit and gaps
The next 24 hours over eight cities, from an 18-satellite template, computed live on this page.
Validated: sensor footprints against the published geometry →
Contacts, data volume and eclipses for the next day come from one mission, so a change of orbit updates the downlink plan.
Validated: the ITU-R rain model against its published tables →
02Start from a real mission
The template gallery comes with reference missions you can open, change and share. Start from ready-made Earth-observation missions.
Two optical imagers sharing one sun-synchronous orbit.
A constellation of imagers for revisit several times a day.
A radar satellite on a repeat ground track for interferometry.
03Built for imaging
Every orbit an imaging mission needs, with the local time you want over your targets.
Grow one satellite into a fleet, or bring in the satellites already flying.
How often you see each area, and how long you wait between looks.
Every pass over your stations and targets, with the terrain and limits that matter.
Enough power through every eclipse, to the end of the mission.
Ask for a target every pass and approve the plan: passes, uplink and downlink, timed for you.
Every pass lands its data, with the margin to prove it.
Bring your files in as missions, and hand results to the tools downstream.
04Scale
More seats, more compute and shared workspaces come with Team and above. Plans and pricing.
05Questions
Yes. Bring in the files from the tools you use today, or a constellation already flying, and analyse and share it in Arksa.
Yes. Optical tasking checks the solar elevation at the target; radar passes count day and night.
Orbit design is checked against published references on every change. See the validation results.
On Sovereign, compute and files stay on your own servers. None of your mission data reaches Arksa: targets, schedules and results never leave.
Under NDA, with the founder who builds Arksa.
Request a briefing06More solutions
Walker shells, crosslinks, latency against fibre and conjunction screening at scale.
Transfers, Lagrange points, and relays for the Moon and Mars.
Built to run on your own servers. Only licence, reference-data and update checks reach Arksa.
Early access · Mission and Sovereign by contract
The Sun-synchronous imaging pair is on Pro. Request access to open it, or talk to us about your fleet.