Key takeaways
What is Lauth?
Lauth is a multi-account browser built on Chromium, developed by the Brazilian company JRX Internet and distributed at lauth.com.br. It arrived in 2024 and runs on Windows and macOS.
Each profile in Lauth runs as a fully isolated environment. It carries its own device fingerprint (user agent, Canvas, WebGL, audio, fonts, timezone, WebRTC, and resolution), its own cookies and local storage, and its own proxy IP. Lauth calls this isolation layer AdSafe. Because those signals do not overlap between profiles, you can operate many accounts side by side on one computer while keeping each one internally consistent and separate from the others.
That model puts Lauth in the same category as the tools covered in our roundup of the best antidetect browsers for multi-accounting. The proxy is the piece that completes the picture: the fingerprint separates the browser environments, and a dedicated IP per profile separates the network identity.
What is Lauth used for?
Lauth is used anywhere one operator needs to run several accounts that each look like a distinct, ordinary user. The most common jobs:
The unifying thread is legitimate multi-account management: many accounts, each kept in good standing under its own consistent fingerprint and IP, in compliance with each platform's terms.
Key features of Lauth
The features that matter most for proxy-backed multi-account work:
Is Lauth free to use?
Lauth offers a 7-day free trial with no credit card required. After the trial, it moves to paid plans that scale by the number of profiles you can run at once.
| Plan | Profiles | Best for |
|---|---|---|
| Starter | 10 | Solo operators and a first account set |
| Premium | 50 | Growing portfolios and small teams |
| Premium Plus | 300 | Agencies running many client accounts |
| Max | 1,000 | High-volume operations and resellers |
Plans are billed in Brazilian reais (R$), and prices change often, so confirm the current figures on the Lauth pricing page before you commit. Team seats are available as an add-on on the higher tiers. One thing the plans do not fully replace is a quality proxy network: Lauth bundles a proxy option, but most operators bring their own provider so they control the IP type per account, which is where Proxy-Cheap fits in.
How to install Lauth
Lauth ships desktop builds for Windows and macOS. There is no native Linux desktop build, so Linux users run it inside a virtual machine or a Windows environment.
Installation is quick:
Quickstart: create your first Lauth profile
Before you add a proxy, create a profile to attach it to. This takes under a minute.
Each Lauth profile is a separate environment with its own fingerprint and its own dedicated IP. One profile, one identity, one proxy.
At this point the profile uses your real connection. The next sections add a proxy so each profile has its own IP, which is the part that actually separates the accounts at the network level.
Why you need a proxy with Lauth
Lauth separates your accounts at the browser level, but every profile still leaves through the same connection until you add a proxy. Two profiles sharing one public IP are easy to associate, no matter how distinct their fingerprints are. Routing each profile through its own IP from a residential proxy network is what makes multi-account management hold up in practice.
Three concrete reasons to put a proxy on every Lauth profile:
Not every profile needs the same kind of proxy. The cards below map Proxy-Cheap product lines to the jobs people actually run in Lauth, and the best proxies for multi-accounting guide goes deeper on the tradeoffs.
Each product line fits a different profile type. The links below match the cards above.
For most Lauth operators the answer is Static Residential (ISP) or Mobile for the accounts that carry value, and Rotating Residential or Datacenter for research and bulk profiles.
How to set up a proxy in Lauth
Proxies live inside each profile, so you set them when you create or edit a profile. Here is the full path using manual entry, which is the only method Lauth offers.
A Lauth profile sends its traffic through the Proxy-Cheap proxy, reaches the target site from the proxy's IP, and returns the response to that single profile.
The one detail that trips up most first-time setups is the field split. Lauth's own help shows proxies in a single reference string, but the app expects each part in a separate box. Do not paste the whole string into the IP address field:
Reference string Lauth shows: http://45.128.10.20:8080:jdoe:pa55word
Enter it as separate fields instead:
Type HTTP
IP address 45.128.10.20
Port 8080
Username jdoe (turn on "Proxy requires authentication")
Password pa55word
Proxy-Cheap delivers credentials in exactly this shape. Rotating residential uses a single shared hub, thehub.proxy-cheap.com:8080, with your username and password, and you choose the country in the dashboard credential generator. Static products (residential/ISP, datacenter, and static mobile) assign a unique host and port to each proxy, which you copy straight from the dashboard. If you are new to the panel, the Proxy-Cheap dashboard guide shows where those credentials appear.
IP whitelist as an alternative to username and password. Static Residential (ISP), datacenter, and static mobile products support IP allowlist authentication. If you prefer not to store credentials in the profile, add your current public IP to the allowlist in the Proxy-Cheap dashboard and leave Proxy requires authentication turned off in Lauth. Re-add your IP whenever your own ISP address changes. IP whitelist is not offered on rotating residential, which uses username and password.
Rotating proxies with Lauth
Rotation works one of two ways in Lauth, and the right choice depends on whether the profile needs a steady IP or a fresh one each time.
Because Lauth has no bulk proxy import, the reusable proxy list is how you scale without retyping. Save each Proxy-Cheap endpoint once, then pick it from the list when you edit a profile, mapping one distinct proxy to each account so no two profiles share an address.
For a full breakdown of when each type fits, see static vs rotating proxies. The short version for multi-accounting: identity accounts want one steady IP, while research and bulk profiles benefit from rotation.
Advanced: matching each profile's identity to its proxy
A proxy only helps if the rest of the profile agrees with it. When the IP exits in one country but the profile reports another timezone, language, or WebRTC address, the signals look inconsistent, and inconsistency is what puts accounts at risk. Three habits keep a Lauth profile coherent:
After you set a proxy, verify the whole picture: open the profile and load an IP checker to confirm the exit IP and country, then run a WebRTC and DNS leak test to confirm every signal matches the proxy. This two-step check catches the majority of account-consistency problems before they matter.
Common errors and how to fix them
Most proxy problems in Lauth fall into a handful of buckets. Each has a clear fix.
1. The whole proxy string was pasted into one field. Lauth has no import, so a value like host:port:user:pass dropped into the IP address box never resolves. Split it: bare host or IP in IP address, the number alone in Port, and the login in the username and password fields after you enable Proxy requires authentication.
2. Authentication fails or Test proxy returns no IP. Usually the Proxy requires authentication toggle is off, so Lauth sends the request with no credentials. Turn it on, then enter the username and password from your provider dashboard (not your Lauth account login) in the fields that appear, and re-test.
3. Test proxy fails even though the credentials are correct. The Type dropdown does not match the endpoint. HTTP, HTTPS, SOCKS4, and SOCKS5 are not interchangeable, and providers often serve different protocols on different ports. Match the dropdown to what the provider issued, confirm the port belongs to that protocol, and re-test. If unsure, try SOCKS5 first, since it also routes DNS through the proxy.
4. Authentication keeps failing no matter what. The proxy may use IP-whitelist authentication instead of a username and password. Add your current public IP to the allowlist in the provider dashboard, turn Proxy requires authentication off in Lauth, and enter only host and port. Re-whitelist whenever your home IP changes.
5. Test proxy passes, but the profile still shows your real IP. The change was tested but not fully saved, or the profile was open before the save. Save the connection settings, save the profile with Save changes, then fully close and relaunch the profile. Verify on an IP checker that the displayed IP equals the proxy IP.
6. A stray space or hidden character breaks the connection. A trailing space after the port or an invisible line break from a dashboard copy is enough to fail the check. Retype or carefully paste each field, delete any leading or trailing whitespace, and confirm the port is digits only.
7. The exit IP is in the wrong country, or a leak still shows your home IP. The IP itself may be in the wrong region, or the profile's WebRTC and DNS are leaking your real address. Request an IP in the target country, set the profile timezone to automatic, point WebRTC at the proxy IP, and confirm on a WebRTC and DNS leak checker that every signal matches the proxy.
Is Lauth good? Pros and cons
For legitimate multi-account management, Lauth is a capable option in its class. The fingerprint isolation is thorough, the proxy support is broad, and the 7-day trial lets you test a full workflow before paying. A few tradeoffs are worth weighing.
Pros
Cons
The practical setup for most teams: run Lauth for the fingerprint isolation, pair it with a value-tier provider on pay-as-you-go pricing, and assign one dedicated IP per profile. That covers the vast majority of multi-account workflows without enterprise overhead. Residential IPs are the default starting point for most Lauth accounts, with mobile or ISP for your highest-value profiles and datacenter for speed-first tasks.
