Project and Licensing

What is the Traverse roadmap?

Q: What is the Traverse roadmap?

The Traverse roadmap focuses on completing placement targets (browser, edge, cloud, AI pipeline), adding language SDKs beyond Rust, a hosted capability registry, and production hardening. The local target is stable in v0.7.0. See the public roadmap page for current milestone status.

Traverse v0.7.0 has a stable local placement target. The roadmap focuses on completing the remaining placement targets, adding language SDKs beyond Rust, a hosted registry option, and production hardening. See the full roadmap page for current milestone status.

Placement targets

The five planned placement targets are: local (done), browser (in development), edge, cloud, and AI pipeline. Each target runs the same WASM binary with the same contract enforcement — they differ only in the host environment they integrate with.

Browser adapter via traverse-expedition-wasm — in active development
Edge target (Cloudflare Workers, Fastly Compute) — planned
Cloud target (Lambda, Cloud Run) — planned
AI pipeline target — planned

Language SDKs

Capabilities must be written in Rust today (anything that compiles to wasm32-wasi works, but Rust is the primary path). The roadmap includes SDKs that let developers write capabilities in Python, TypeScript, and Go, with the SDK handling the WASM compilation and contract generation automatically.

Hosted registry

Running a local registry is fine for single-machine use. The roadmap includes a hosted registry service for teams that need to share capabilities across machines and environments. This is analogous to crates.io for WASM capabilities.

Production hardening

Long-term trace storage integration
Registry access controls
Capability signing and verification
Performance benchmarks and optimization
Expanded test coverage for edge cases

The roadmap is public and open to community input. See roadmap for the full picture and how to contribute if you want to help with any of these areas.