What 301.st actually is

301.st is a management interface that sits on top of the infrastructure you already own. It is not a hosting service, not a redirect proxy, not a TDS provider running its own servers, and not a replacement for Cloudflare or your registrar.

Your domains stay in your registrar. Your zones stay in your Cloudflare account. Your traffic never passes through our servers — it runs on your own Cloudflare Workers, at the edge. We just give you one place to manage all of it instead of jumping between five dashboards every time you change a redirect or add a new offer.

What 301.st helps you do

  • Manage your domain portfolio across one or more Cloudflare accounts from one screen.
  • Push redirects from old URLs to new offers without manual DNS changes — your rule is live at the Cloudflare edge within seconds, not at DNS-propagation speed.
  • Set up GEO and UA routing rules and A/B splits at the edge with TDS — no separate provider to host or maintain on your own VPS.
  • Process postbacks from affiliate networks and keep attribution connected to the campaigns and sites that drove them.

What stays yours

  • Your Cloudflare account, your zones, your credentials — we connect through your scoped API tokens and you can revoke them in one click.
  • Your registrar accounts and domain ownership — we read your portfolio, we do not take it over.
  • Your hosting and landing pages — they live wherever you put them, we just route traffic to them.
  • Your data and your traffic — nothing passes through our servers, everything runs on your Cloudflare edge.

How the workflow fits together

  1. Connect Cloudflare — your account, your scoped API tokens, revoke any time.
  2. Sync your domains — your existing portfolio becomes a searchable, filterable dashboard with health monitoring.
  3. Organize by campaigns — group domains into projects and sites that match how you actually work (one project per offer, per brand, per geo — whatever fits).
  4. Set up redirects — edge-speed rules with GEO and UA filtering, deployable in bulk across many domains at once.
  5. Add TDS for split testing — site-scoped routing rules for A/B tests, geo-splits, and conditional landing logic, running at the Cloudflare edge.
  6. Track conversions — postbacks from affiliate networks land back in your dashboard for real-time attribution.

Principles behind the product

We want this kind of tooling to feel calmer, not more chaotic. That means clear ownership boundaries and fewer hidden moving parts.

  • Your setup stays yours. 301.st improves how you operate it. It doesn't take ownership.
  • Structure matters. The product is strongest when you can still understand your own setup six months later.
  • Honest copy. Every capability described on this site is one you can use today, described the way it actually behaves.
  • The free plan is real. Not a 14-day trial wrapped in marketing — start a project on Free during Open Beta, scale through Pro and Business as your portfolio grows. See pricing for what each tier covers.

Who it's built for

  • SEO webmasters running portfolios of affiliate domains, with regular redirect operations.
  • Affiliate media buyers placing landing pages and routing paid traffic across geos and offers.
  • Agencies managing affiliate infrastructure for multiple clients without giving up ownership control.
  • Solo affiliates and small teams who want one workspace instead of five tabs, and a free plan that's a real starting point — not a 14-day trial.

If you do non-affiliate redirect work — corporate rebrand consolidations, e-commerce migrations, internal traffic routing — the same platform fits, with the same boundary rules.

Try it free in Open Beta

The free plan is enough to run a small affiliate site from domain to offer to conversion tracking. No card required, no time limit during Open Beta.