The words, in plain words.

A saved iPhone identity. A profile keeps its logins, cookies, and history across every run — so to a website, each profile looks like the same physical phone coming back, every session, every time.

A profile, running live. Starting a session spins up a real iPhone Safari browser in the cloud with that profile's identity and history loaded. Stop it, and the profile remembers everything for next time.

Sessions running at the same time — think browser tabs open at once. Driftstack plans are priced on the concurrent cap (each tier also sets how many profiles you can store): within it, hours, clicks, and page visits are unmetered.

A relay your session's traffic travels through, so a website sees the relay's address instead of the session's own — which would otherwise be our data center's. In Driftstack you attach your own proxy per profile — each phone browses from its own corner of the world.

Like a proxy, a way to give traffic a different exit — but as an encrypted tunnel that carries everything the device sends. Driftstack profiles accept your own VPN configuration as an alternative to a proxy.

Your session's own internet exit — where its traffic actually leaves for the open web. Driftstack routes a session's traffic through the exit you attach (proxy or VPN), and the phone's language and clock (locale and timezone) follow the exit's location so nothing contradicts the address a website sees. What's live versus rolling out is documented at /trust/security-overview.

What a website can measure about a visitor — screen size, fonts, graphics quirks, dozens of small signals — combined into a picture stable enough to recognize a device it has seen before, even without cookies.

One fingerprint signal: a page asks the browser to draw an invisible picture, then boils the pixels down to one short value. Different engines draw slightly differently, so the value betrays what's really rendering. Driftstack sessions return the value a real iPhone returns, because the same engine draws the picture.

The one-line introduction a browser sends with every request — "I'm Safari on an iPhone." It's trivial to fake, which is exactly why serious detection systems don't trust it and measure the fingerprint instead.

The browser engine Apple ships on every iPhone — Safari is built on it. Driftstack sessions are built from Apple's WebKit source, so what a website measures matches what a real iPhone would return.

A specific iPhone model + iOS version + Safari version combination — say, an iPhone 17 on iOS 18.7 with Safari 26.4. Every Driftstack profile is built on an archetype, so each measurable detail agrees with a phone Apple really shipped.

A browser built so websites can't link or block its users by fingerprint. Most anti-detect tools disguise a desktop browser as something else; Driftstack takes the other path — running the real iPhone engine, so there's no disguise to spot. The comparison page walks the difference signal by signal.

A browser running without a visible window, driven by code — the standard tool for automation and data collection. Classic headless browsers leave measurable tells, and detection systems look for those tells specifically.

Software pretending to be other hardware. Driftstack sessions are not emulated iPhones — they run Apple's real browser engine on Apple-silicon hardware, the same chip family as the iPhone, which is why the measurements come out right.

A ready-made library for driving Driftstack from your own code — first-party in TypeScript, Python, and Go, on top of a plain HTTPS API any HTTP client can call. If you'd rather not code, the desktop app does the same things with clicks.

Bring Your Own Key. Driftstack's optional AI agent can use the key from your own AI-provider account (for example Anthropic) — the AI usage is then billed to you by your provider, with no Driftstack markup — instead of paying the bundled rate on one Driftstack invoice.

Running the Driftstack stack on Mac hardware you own. Session content stays inside your network; we supply the software, orchestration, and hands-on onboarding. The packages are on /self-hosted.

Giving a fresh profile some ordinary browsing history before it goes to work, so it doesn't look brand-new the day it matters. Driftstack's Warm-up Scheduler will automate this on a curve — light touches first, deeper flows later.