Every test run,
on the record.

Astrolabe captures hardware test data where the test happens. Orrery keeps every run in one record your release decisions can point back to.

Start with Astrolabe See Orrery

PSU-200, revision C 6 runs

Each row opens its manifest, artifacts, and rule results.

How a run gets from the bench to a release.

Astrolabe owns the first half, Orrery the second. Nothing is handed off by email or a shared drive in between.

Capture
astrolabe capture
Reads from serial ports, TCP sockets, or files you already have (CSV, JSONL, raw logs) and stores each run locally first.

A dropped connection doesn’t lose a run.
Upload
astrolabe upload
Sends stored runs to Orrery. Uploads resume where they stopped, retry on failure, and never arrive twice.

Every run captured at the bench reaches the record once.
Analyze
In Orrery
Checks each run’s manifest and artifacts against your validation rules, with optional AI analysis.

Filter by project and compare runs instead of rebuilding context from folders.
Ship
In Orrery
Release decisions cite the exact manifest, artifacts, and rule set behind them.

When someone asks why a build shipped, the answer is already on the record.

Astrolabe works where the test runs. Orrery is where the team reads the results.

Capture, at the bench

Built for unstable rigs and patchy networks. Stores a complete run locally before anything else happens.

Captures from serial ports, TCP sockets, or existing CSV, JSONL, and raw log files.
Keeps captures safe on disk while the network is down.
Uploads to Orrery with automatic retry, resume, and no duplicates.

Use Astrolabe free

Analysis, for the team

Turns Astrolabe runs into a project record that engineers, QA, and release owners can question.

See Orrery in action