Every engineer has their own system. That's the problem.
Astrolabe replaces ad-hoc scripts and inconsistent folder structures with a single capture workflow — serial, TCP, or file, normalized to a structured format with full metadata every time. Runs are stored locally first, so field sessions work offline, and nothing gets lost before it reaches the backend.
Capabilities
Built for engineers who need dependable acquisition, structured records, and seamless handoff to the Orrery QA environment.
Standardized capture
Connect serial ports and TCP sockets with astrolabe capture. Every run uses consistent sampling and timestamping, so results are comparable across engineers, sessions, and devices.
Structured records
Every run is stored with a manifest, SHA-256 checksums, and schema version. NDJSON output is ready for automated analysis, CI replay, or direct handoff to the Orrery platform.
Resilient delivery
Runs are cached locally before upload, so captures succeed even without network. astrolabe upload retries automatically, resumes partial transfers, and never double-submits a run that already landed.
File ingestion
Import existing CSV, JSONL, and raw log files into the same normalized run format with astrolabe capture file. Bring your existing test data with you — no recapture required.
Operational workflow
A predictable sequence from configuration through upload keeps bench sessions traceable and auditable.
Integration with Orrery
Once a run leaves the local cache, Orrery takes over — registering artifacts, coordinating storage, and making the data immediately available for review, triage, and reporting.
- ▹Uploads target presigned URLs or API endpoints created by Orrery, keeping authentication aligned with platform policy.
- ▹Each run is registered with a
run_id, ensuring artifacts, manifests, and follow-up analysis share one source of truth. - ▹Structured JSON logs simplify CI pipelines and integrate cleanly with observability tooling.