1<!doctype html> 2<html lang="en" data-theme="dark" data-i18n-surface="marketing"> 3 <head> 4 <meta charset="UTF-8" /> 5 <meta name="viewport" content="width=device-width, initial-scale=1.0" /> 6 <title data-i18n="contactPage.head.title">Contact 301.st | Partnerships, Integrations, and Business Inquiries</title> 7 <meta 8 name="description" 9 content="Contact 301.st about partnerships, integrations, agency workflows, product feedback, and business inquiries around Cloudflare-native redirect operations." 10 data-i18n-content="contactPage.head.description" 11 /> 12 <meta name="keywords" content="contact 301.st, partnerships, integrations, agency workflows" data-i18n-content="contactPage.head.keywords" /> 13 <link rel="canonical" href="https://301.st/contact" data-i18n-href="contactPage.head.url" /> 14 <meta property="og:type" content="website" /> 15 <meta property="og:site_name" content="301.st" /> 16 <meta property="og:title" content="Contact 301.st | Partnerships, Integrations, and Business Inquiries" data-i18n-content="contactPage.head.title" /> 17 <meta 18 property="og:description" 19 content="Talk to the 301.st team about partnerships, integrations, agency workflows, and business inquiries." 20 data-i18n-content="contactPage.head.socialDescription" 21 /> 22 <meta property="og:url" content="https://301.st/contact" data-i18n-content="contactPage.head.url" /> 23 <meta property="og:image" content="https://301.st/img/og.jpg" /> 24 <meta property="og:image:width" content="1200" /> 25 <meta property="og:image:height" content="630" /> 26 <meta name="twitter:card" content="summary_large_image" /> 27 <meta name="twitter:title" content="Contact 301.st | Partnerships, Integrations, and Business Inquiries" data-i18n-content="contactPage.head.title" /> 28 <meta 29 name="twitter:description" 30 content="Talk to the 301.st team about partnerships, integrations, agency workflows, and business inquiries." 31 data-i18n-content="contactPage.head.socialDescription" 32 /> 33 <meta name="twitter:image" content="https://301.st/img/og.jpg" /> 34
34<script type="application/ld+json" data-i18n-html="contactPage.head.schema"> 35 { 36 "@context": "https://schema.org", 37 "@type": "ContactPage", 38 "name": "Contact 301.st", 39 "description": "Contact 301.st about partnerships, integrations, agency workflows, product feedback, and business inquiries.", 40 "url": "https://301.st/contact", 41 "isPartOf": { 42 "@type": "WebSite", 43 "name": "301.st", 44 "url": "https://301.st" 45 } 46 } 47 </script>
47 48 <link rel="alternate" hreflang="en" href="https://301.st/contact" /> 49 <link rel="alternate" hreflang="ru" href="https://301.ru/contact" /> 50 <link rel="alternate" hreflang="de" href="https://301.st/de/contact" /> 51 <link rel="alternate" hreflang="es" href="https://301.st/es/contact" /> 52 <link rel="alternate" hreflang="pt-BR" href="https://301.st/pt/contact" /> 53 <link rel="alternate" hreflang="tr" href="https://301.st/tr/contact" /> 54 <link rel="alternate" hreflang="uk" href="https://301.st/uk/contact" /> 55 <link rel="alternate" hreflang="pl" href="https://301.st/pl/contact" /> 56 <link rel="alternate" hreflang="x-default" href="https://301.st/contact" /> 57 <link rel="icon" href="/favicon.ico" sizes="any" /> 58 <link rel="icon" type="image/svg+xml" href="/favicon.svg" /> 59 <link rel="apple-touch-icon" href="/apple-touch-icon.png" /> 60 <link rel="stylesheet" href="/css/theme.css?v=488e9981" /> 61 <link rel="stylesheet" href="/css/layout.css?v=c47f05a8" /> 62 <link rel="stylesheet" href="/css/site.css?v=5742ca1a" /> 63
63<script type="module" crossorigin src="/assets/locales-en-core-Bs6rsBqu.js"></script>
63 64
64<script type="module" crossorigin src="/assets/visit-CLllHqUa.js"></script>
64 65
65<script type="module" crossorigin src="/assets/tabs-BfHvRz9E.js"></script>
65 66
66<script type="module" crossorigin src="/assets/main-public-D8_5nxql.js"></script>
66 67 </head> 68 <body class="surface-mesh"> 69 <header class="site-header" role="banner"> 70 <!-- Canonical page shell guidance: 71 - Static content pages: wrap main content with class="page-shell" (often with stack-list) to keep gutters aligned. 72 - App-shell pages: use layout-shell/layout-main wrappers inside a page-shell when needed. 73 - Always include CSS in order: theme.css, layout.css, site.css. 74 - Keep header/footer partials inside the page-shell context so spacing stays consistent. --> 75 <div class="page-shell site-header__inner"> 76 <!-- Full logo for desktop --> 77 <a class="brand brand--full" href="/" aria-label="301.st"> 78 <img src="/img/301-full.svg" alt="301.st" width="80" height="32" /> 79 </a> 80 81 <!-- Compact logo for mobile (when burger appears) --> 82 <a class="brand brand--compact" href="/" aria-label="301.st"> 83 <svg class="brand__logo" aria-hidden="true"> 84 <use href="#i-brand-301"></use> 85 </svg> 86 </a> 87 88 <button 89 class="btn-chip burger-button" 90 type="button" 91 aria-label="Open menu" data-i18n-aria="common.aria.openMenu" 92 aria-expanded="false" 93 data-mobile-menu-toggle 94 > 95 <span class="icon" data-icon="mono/backburger"></span> 96 </button> 97 98 <!-- Dashboard nav (logged in) --> 99 <nav class="primary-nav" aria-label="Primary" data-i18n-aria="common.aria.primaryNav" data-onlogin hidden> 100 <a href="/integrations" data-i18n="layout.nav.integrations">Integrations</a> 101 <a href="/projects" data-i18n="layout.nav.projects">Projects</a> 102 <a href="/domains" data-i18n="layout.nav.domains">Domains</a> 103 <a href="/redirects" data-i18n="layout.nav.redirects">Redirects</a> 104 <a href="/sites" data-i18n="layout.nav.sites">Sites</a> 105 <a href="/streams" data-i18n="layout.nav.streams">Streams</a> 106 </nav> 107 108 <!-- Marketing nav. Visible on public pages regardless of auth state 109 so a logged-in user browsing /pricing or /features still has 110 marketing-section navigation. On dashboard pages it's hidden via 111 CSS (body.layout-dashboard) to keep the dashboard top bar focused. 112 Login is split out into a dedicated logged-out CTA below. --> 113 <nav class="primary-nav primary-nav--public" aria-label="Site sections" data-i18n-aria="common.aria.siteSections" data-nav-public> 114 <a href="/features" data-i18n="layout.nav.features">Features</a> 115 <a href="/pricing" data-i18n="layout.nav.pricing">Pricing</a> 116 <a href="/partners" data-i18n="layout.nav.partners">Partners</a> 117 <a href="/docs" data-i18n="layout.nav.docs">Docs</a> 118 <a href="/#login" data-onlogout hidden data-i18n="layout.nav.login">Login</a> 119 </nav> 120 121 <div class="header-actions"> 122 <div class="dropdown lang-switcher" aria-label="Language selection" data-i18n-aria="common.aria.languageSelection"> 123 <button 124 type="button" 125 class="btn-chip btn-chip--sm btn-chip--dropdown dropdown__trigger lang-switcher__trigger" 126 aria-haspopup="listbox" 127 aria-expanded="false" 128 data-i18n-aria="layout.lang.label" 129 > 130 <span class="lang-flag" data-lang-flag></span> 131 <span class="btn-chip__label" data-lang-label>Ð ÑÑÑкий</span> 132 <span class="btn-chip__chevron icon" data-icon="mono/chevron-down"></span> 133 </button> 134 <div class="dropdown__menu dropdown__menu--align-left" role="listbox" data-lang-menu></div> 135 </div> 136 137 <button class="btn-icon btn-icon--compact theme" aria-label="Toggle theme" data-theme-toggle data-i18n-aria="layout.nav.theme"> 138 <span class="icon" data-icon="mono/sun"></span> 139 </button> 140 </div> 141 </div> 142 143 144 <div class="utility-bar"> 145 <div class="page-shell utility-bar__inner"> 146 <div class="utility-left"> 147 <nav class="breadcrumbs" aria-label="Breadcrumb" data-i18n-aria="common.aria.breadcrumb"> 148 <a href="/" class="crumb" 149 ><span class="icon" data-icon="mono/home"></span> <span data-i18n="layout.nav.home">Home</span></a 150 >
151 <span class="sep" aria-hidden="true">></span> 152 <span class="crumb is-current" data-i18n="contactPage.breadcrumb">Contact</span> 153 <span class="badges"> 154 <span class="badge badge--brand" data-i18n="contactPage.badge">Partnerships</span> 155 </span> 156 </nav> 157 </div> 158 159 <div class="utility-right"> 160 <a class="btn-icon btn-icon--compact" href="/docs" aria-label="Help" data-i18n-aria="layout.nav.help" data-onlogout hidden> 161 <span class="icon" data-icon="mono/help-circle"></span> 162 </a> 163 164 <button class="btn-icon btn-icon--compact" type="button" aria-label="Notifications" data-i18n-aria="common.aria.notifications" data-onlogin hidden> 165 <span class="icon" data-icon="mono/bell"></span> 166 </button> 167 168 <a class="btn-chip btn-chip--input" href="/account" data-onlogin aria-label="User account" data-i18n-aria="layout.nav.account" hidden> 169 <span class="btn-chip__icon" data-icon="mono/user"></span> 170 <span class="btn-chip__label" data-user-name data-i18n="layout.nav.guest">Guest</span> 171 </a> 172 173 <button class="btn-icon btn-icon--compact" type="button" data-onlogin data-action="logout" aria-label="Log out" data-i18n-aria="auth.logout" hidden> 174 <span class="icon" data-icon="mono/log-out"></span> 175 </button> 176 </div> 177 178 </div> 179 180<div 181 id="GlobalNotice" 182 class="app-alert app-alert--info" 183 data-state="hidden" 184 data-type="info" 185 role="status" 186 aria-live="polite" 187> 188 <div class="app-alert__inner"> 189 <span class="icon app-alert__icon" aria-hidden="true"> 190 <svg> 191 <use href="#i-mono-info"></use> 192 </svg> 193 </span> 194 <div class="app-alert__content"> 195 <p id="GlobalNoticeText" class="app-alert__text"></p> 196 </div> 197 <button 198 type="button" 199 class="app-alert__close" 200 aria-label="Close notification" 201 data-i18n-aria="notice.close" 202 > 203 <span class="icon" aria-hidden="true"> 204 <svg> 205 <use href="#i-mono-close"></use> 206 </svg> 207 </span> 208 </button> 209 </div> 210</div> 211 212 </div> 213 </header> 214 215 <main class="page-shell stack-list" data-pagefind-body> 216 <header class="page-header"> 217 <h1 class="h1" data-i18n="contactPage.title">Contact 301.st</h1> 218 <p class="text-lead" data-i18n="contactPage.lead"> 219 Business grows through relationships. If you are exploring partnerships, integrations, agency workflows, or simply 220 want to see whether 301.st fits your stack, we would be glad to hear from you. 221 </p> 222 </header> 223 224 <div class="panel panel--info"> 225 <p class="text-sm"> 226 <span class="icon" data-icon="mono/info"></span> 227 <strong data-i18n="contactPage.notice.title">Business runs on good connections:</strong> 228 <span data-i18n="contactPage.notice.body"> 229 we are happy to talk partnerships, integrations, agency workflows, and practical ideas around Cloudflare-native 230 operations. 231 </span> 232 </p> 233 </div> 234 235 <div class="grid-2"> 236 <section class="card card--panel"> 237 <header class="card__header"> 238 <h2 class="card__title" data-i18n="contactPage.partnerships.title">Partnerships and business development</h2> 239 </header> 240 <div class="card__body stack"> 241 <p class="text-body" data-i18n="contactPage.partnerships.body">We enjoy meeting agencies, affiliate teams, product partners, and infrastructure folks who see overlap with the workflows 301.st is building.</p> 242 <ul class="list--spaced"> 243 <li data-i18n="contactPage.partnerships.item1">Partner conversations for agencies, affiliate teams, and ecosystem partners.</li> 244 <li data-i18n="contactPage.partnerships.item2">Commercial discussions when 301.st may fit your clients or internal stack.</li> 245 <li data-i18n="contactPage.partnerships.item3">Joint ideas around domains, redirects, and Cloudflare-heavy operations.</li> 246 </ul> 247 </div> 248 </section> 249 250 <section class="card card--soft"> 251 <header class="card__header"> 252 <h2 class="card__title" data-i18n="contactPage.integrations.title">Integrations and product ideas</h2> 253 </header> 254 <div class="card__body stack"> 255 <p class="text-body" data-i18n="contactPage.integrations.body"> 256 If you want 301.st to connect with another provider, internal tool, or workflow, that is exactly the kind of 257 conversation we want early. 258 </p> 259 <ul class="list--spaced"> 260 <li data-i18n="contactPage.integrations.item1">
260New registrar, provider, and infrastructure integration ideas.</li> 261 <li data-i18n="contactPage.integrations.item2">Workflow requests around Cloudflare, domains, redirects, and traffic routing.</li> 262 <li data-i18n="contactPage.integrations.item3">Feedback from teams doing real operational work at scale.</li> 263 </ul> 264 </div> 265 </section> 266 </div> 267 268 <section class="card card--panel"> 269 <header class="card__header"> 270 <h2 class="card__title" data-i18n="contactPage.form.title">Start the conversation</h2> 271 </header> 272 <div class="card__body stack"> 273 <p class="text-body" data-i18n="contactPage.form.lead"> 274 Send a quick note and tell us what you are exploring. A rough outline is enough: partnership idea, integration 275 request, agency workflow, product feedback, or a question about the platform. 276 </p> 277 278 <div class="contact-form-wrap"> 279 <form id="contact-form" class="stack" novalidate> 280 <div class="field"> 281 <label class="field-label" for="contact-name"> 282 <span data-i18n="contactPage.form.fields.name">Name</span> 283 <span class="text-muted" data-i18n="contactPage.form.optional">(optional)</span> 284 </label> 285 <input 286 type="text" 287 id="contact-name" 288 name="name" 289 class="input" 290 autocomplete="name" 291 data-i18n-placeholder="contactPage.form.placeholders.name" 292 placeholder="How should we address you?" 293 /> 294 </div> 295 <div class="field"> 296 <label class="field-label" for="contact-email"> 297 <span data-i18n="contactPage.form.fields.email">Email address</span> 298 <span class="field-required">*</span> 299 </label> 300 <input 301 type="email" 302 id="contact-email" 303 name="email" 304 class="input" 305 required 306 autocomplete="email" 307 data-i18n-placeholder="contactPage.form.placeholders.email" 308 placeholder="[email protected]" 309 /> 310 </div> 311 <div class="field"> 312 <label class="field-label" for="contact-telegram"> 313 <span data-i18n="contactPage.form.fields.telegram">Telegram</span> 314 <span class="text-muted" data-i18n="contactPage.form.optional">(optional)</span> 315 </label> 316 <input 317 type="text" 318 id="contact-telegram" 319 name="telegram" 320 class="input" 321 autocomplete="off" 322 data-i18n-placeholder="contactPage.form.placeholders.telegram" 323 placeholder="@username" 324 /> 325 </div> 326 <div class="field"> 327 <label class="field-label" for="contact-message"> 328 <span data-i18n="contactPage.form.fields.message">Message</span> 329 <span class="text-muted" data-i18n="contactPage.form.optional">(optional)</span> 330 </label> 331 <textarea 332 id="contact-message" 333 name="message" 334 class="textarea" 335 rows="4" 336 data-i18n-placeholder="contactPage.form.placeholders.message" 337 placeholder="Tell us about your team, workflow, partnership idea, or integration request..." 338 ></textarea> 339 </div> 340 <div style="position: absolute; left: -9999px;" aria-hidden="true"> 341 <label for="contact-website">Website</label> 342 <input type="text" id="contact-website" name="website" tabindex="-1" autocomplete="off" /> 343 </div> 344 <div id="contact-turnstile"></div> 345 <button type="submit" class="btn btn--primary" id="contact-submit">
346 <span data-contact-submit-label data-i18n="common.contactForm.submit">Send message</span> 347 </button> 348 <div id="contact-msg" class="text-sm" hidden></div> 349 </form> 350 </div> 351 </div> 352 </section> 353 354 <section class="stack-list docs-faq" aria-label="FAQ"> 355 <h2 class="h3" data-i18n="contactPage.faq.title">FAQ</h2> 356 <details class="docs-faq__item" open> 357 <summary class="docs-faq__summary" data-i18n="contactPage.faq.q1">Do I need a polished proposal?</summary> 358 <div class="docs-faq__body"> 359 <p data-i18n="contactPage.faq.a1"> 360 No. A short note is enough. Tell us who you are, what you are building, and where you see overlap. We are 361 happy to start from a rough idea. 362 </p> 363 </div> 364 </details> 365 <details class="docs-faq__item"> 366 <summary class="docs-faq__summary" data-i18n="contactPage.faq.q2">Are you open to partnerships and integrations?</summary> 367 <div class="docs-faq__body"> 368 <p data-i18n="contactPage.faq.a2"> 369 Yes. Partnerships, agency workflows, integration ideas, and ecosystem conversations are all welcome. 370 </p> 371 </div> 372 </details> 373 <details class="docs-faq__item"> 374 <summary class="docs-faq__summary" data-i18n="contactPage.faq.q3">Is this page only for support questions?</summary> 375 <div class="docs-faq__body"> 376 <p data-i18n="contactPage.faq.a3"> 377 Not at all. You can use it for business development, product questions, integration requests, or general 378 feedback about the platform. 379 </p> 380 </div> 381 </details> 382 </section> 383 384 <aside class="card card--soft stack"> 385 <header class="card__header"> 386 <h2 class="h3" data-i18n="contactPage.cta.title">Have an idea but not the full plan yet?</h2> 387 </header> 388 <div class="card__body stack"> 389 <p class="text-lead" data-i18n="contactPage.cta.lead"> 390 Send it anyway. Good partnerships often start with one useful conversation. 391 </p> 392 <div class="cluster"> 393 <a href="/features" class="btn btn--ghost" data-i18n="contactPage.cta.features">See features</a> 394 <a href="/docs" class="btn btn--ghost" data-i18n="contactPage.cta.docs">Read docs</a> 395 <a href="/#register" class="btn btn--primary" data-i18n="contactPage.cta.register">Create account</a> 396 </div> 397 </div> 398 </aside> 399 </main> 400 401 <footer class="site-footer"> 402 <div class="page-shell footer-grid" data-onlogout> 403 <div class="footer-brand"> 404 <div class="brand" aria-label="ÐÑенд 301.st"> 405 <svg class="brand__logo" aria-hidden="true"> 406 <use href="#i-brand-301"></use> 407 </svg> 408 <span class="brand__text">301.st</span> 409 </div> 410 <p class="muted" data-i18n="layout.footer.description">Redirects and analytics.</p> 411 </div> 412 <nav class="footer-nav" aria-label="Footer navigation" data-i18n-aria="common.aria.footerNav"> 413 <a href="/integrations" class="btn-chip"> 414 <span class="icon" data-icon="mono/puzzle-outline"></span> 415 <span class="btn-chip__label" data-i18n="layout.nav.integrations">Integrations</span> 416 </a> 417 <a href="/projects" class="btn-chip"> 418 <span class="icon" data-icon="mono/layers"></span> 419 <span class="btn-chip__label" data-i18n="layout.nav.projects">Projects</span> 420 </a> 421 <a href="/domains" class="btn-chip"> 422 <span class="icon" data-icon="mono/dns"></span> 423 <span class="btn-chip__label" data-i18n="layout.nav.domains">Domains</span> 424 </a> 425 <a href="/redirects" class="btn-chip"> 426 <span class="icon" data-icon="mono/arrow-right"></span> 427 <span class="btn-chip__label" data-i18n="layout.nav.redirects">Redirects</span> 428 </a> 429 <a href="/sites" class="btn-chip">
430 <span class="icon" data-icon="mono/landing"></span> 431 <span class="btn-chip__label" data-i18n="layout.nav.sites">Sites</span> 432 </a> 433 <a href="/streams" class="btn-chip"> 434 <span class="icon" data-icon="mono/directions-fork"></span> 435 <span class="btn-chip__label" data-i18n="layout.nav.streams">Streams</span> 436 </a> 437 </nav> 438 </div> 439 <div class="page-shell footer-legal"> 440 <span data-i18n="layout.footer.copyright">© 301.st</span> 441 <span class="separator" aria-hidden="true">â¢</span> 442 <a href="/about" data-i18n="layout.footer.about">About</a> 443 <span class="separator" aria-hidden="true">â¢</span> 444 <a href="/partners" data-i18n="layout.footer.partners">Partners</a> 445 <span class="separator" aria-hidden="true">â¢</span> 446 <a href="/docs" data-i18n="layout.footer.docs">Docs</a> 447 <span class="separator" aria-hidden="true">â¢</span> 448 <a href="/privacy" data-i18n="layout.footer.privacy">Privacy</a> 449 <span class="separator" aria-hidden="true">â¢</span> 450 <a href="/terms" data-i18n="layout.footer.terms">Terms</a> 451 <span class="separator" aria-hidden="true">â¢</span> 452 <a href="/security" data-i18n="layout.footer.security">Security</a> 453 <span class="separator" aria-hidden="true">â¢</span> 454 <a href="/requisites" data-i18n="layout.footer.requisites">Legal Info</a> 455 <span class="separator" aria-hidden="true">â¢</span> 456 <a href="/contact" data-i18n="layout.footer.contact">Contact</a> 457 </div> 458 </footer> 459 460 461
461<script type="module" src="https://static.cloudflareinsights.com/beacon.min.js/v31edd6df95cf4e85bb4c19e7a9bdbcba1788362987495" integrity="sha512-iIg7k2xntmwu6/uSb5tpc/hySgZc4eoL31yB29W6tJFo2akwjPWcEqnCEdJvGexCL0KEQwVYv5BlowfhVz26hg==" data-cf-beacon='{"version":"2024.11.0","token":"75469f8135f44c809632930aeccdcd5b","r":1,"spa":2}' crossorigin="anonymous"></script>
461 462</body> 463</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.