Getting Started With 301.st

The practical rollout order for teams moving from account creation to live Cloudflare-backed redirect workflows.

The Short Version

  1. Create access. Sign in with email or OAuth and make sure the account you use matches the team that will own operations.
  2. Connect Cloudflare. This is the trust boundary that unlocks zone discovery, domain sync, and routing workflows.
  3. Sync domains. Pull real inventory into the domains layer before trying to model downstream logic.
  4. Create structure. Use projects and sites when you need clear boundaries for brands, offers, teams, or destinations.
  5. 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.

Recommended Production Rollout Order

The safest way to adopt 301.st is to build confidence in layers. First connect the infrastructure, then verify the inventory, then create structure, and only then push the routing workflow your team will actually operate every day.

  • Layer 1: access and authentication.
  • Layer 2: Cloudflare integration and domain sync.
  • Layer 3: projects and sites where they improve clarity.
  • Layer 4: redirects as the main live workflow.
  • Layer 5: TDS only when your use case genuinely needs the newer routing surface.

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.

Next Guides to Open

Cloudflare integration Domain management Projects and sites Redirects