One published interface. Three ways to fly.
Arqlius is a shared hub you can trust because its owner competes with no one. You qualify against a stable, published interface — the same rulebook, applied identically to every tenant, with every custody event committed to a neutral, auditable ledger. The moat is service, not lock-in.
Come as a visitor, a resident, or a passenger.
Three ways to use the hub, from the lowest barrier to a permanent presence.
Visiting Vehicles
Tugs, servicers and cargo craft that dock and depart. You fly to the arrival hold, execute the published approach, and berth on an assigned, deconflicted corridor — then leave when your mission is done.
Resident Berth Modules
A module you lease or own, launched to self-berth and stay. Start with one isolated berth and scale to a whole row. Your module draws hub shore power and services on an SLA; you retain full authority over your own system.
Usage Tenants
Your cargo transits the hub aboard third-party vehicles — cross-docked, stored in the ring, or transferred to another tenant under a contract you both see settle in near real time. The lowest barrier to entry.
From first contact to a standing berth.
The engineering track and the commercial track run in parallel — so your team can begin conforming a vehicle long before terms are signed.
Engage
You receive the Interface Control Document and the tariff schedule; interface compliance is scoped. The commercial track — usage, lease, or membership — proceeds alongside the engineering work.
Qualify
Four gates: interface compliance review, interface qualification on the ground emulator, a joint integrated simulation, and a first-arrival supervised demonstration.
Operate
Standing berth windows or per-call requests; utilities on SLA; cargo and propellant services by tariff. Disputes are arbitrated against the ledger record, not against a rival's word.
Grow or Leave
Usage tenants can step up to a leased module that launches and self-berths. Departing tenants close out with a final settlement extract and their module departs or transfers — no exit penalty beyond the contracted term.
Your rival can be berthed next door and never see your telemetry.
No tenant's data is observable by another tenant, or by Arqlius operations, beyond the minimal safety-required parameter set. Per-berth feeds are independently protected, so a fault in any tenant's system sheds only that berth. And because Arqlius flies its own tug through the very same corridors, rules and billing as every tenant, the neutrality claim is exercised daily by Arqlius itself.
The rulebook executes the same for everyone — and leaves an auditable trail.
A fully serviced address in orbit.
Baseline per-berth provisions. Values are preliminary and controlled through the Interface Control Document. See the facility overview for the full picture.
| Power | 1–15 kW per berth at 120 VDC, dual A/B feeds, metered as custody events. |
|---|---|
| Thermal | Up to 5 kW heat rejection via self-sealing coolant quick-disconnects. |
| Data | Isolated 1 Gb/s-class tenant fibre, cryptographically separated, relay-backhauled. |
| Docking | IDSS soft-capture; visiting vehicles to 12,000 kg on published, auditable corridors. |
| Cargo | Robotic, EVA-free cross-dock between berths and to the ~1,300 m³ storage ring. |
| Settlement | Every custody transition — capture, transfer, metering — committed to the neutral ledger, near real time. |
Become an Arqlius tenant.
Whether you're conforming a vehicle, planning a resident module, or exploring usage access — we'd like to understand your mission and share the tenant engagement package.
Inquiries are handled by legal@vexidus.com — Vexidus Corporation, majority owner of Arqlius.