Do you support sticky sessions for sneaker bots?

Yes. Append a session ID to the username and you'll get the same IP for up to 30 minutes — long enough for any cart → checkout flow, even on slow CAPTCHA or queue sites.

Will these work on Footsites, Shopify and SNKRS?

Yes — datacenter for Shopify and most Footsites releases, ISP or residential for SNKRS and Yeezy Supply (which run heavier IP scoring). You can mix types per task in any major bot.

Are there per-bot setup guides?

We publish drop-in configs for Cyber, Wrath, Valor, Kodai, MEKsneakers, NSB, Tohru and more. Reach out in chat and we'll walk you through it before your next drop.

← Rift // HomeUC—03 / DROP

§ Use Case — Sneakers

Drop-day ready
checkout proxies.

Q: What format do you export proxies in?

ip:port:user:pass — the universal sneaker bot format. Generate any number of session-locked proxies from the dashboard, copy-paste into your bot, and you're live.

Sub-second datacenter and ISP pools tuned for sneaker drops on Footsites, Shopify, Yeezy Supply, SNKRS and Supreme. Sticky checkout sessions, no subnet bans, plug-and-play with Cyber, Wrath, Valor, Kodai, MEKsneakers and homegrown bots.

Open the Rift

See pricing

§ Pillars

Why operators run this stack on Rift.

Sub-second checkout

<200ms p50 latency from drop-region datacenters. Beat humans and competing bots to the cart-add and checkout calls.

No subnet bans

Diversified ASN footprint across 25+ countries. Footsites, Shopify and SNKRS subnet sweeps don't touch your pool.

Sticky sessions

Lock an IP through cart → checkout → confirmation. No mid-flow IP rotation breaking your session token.

Datacenter

Datacenter + ISP

Drops are won in milliseconds. Datacenter delivers sub-200ms latency from drop regions at $1/GB — residential is too slow for cart races, mobile is overkill. For SNKRS and high-detection sites, layer in ISP.

City + ASN targeting
Sticky sessions up to 30 min
Zero-log, ethically sourced
HTTP / HTTPS / SOCKS5

Configure Datacenter

Drop-in snippet

JSON

// Generic sneaker bot proxy list format
[
  "gateway.riftproxy.com:7777:user-type-dc-region-us-session-task1:KEY",
  "gateway.riftproxy.com:7777:user-type-dc-region-us-session-task2:KEY",
  "gateway.riftproxy.com:7777:user-type-dc-region-us-session-task3:KEY"
]
// Each session = sticky IP for the full checkout flow

Works with Puppeteer, Playwright, Selenium, Scrapy, cURL and every commercial scraping platform.

§ Decoded

Niche questions.

§ The drop-day playbook

How copping crews run drops on Rift

Sneaker drops are decided in the first three seconds. The bot that lands an in-cart request before stock-counter sync wins; everything else loses. Rift's datacenter pool is built around that single constraint — sub-200ms p50 latency from the same regions where Shopify, Footlocker, JD Sports and Yeezy Supply run their edge, with diversified ASN allocations so the subnet sweeps that hit cheap providers on every major drop never touch your task pool.

Datacenter, ISP and residential — what to use where

Datacenter is the workhorse: $1/GB, unlimited concurrency, ~150ms latency from the right region, and clean ASN footprint that flies through Shopify, Demandware, SFCC and most Footsites releases. ISP layers in for SNKRS, Yeezy Supply and any drop where the platform runs heavier IP-reputation scoring — same low-latency profile but on consumer-ISP registered subnets that don't carry the "datacenter" risk tag. Residential is the fallback for the hardest drops (Supreme, Palace, hype web stores running DataDome) where even ISP gets soft-banned within a few hundred attempts.

Sticky sessions for the full checkout flow

Every commercial sneaker bot models the drop as a state machine: monitor → ATC → checkout → confirmation, plus optional CAPTCHA-solver detours. Mid-flow IP rotation breaks the session token on most sites, instantly invalidating the cart and burning the task. Rift's session strings (for example user-type-dc-region-us-session-task42) lock an IP for up to 30 minutes, so a single task holds the same exit from monitor all the way through to the confirmation page even when the queue page sits open for 10+ minutes. Generate one session per task and you can run hundreds of parallel cooks with no cross-contamination.

Bot compatibility — Cyber, Wrath, Valor, Kodai and the rest

Rift exports proxies in the universal ip:port:user:pass format that every commercial sneaker bot ingests natively — Cyber AIO, Wrath AIO, Valor AIO, Kodai, MEKsneakers, NSB, Tohru, Project Destroyer, Sole AIO, Stellar AIO, Cybersole legacy and homegrown Selenium / Puppeteer / Go scrapers. Generate any number of session-locked proxies from the console, paste into the bot's proxy manager, assign per-task and you're live. For bots that support per-site proxy groups (Cyber, Wrath, Valor) you can mix datacenter and ISP within the same task list and route SNKRS through ISP while Shopify stays on datacenter.

Pricing, billing and drop-day support

Datacenter starts at $1/GB on the SOCKS5 budget plan and the full rotating datacenter pack — a typical shoe drop runs 30-80MB per task across monitor, ATC and checkout, so a full 50-task setup costs cents per drop. Bandwidth credits never expire within 90 days, so buying a Pro pack ahead of release calendar season locks your cost in. Drop-day support runs live on Discord — when something goes sideways at 9:58am EST, an engineer is on the channel within minutes.

Open the rift. Tonight.

Spin up a key in 60 seconds. Pay-as-you-go, no commitment, no logs.

Launch Console

Drop-day readycheckout proxies.