What a mobile sneaker bot is, and what a phone cannot do

Start with the word “bot”, not the word “mobile”

A sneaker bot is software that buys limited releases faster and more often than a person can. The classic version runs on a Windows desktop or a rented Windows server, and it does four things at once. It watches a retailer for a product to go live. It holds a stack of saved checkout profiles. It routes each attempt through a different proxy address, so the retailer sees many shoppers rather than one machine. Then it submits the checkout the instant stock appears.

That last part is the whole point. On a first come, first served release, the gap between a pair and nothing is a few hundred milliseconds, and a script wins that by default.

Everything else in a desktop bot exists to keep the script alive. Proxies are there because retailers rate limit a single address. Server hosting is there because a laptop on home Wi-Fi is slower and goes to sleep. High task counts are there because one attempt is not worth the setup. Renewal keys are there because retailers change their sites and the software has to be patched to keep up. Running a desktop bot well is a small operations job, and the people who do it well treat it like one.

What actually changes when the job moves to a phone

Four things change, and only one of them is about speed.

Distribution changes. A desktop bot is a file you download from a vendor’s website. A phone app arrives through the App Store or Google Play, which means a review before the first install, a named developer entity on record, an automatic update channel and a refund process that is not an email to the vendor. That shift is large enough to deserve its own page, so the detail is in how iOS distribution changes what you can buy.

The proxy stack disappears. Proxies solve a problem created by volume. One phone, one account, one entry has no volume to spread, so there is nothing to rotate and nothing to rent. This is the difference the category advertises, and it is real.

The background disappears. iOS and Android both suspend apps that are not in front of you. A phone app cannot sit in a loop for six hours waiting for a restock the way a process on a server can. Anything a phone app does at a scheduled moment, it generally does because you opened it and started it.

The scale disappears. This is the part the category’s marketing tends to skip, so it gets its own heading below.

What a phone genuinely cannot do

Here is the unflattering part. A phone is not a quiet substitute for a desktop setup. Four capabilities do not survive the move.

Concurrency. A desktop all-in-one bot is sold on task counts, because hundreds of simultaneous attempts across a release is the mechanism. A phone runs one thing at a time, on one connection.

Unattended operation. A server runs while you sleep, in a different time zone, without you. A phone runs when it is charged, unlocked and in your hand.

Retailer coverage. Every retailer needs its own integration, and desktop vendors compete on the length of that list. Cybersole publishes support for more than 1,350 stores. A focused mobile app usually supports exactly one release process, and says so.

Raw checkout speed. On a first come, first served drop, a desktop bot on a fast connection will get there before you, and before your phone. There is no polite way to soften that.

If your goal is volume across many retailers, a desktop setup is the tool for the job, and a phone app is not a smaller version of it. It is a different thing.

The reason the category exists anyway

Most of the pairs people actually chase on Nike do not go out first come, first served. They go out as a Draw: an entry window opens, it closes at a published time, and Nike selects winners at random from everyone who entered inside it. Speed cannot win a random selection. Our full explanation of the mechanics is in how Nike SNKRS draws work.

That single fact redraws the whole comparison. For a Draw, the capabilities a phone loses are the capabilities that were not worth anything here, and the capabilities a phone keeps, a calendar in your pocket and billing already validated, are the ones that decide whether you are entered at all.

The other half of the picture is Nike. Nike says it sees roughly 12 billion bot calls a month against SNKRS, and estimates automated traffic at between 10 and 50 percent of all entries on a given release. Nike’s Terms of Use also restrict automated access to its services. If you are weighing any tool in this category, read those terms yourself rather than trusting a vendor’s summary of them, ours included.

A correction to the older version of this page

The version of this article that ran on our previous site defined the category correctly and then said Laced was one of these tools. Two sections later, the same page said Laced does not use bots, proxies or automated checkout scripts. Both sentences cannot be true, and the second one is the accurate one.

So, the settled position. Laced does not automate checkout, because a Draw has no checkout to win: it closes and picks at random. What Laced does is put multiple entries into that Draw. You add a profile, a card and a shipping address, it validates in up to sixty seconds, and you pick releases and sizes from a seven-day calendar. The work that sits behind an entry, including the accounts and the infrastructure they run on, is Laced’s rather than yours, which is described in how Laced works under the hood. The step-by-step walkthrough has the rest.

The mechanism is more entries, through more profiles. It is not better odds on any one entry, and nothing sold by anybody changes that number. One profile is free, and the paid plans are auto-renewing subscriptions that add profiles. If you want to see what the category charges for the desktop version of this problem, we put the published numbers side by side in what sneaker bots cost in 2026.

How to decide, in three questions

Are you buying across many retailers, or one? Many retailers means desktop. One release process means a focused tool is enough.

Is the release a Draw or a race? A race rewards speed and infrastructure. A Draw rewards being entered, with working payment details, before the window shuts.

How much operations work do you actually want? Proxies, servers, renewals and patch cycles are a real time cost on top of a real money cost. Some people enjoy that. Most people asking this question do not.

If you land on the mobile side of all three, Laced is built for that narrow case and nothing wider.

The short version

A mobile sneaker bot is the category term for checkout automation running on a phone. The phone version trades concurrency, unattended running, retailer coverage and raw speed for simplicity and store distribution. On a first come, first served drop that trade is bad. On a SNKRS Draw, where selection is random at the close, most of what was traded away was never worth anything.