Docs
Getting started
VeluneOS has two tools. Pick the one that matches your question — they work independently.
One log → Velune Trace“Where in this log should I look first?” Open source, runs locally, no account.
Two runs → VeluneOS Compare“What changed between these two runs?” Prepare locally with the Adapter Kit, compare in the hosted Private Beta.
The Compare workflow
- Get access. Compare is a Private Beta. Request access; we confirm data-use terms in writing and send Compare credentials.
- Install the Adapter Kit on the machine that holds your recordings. Install
- Prepare two runs locally: discover streams, name the ones you care about, confirm any uncertain pairing, and generate
comparison.velune. Prepare two runs - Review the preview (
comparison.preview.json) to see exactly what the file contains. Review the preview - Sign in and upload at compare.veluneos.ai/compare. Upload and read the report
- Read the report and verify the reported windows in your own tools. The engineering decision is yours.
Raw MCAP stays on your machine. The Adapter never uploads anything; you upload one derived file yourself. See Data boundaries.
Requirements at a glance
| Tool | Runs | Needs | Input |
|---|---|---|---|
| Velune Trace | Your machine | Python 3.12 (validated on Ubuntu 24.04) | One MCAP file |
| Velune Adapter (Beta Kit 0.1.1b5) | Your machine | Python 3.12 or 3.13 | One Reference MCAP + one Target MCAP |
| VeluneOS Compare | Hosted | Beta credentials, a web browser | comparison.velune from the Adapter Kit |
Help
Questions during the Beta: [email protected]. Please never attach raw logs, credentials or personal data.