Getting Started With 301.st
The practical rollout order for teams moving from account creation to live Cloudflare-backed redirect workflows.
The Short Version
- Create access. Sign in with email or OAuth and make sure the account you use matches the team that will own operations.
- Connect Cloudflare. This is the trust boundary that unlocks zone discovery, domain sync, and routing workflows.
- Sync domains. Pull real inventory into the domains layer before trying to model downstream logic.
- Create structure. Use projects and sites when you need clear boundaries for brands, offers, teams, or destinations.
- Launch redirects. Treat redirects as the main stable production workflow once the foundation is clean.
Start Here If
- You already manage real Cloudflare-backed domains and want a cleaner control surface.
- You need projects, sites, and redirect logic to stay readable as the setup grows.
- You are evaluating 301.st for production use and want the least risky entry path.
Do Not Start With
- Advanced routing ideas before Cloudflare access and domain sync are trustworthy.
- Premature project fragmentation for every single domain.
- TDS as the first public workflow when redirects are the more mature path today.
Feels Production-Ready Today
- Authentication and account access.
- Cloudflare and registrar-linked integrations.
- Domains table, filtering, inspection, and operational actions.
- Projects and sites as structure for growing accounts.
- Redirect setup and sync workflows.
Treat More Carefully
- TDS is real and shipped, but still newer in public framing than redirects.
- Not every account needs deep project or site structure on day one.
- The best rollout usually starts with a narrow production slice, not with every possible surface at once.
FAQ
Do I need Cloudflare first?
For the main workflow, yes. 301.st is built around Cloudflare-managed infrastructure and reaches value fastest there.
Can I start with redirects only?
Yes, after integration and domain sync are in place. Redirects are the strongest first production workflow in the product.
Should I begin with TDS?
No. Keep TDS discoverable, but treat it as a newer surface unless your use case specifically depends on it.