Arqlius One orbital hub
A Vexidus Corporation Company

The Neutral Truck Stop of Space

Shared orbital logistics infrastructure the whole industry can trust — built one de-risked gate at a time.

Everyone in space is about to rebuild the same infrastructure — docking, power, propellant, coordination. Arqlius builds it once, neutrally, and opens it to all of them.

The Problem

The logistics layer is being rebuilt from scratch — by everyone, at once.

Satellite servicing, cislunar delivery, in-space manufacturing and lunar logistics are all arriving together. Each new operator solves the same fixed problems alone — and runs the result far below capacity.

01

Dock

Every operator builds its own berthing interface from zero.

02

Power & Thermal

Each duplicates the same utility systems, underused.

03

Propellant

Storage and transfer, solved five times over.

04

Coordinate & Settle

No trusted books across rival operators.

The pattern is old. Before ports, every merchant built their own dock. The wasteful equilibrium persists until someone builds the shared layer — and it only works if its owner doesn't compete with the users.

The Insight

Neutrality is the moat — and it can't be copied.

A fleet operator can build a hub. What it cannot build is the trust of its own competitors. A hub owned by a fleet operator can throttle, deprioritize, or observe its rivals — the moment infrastructure is owned by a competitor, it stops being infrastructure and becomes a weapon.

Arqlius owns no competing fleet.

Our tug exists to prove capability and generate the custody data our software settles — not to compete with our tenants. Neutrality is a fact of our structure, enforced in software, not a marketing posture. Every custody transition is committed to a neutral, auditable ledger.

The Facility — Arqlius One

Twelve identical berths, a twelve-module cargo ring, and a spine that keeps hazard away from tenants.

The frozen pilot configuration: three service cores, a spoke-rooted adapter, three tenant rows, and a cargo ring at the boundary — designed so bulk propellant always stays two full segments from any tenant berth.

Arqlius One frozen configuration — engineering schematic
Arqlius One — Frozen Configuration · 70 m flown structure
  • 12Berths across three rows — metered power, data, thermal and storable propellant, fault-isolated at each berth's own service vault.
  • ~1,300 m³Cargo ring (N=12) of leasable, robot-served storage at the service / tenant boundary.
  • 1–15 kWPer-berth power at 120 VDC on dual A/B feeds, metered; 5 kW thermal rejection; 1 Gb/s isolated data.
  • IDSSSoft-capture docking — visiting vehicles up to 12,000 kg, on published, auditable approach corridors.
  • +1Reserved forward port — market-allocated to a fourth tenant row or a crewed safe-haven module as demand dictates.

Explore Arqlius One in detail →

Why Now — The Head Start

The hardest layer to copy is already built and working.

The defensible layer — coordination and settlement — exists today, proven inside the Vexidus ecosystem. Arqlius productionizes built assets for flight; it does not invent the moat from zero.

Vexidus L1

Post-quantum ledger — the immutable custody & settlement layer across operators and jurisdictions.

Vexalus / Vexcelon

Logistics coordination software — scheduling, routing and billing for a multi-operator facility.

VIDA

Identity attestation — tenant-to-tenant isolation and verifiable, auditable custody events.

The Approach — Staged De-Risking

We don't build a station on faith. We fund the cheapest thing that de-risks one.

Each gate is proven before the next begins. Autonomous docking — the capability that gates every hub berthing — is demonstrated first on the tug's own paid missions.

1

Prove

Coordination software live and a storable tug flying paid LEO/GEO missions.

Lowest risk
2

Qualify

Cislunar tug and autonomous docking qualified; anchor tenant engaged.

Moderate
3

Fly the Hub

Seed hub flying and earning: cores and first row, then ring closure to twelve berths.

De-risked
4

Replicate

Crewed safe-haven module at the reserved port; additional hulls as pre-lease dictates.

Proven economics
For Tenants

The interface is the product's front door — and it's open years before we fly.

Our Tenant Interface Control Document lets your engineers conform their vehicle to the hub long before it launches. Three ways to fly with Arqlius:

CLASS A

Visiting Vehicles

Tugs, servicers and cargo craft that dock and depart on assigned, deconflicted corridors.

CLASS B

Resident Berth Modules

Leased or owned modules that self-berth and stay — start with one isolated berth, scale to a whole row.

CLASS C

Usage Tenants

Cargo that transits the hub aboard third-party vehicles — the lowest barrier to entry.

See the tenant lifecycle & interface →

Build It Once, Neutrally

Register your interest.

Whether you're a prospective tenant conforming a vehicle, an operator exploring the shared layer, or an investor tracking the program — we'd like to hear from you.

Inquiries are handled by legal@vexidus.com — Vexidus Corporation, majority owner of Arqlius.