Vision
Build a fast, reliable, script-friendly speed test CLI that supports multiple providers with a consistent output model.Guiding Priorities
The development of Universal Speedtest CLI is driven by four core principles:Accuracy First
Stable measurement methodology and transparent metrics ensure reliable results you can trust.
Extensibility
Provider-agnostic architecture enables support for multiple speed test backends.
Automation-Friendly
Predictable exit codes and JSON-first workflows make CI/CD integration seamless.
Operational Trust
Reproducible releases and strong CI quality gates ensure production reliability.
Development Phases
Our roadmap is organized into distinct phases, each building upon the previous foundation. This structure is directional and may evolve based on community feedback.Phase 1: Foundation Hardening
Phase 1: Foundation Hardening
Strengthening the core functionality with improved error handling and reliability features.
- Add structured error codes and clearer failure diagnostics
- Add timeout/retry flags for unstable networks
- Add a
--no-colorflag (in addition toNO_COLORenv support) - Expand tests for edge-case latency/packet-loss scenarios
- Add benchmark tests for core stats functions
Phase 2: Multi-Provider Core
Phase 2: Multi-Provider Core
Introducing a flexible provider system that enables support for multiple speed test backends.
- Introduce a provider interface (
cloudflare, future providers) - Add
--providerflag withautoand explicit provider selection - Normalize results so provider changes do not break JSON consumers
- Add provider capability reporting (what each backend can measure)
- Add integration tests for provider-specific adapters
Phase 3: CLI and Output Enhancements
Phase 3: CLI and Output Enhancements
Expanding output options and test configurations for advanced use cases.
- Add machine-readable metadata (
timestamp,provider,version) - Add NDJSON / compact streaming output mode for automation pipelines
- Add optional result export (
--outJSON file) - Add configurable test profiles (
quick,standard,deep) - Add optional localization improvements for human-readable output
Phase 4: Ecosystem and Reliability
Phase 4: Ecosystem and Reliability
Building distribution channels and improving the contributor experience.
- Homebrew formula and common package ecosystem support
- Docker image for CI and container-based workflows
- Signed release artifacts and optional provenance/SBOM support
- Optional telemetry design proposal (off by default)
- Public contribution guide for adding new providers
Community Input
Feature requests and provider proposals are welcome via GitHub Issues.Priority will favor changes that keep outputs stable and improve real-world reliability.
- Check existing issues to avoid duplicates
- Describe your use case and the problem you’re solving
- Consider backward compatibility and stability
- Provide examples or references when possible