TDS Status and Rollout Guide
A public status page for a shipped but newer routing surface that is still catching up to the maturity of redirects.
What Is True Today
TDS exists in the product and already has real operational shape. It is not imaginary or purely conceptual.
At the same time, its public story should still be framed more carefully than redirects. The goal is accuracy, not overstatement.
Safe Public Framing
- TDS is an active product area inside 301.st.
- It already belongs to the broader Cloudflare-backed operating model.
- Public docs should describe its current position and boundaries, not pretend it is the only routing story that matters.
What We Intentionally Avoid
- Over-optimized SEO pages that imply final feature completeness.
- Promises that could outpace the actual public rollout.
- Copy that competes with redirects as the main production entry point today.
How to Position TDS Next to Redirects
Redirects should continue to carry the more mature documentation and SEO intent. They are easier to explain as a stable, production-ready workflow.
TDS should remain visible, searchable, and honest. The right message is that it is real, shipped, and evolving, but still newer in public positioning than the redirect layer.
Who Should Read This Page Right Now
- Teams already evaluating the broader 301.st platform and wanting a realistic picture of newer routing surfaces.
- Partners or operators deciding whether redirects are enough today or whether they should track TDS more closely.
- Anyone who needs the honest public position instead of a hype-driven feature pitch.
FAQ
Is TDS available inside the product?
Yes, but this page deliberately avoids presenting it as the most mature workflow in the platform.
Should public search traffic land on TDS pages first?
No. Redirects and setup guides are stronger first-entry pages for production intent right now.
Will this page likely change later?
Yes. As TDS settles further, this status page can grow into a fuller guide set.