Migration
Outgrowing Multilogin.The fleet is the part you cannot buy.
Multilogin has the strongest mobile story in this category and no way for you to run any of it. If your next problem is where the browsers execute and who holds the profile records, this is the comparison.
Every claim about Multilogin on this page links the page it came from, read on 2026-07-27.
- Rows compared
- 31
- Rows unverified
- 5
- Things Multilogin does better
- 5
- Sources read on
- 2026-07-27
01Their ceiling
Why teams leave
Where Multilogin stops
- Custody
Profile metadata is always on AWS
Their storage documentation states profile metadata is stored on AWS even when you choose local storage for the profile data itself. There is no self-hosted deployment, so the platform cannot operate without their cloud. - Mobile
Cloud phones are theirs, and metered
Android runs on Multilogin's infrastructure and is billed by the mobile minute on top of the subscription, at $0.011 a minute. Cost tracks usage rather than fleet size, and mobile profiles cannot be stored locally at all. - Teams
Seats start at the third paid plan
Free, Pro 10 and Pro 50 include no team seats. Pro 100 includes two, and unlimited seats arrive with Business. A team of three means moving up two plans rather than sending an invitation. - Automation
The launcher owns the endpoint
Automation runs through Multilogin's launcher, which returns a per-framework automation port once you declare selenium, puppeteer or playwright. A raw CDP endpoint you hold yourself is not documented as a separate surface.
02Full table
Row by row
31 rows against Multilogin
| What is compared | VeilBrowserOurs | Multilogin |
|---|---|---|
| Where it runsWhich machines execute the browser, and whose infrastructure holds the data. | ||
| Browser execution locationThe machine the Chromium process actually runs on. | The customer's own machine, or a customer-operated worker fleet. Only the local API spawns browser processes. The cluster manager load-balances launches across worker hosts with an OpenResty least-connections upstream; it never runs browsers itself. VeilBrowser local-api browser service, read from our codebase on 2026-07-27 | Browser profiles launch in the Multilogin desktop app on the user's machine. Cloud Phones run on Multilogin's infrastructure. |
| Self-hostable control planeCan the management plane run on customer infrastructure at all. | Yes One command, one input. The installer states the org API key is the only required value. VeilBrowser cluster-manager installer, read from our codebase on 2026-07-27 | No No self-hosted option is offered. Profile metadata is always stored on AWS, including for locally stored profiles, so the platform cannot operate without Multilogin's cloud. |
| Self-hostable browser fleetCan a pool of browser workers be operated by the customer. | Yes Worker hosts are registered as fleet hosts and receive launches through the cluster manager's load balancer; per-worker concurrency is capped by VEIL_MAX_BROWSERS. VeilBrowser cluster load balancer template, read from our codebase on 2026-07-27 | No Profiles run on operator desktops or Multilogin's cloud phones. There is no customer-operated worker fleet. |
| Where profile data lives | Partial Sessions, fleet state and profile bundles stay on customer disks in per-host SQLite. Accounts, organisations and cloud profile configuration currently live in the vendor-hosted PostgreSQL, and workers fetch profile config from it at launch. VeilBrowser architecture decisions, read from our codebase on 2026-07-27 | Profile metadata always on AWS. Profile data such as cookies and extensions either on AWS or on the operator's device, chosen per profile. Local profile paths are documented for Windows, macOS and Linux. Mobile profiles are always cloud-based and cannot be stored locally. |
| Platforms and mobileWhat a profile can present itself as, and whether mobile means a real device. | ||
| Profile OS targetsThe operating systems a profile can present, not the OSes the app installs on. | win, mac, linux, android Canonical enum in the shared schemas. The dashboard profile form currently omits android, which is a UI gap rather than a platform limit. VeilBrowser shared Zod schemas, read from our codebase on 2026-07-27 | Windows, macOS and Linux for browser profiles; Android for cloud phones. Derived from the documented local profile storage paths and the cloud phone product. |
| Android profiles | Partial Android is a profile fingerprint target with real device models resolved from installed profile bundles. It is not a hosted Android device. VeilBrowser profile bundle service, read from our codebase on 2026-07-27 | Yes Cloud Phones support Android 10 through 16, selectable per profile, with locations in 190+ countries. Billed by mobile minute. |
| iOS profiles | No No iOS target exists in the OS enum. | No Only Android cloud phones appear on their pricing and product pages. Recorded as absent rather than confirmed unavailable. |
| Real devices or emulationWhether mobile support is hosted hardware or a spoofed fingerprint. | Emulation only, on worker-hosted Chromium. No cloud phone or real-device fleet exists anywhere in the codebase. VeilBrowser shared Zod schemas, read from our codebase on 2026-07-27 | Multilogin states Cloud Phones are not an emulator and run Android on real smartphone hardware.Their claim This is their claim and is not independently verifiable. Quote it, do not assert it. |
| Automation surfaceHow code drives the browser, and what a subscription gates. | ||
| Chrome DevTools Protocol access | Yes Launch returns a standard `ws://127.0.0.1:<port>/devtools/browser/<id>` endpoint. VeilBrowser local-api browser service, read from our codebase on 2026-07-27 | Partial The launcher returns an automation port after you declare an automation_type of selenium, puppeteer or playwright. A raw CDP endpoint is not documented as a separate surface. |
| Puppeteer | Yes Connects to the returned CDP WebSocket endpoint directly. VeilBrowser local-api browser service, read from our codebase on 2026-07-27 | Yes |
| Playwright | Yes connectOverCDP against the returned WebSocket endpoint. VeilBrowser local-api browser service, read from our codebase on 2026-07-27 | Yes |
| Selenium | Partial Works through the same debug port via Selenium's debuggerAddress, but there is no Selenium-specific code path or worked example in the repository yet. VeilBrowser local-api browser service, read from our codebase on 2026-07-27 | Yes Remote WebDriver only. Multilogin states a local WebDriver will break automation. |
| REST API | Yes Cloud routes under /v1 for profiles, organisations, sessions, plans and billing; local routes for sessions, profiles, fleet and cluster operations. VeilBrowser SaaS API routes, read from our codebase on 2026-07-27 | Yes A cloud API for profiles, folders, proxies and extensions, plus a local launcher API on the operator's machine. |
| First-party typed SDKA vendor-maintained, typed client library, not community samples. | Yes @veil/api exposes typed Eden clients for both the local and cloud APIs, derived from the server types. VeilBrowser typed API client, read from our codebase on 2026-07-27 | Unknown A CLI, a script runner and framework examples are documented, but no first-party typed client library was found. |
| API needs a paid plan | Not summarised Ours to answer, and we cannot yet. The gate exists in the plan definitions and is not enforced by the API, so either answer would be falsifiable. | Yes The Free plan has no API access. The FAQ says API access is included with all Pro and Business plans starting at Pro 10, while the plan table shows rate limits only from Pro 50. The two disagree. |
| Published API rate limits | Base 50/min and 500/hour, Team 100/min and 1,500/hour, Advanced 200/min and 3,000/hour. VeilBrowser plan seed, read from our codebase on 2026-07-27 | 50 requests/minute at Pro 50, 100 at Pro 100, 100 with custom limits available on Business. Pro 10 has no published limit. A legacy Multilogin 6 help page still claims API access in all plans, which the current pricing page contradicts. |
| Proxies and identity coherenceProtocol coverage, per-profile assignment, and whether the identity follows the exit IP. | ||
| Proxy protocols | http, https, socks5, socks5h socks5h keeps DNS resolution at the proxy exit. One local service still parses a legacy socks4 value that is not in the canonical schema. VeilBrowser shared Zod schemas, read from our codebase on 2026-07-27 | HTTP, HTTPS and SOCKS5 for custom proxies. Built-in Multilogin proxies can be created as HTTP or SOCKS5. SSH tunnels are not documented. socks5h is not offered. |
| Per-profile proxy assignment | Yes Each profile stores its own proxy, and a launch may pass a per-session override. VeilBrowser shared Zod schemas, read from our codebase on 2026-07-27 | Yes Multilogin recommends a different proxy per profile, and supports pasting a list of up to 25 proxies assigned sequentially or randomly. |
| Timezone, locale and geolocation from the exit IPWhether the profile derives IP-dependent values automatically. | Yes Derived by the browser build rather than by the platform API, which is why it is not visible in an API surface. The browser core's CLI reference documents timezone, locale, languages and location as IP-based by default, with flags that exist only to override the automatic behaviour. Auto-detection requires the proxy to arrive as --proxy-server, which is how the launch path passes it. VeilBrowser local-api browser service, read from our codebase on 2026-07-27 | Yes Multilogin describes a passing proxy check as having “connected to your proxy and got the required IP-dependent data”, and their guidance is to keep timezone, geolocation and languages aligned to the proxy. |
| Proxies sold in-product | No No proxy purchasing, traffic metering or bundled IP pool exists. VeilBrowser shared Zod schemas, read from our codebase on 2026-07-27 | Yes Residential and mobile proxy traffic is included monthly on paid plans, with country and city targeting and pay-as-you-go top-ups at $3.50 per GB. |
| Rotation / change-IP URL | No No change-IP URL, rotation scheduler or proxy health check in code. VeilBrowser shared Zod schemas, read from our codebase on 2026-07-27 | Partial Proxy lists can be consumed sequentially or randomly across profiles, but no per-proxy change-IP URL is documented for custom proxies. |
| Teams and access controlSeats, permission granularity and what an operator can audit. | ||
| Team seats | 1, 2, 5, 15 and 50 seats from Lite through Advanced. Enforced on invite against the organisation's member limit. VeilBrowser plan seed, read from our codebase on 2026-07-27 | None on Free, Pro 10 and Pro 50. Two on Pro 100. Unlimited on Business. |
| Permission granularity | Three organisation roles: owner, admin, member. The self-hosted cluster manager has its own admin, operator and viewer roles. Coarser than a per-action permission matrix; there is no per-profile or per-folder scoping. VeilBrowser SaaS Prisma schema, read from our codebase on 2026-07-27 | Advanced team management, profile sharing and profile transfer are listed as Business features. No per-action permission matrix is published, so the granularity cannot be compared directly. |
| Activity / audit log | Partial The self-hosted cluster manager records fleet operations. The cloud side has an auditLogs plan flag but no audit log model or endpoint. VeilBrowser plan seed, read from our codebase on 2026-07-27 | Partial Workspace activity logs are listed on the pricing page as coming soon. |
| Two-factor authentication | No Not offered. Account login is email and password plus Google or GitHub OAuth, with no second factor. All three competitors publish two-factor authentication, so this is a gap rather than a decision about what the product is for. VeilBrowser auth configuration, read from our codebase on 2026-07-27 | Yes Listed on every plan including Free. |
| SAML / OIDC single sign-on | No An sso plan feature flag exists, but there is no SAML or OIDC implementation. Google and GitHub OAuth cover user login only. VeilBrowser plan seed, read from our codebase on 2026-07-27 | Unknown No SAML or OIDC offering found on their pages. |
| Compliance and trustOnly certifications and statements the vendor publishes themselves. | ||
| SOC 2 | No No attestation. | Unknown No attestation published on their own site. |
| ISO 27001 / 27701 | No No certification. | Unknown No certification published on their own site. |
| Published GDPR position | Unknown No published position to cite yet. Legal review pending. | Not summarised Their own published pages do not agree here, and the question is a legal one rather than a product one. We do not summarise it in either direction. |
| Customer control over data location | Partial A self-hosted deployment keeps fleet state, sessions and profile bundles on customer infrastructure in a chosen location. Account and cloud profile records still sit in the vendor database, so this is not yet full residency control. VeilBrowser architecture decisions, read from our codebase on 2026-07-27 | Unknown No page of theirs names a storage region you can choose, so this is recorded as unverified. Descriptions of their data centres published by third parties are not first-party sources and are not used here. |
| Publishes comparison pages | No | Yes Dedicated compare pages against AdsPower, Octo Browser and XLogin, plus blog round-ups against GoLogin. |
Reading the table
- Yes
- Documented and available.
- Partial
- Available with a documented limit, named in the cell.
- No
- Documented as absent, or absent from every page we read.
- Unknown
- Not verifiable from their own pages. Not the same as absent.
- Not summarised
- Their published pages do not agree, so we do not characterise it.
03Where they win
Conceded
Where Multilogin is stronger
- Cloud Phones are a real product VeilBrowser has no answer to: hosted Android environments across many countries, able to run native apps.
- Built-in residential and mobile proxy traffic is included in every paid plan, so a customer never has to source proxies separately.
- Two browser engines, a Chromium build and a Firefox build, give fingerprint diversity VeilBrowser does not offer.
- Their entry pricing is below ours: a permanent free plan with five profiles, and a paid plan from $7.08 a month on annual billing.
- Ten years in market, 24/7 support in five languages, and an established detection track record.
None of this is hedged. If one of these is the thing your work depends on, the honest recommendation is to stay where you are.
04Price
Their list, and ours
What Multilogin costs, and what we cost
| Plan | Monthly | Annual, per month | Profiles | Seats | API rate limit |
|---|---|---|---|---|---|
| FreeCloud profiles only. Auto-deleted if no profile is started for 7 days. One-time 200 MB proxy traffic and 30 mobile minutes. | Free | Free | 5 | None | No API access |
| Pro 101 GB proxy traffic and 60 mobile minutes monthly. | Unpublished | $7.08 | 10 | None | Unpublished. The FAQ says API access starts at Pro 10; the plan table lists no rate limit for this plan. |
| Pro 503 GB proxy traffic and 75 mobile minutes monthly. | Unpublished | $19.17 | 50 | None | 50 requests/minute |
| Pro 1005 GB proxy traffic and 150 mobile minutes monthly. | Unpublished | $26.67 | 100 | 2 | 100 requests/minute |
| Business (from 300 profiles)10 GB proxy traffic and 450 mobile minutes monthly. Scales in steps to 10,000 profiles. | Unpublished | $57.08 | 300 | Unlimited | 100 requests/minute, custom limits available |
| Business (10,000 profiles)Above 10,000 profiles is quoted by their sales team. | Unpublished | $573.75 | 10,000 | Unlimited | Custom |
What the Multilogin list price does not say
- Prices shown are the annual-billed monthly equivalent. Multilogin states annual billing is 35% cheaper than monthly; the monthly-billed figures were not captured, so they are recorded as unknown rather than derived.
- VAT may be added in some countries, so the checkout total is regional.
- Multilogin restructured pricing in July 2026 and introduced the free plan then. This is a young price list and likely to move.
- Mobile minutes and proxy traffic are metered separately at $0.011 per mobile minute and $3.50 per GB, so a plan price is not the whole cost of a mobile workflow.
- Multilogin's own blog posts quote entry prices in euros (€5.85 and €9), which do not reconcile with the dollar pricing page. Use the pricing page only.
VeilBrowser
Our plans scale by profiles, seats and API volume, and seats are part of the plan rather than a separate purchase. The amounts live on the pricing page, which reads the live plan records instead of a marketing table.
Enterprise starts at $5,000 and covers the self-hosted deployment, the fleet size you need and the support around it. No billing period is quoted on that number because the scope decides it.
05Switching
The move
What moving actually involves
- 01
Describe the devices you need
An operating system target, a Chrome major between 135 and 150, an optional Android model and a proxy. Creation is one profile per call, from the API or the dashboard, so a set of forty is a short script, and a browser build is matched and pinned to each one. - 02
Point the proxies you already have at them
One proxy per profile over HTTP, HTTPS, SOCKS5 or SOCKS5H. Nothing has to be bought here, because no proxy traffic is sold here: your existing proxy strings move across as they are. - 03
Run a worker on a machine you own
One container on one host is enough to start, and the same image is what a larger fleet is made of. Browsers execute there rather than on our infrastructure. - 04
Reconnect the automation
A launch returns a standard CDP WebSocket endpoint, so Puppeteer connects to it and Playwright attaches over CDP with no vendor shim. Selenium works through the same debug port, though there is no worked example in our documentation yet.
What does not move
- Cookies and signed-in sessions do not transfer. There is no importer for another platform's profile export, so a profile that is already logged in somewhere logs in again here.
- Fingerprints are not copied across. A profile here is a browser build plus a route, so an identity is recreated rather than migrated, and it is a new device from its first launch.
- There is no hosted mobile device and no proxy traffic for sale. If either is load-bearing in your current workflow, it stays outside this platform.
- We hold no security certifications. If your review requires an attestation from the vendor rather than control of the infrastructure, that is a blocker today and we will say so on the call.
The part of Multilogin with no equivalent here is Cloud Phones. If hosted Android devices are load-bearing for your work, this migration is a downgrade, and the concessions above say so in more detail.
The getting-started path is public documentation, so the whole migration can be read before anyone asks you for a decision.
06Sources
Footnotes
What we read about Multilogin, and what we could not settle
Multilogin in their own words
“Cloud Phones & Browser Profiles in One Platform” — grow social media accounts with Android cloud phones, uploading content and automating posts and engagements from one dashboard.
Rows we could not verify (5)
- First-party typed SDK
- A CLI, a script runner and framework examples are documented, but no first-party typed client library was found.
- SAML / OIDC single sign-on
- No SAML or OIDC offering found on their pages.
- SOC 2
- No attestation published on their own site.
- ISO 27001 / 27701
- No certification published on their own site.
- Customer control over data location
- No page of theirs names a storage region you can choose, so this is recorded as unverified. Descriptions of their data centres published by third parties are not first-party sources and are not used here.
Multilogin pages read
- Multilogin pricing
- Multilogin profile storage help article
- Multilogin custom HTTP and SOCKS proxies
- Multilogin automation FAQ
- Multilogin privacy policy
Multilogin publishes 5 comparison pages of their own. This is the same exercise run in the other direction, with the sources attached.
Outgrowing Multilogin?
Tell us which ceiling you hit and what you run against. If VeilBrowser does not clear it, the call is short and nobody has lost an evaluation cycle.
- The difference
- The fleet runs on your machines, and the control plane can too
- Conceded
- Multilogin has real advantages, listed above and not hedged
- Entry
- Pick a plan, or enterprise from $5,000
Every competitor claim on this page is dated and linked to the page it came from.