NeAntik: a free local antidetect browser for Apple Silicon Macs
Бесплатный антидетект браузер для Mac с Apple Silicon: локальные профили, встроенный Chromium, прокси и Keychain — без аккаунта, облака и телеметрии.
At a glance
- What is it?
- NeAntik is an open source, Mac-only antidetect browser that runs a bundled Chromium and keeps each profile's cookies, storage and proxy settings local. It is a public alpha for developers and QA engineers, not a tool for evading platform rules.
- Who is it for?
- Adopt NeAntik if you are on an Apple Silicon Mac running macOS 14 or newer, you want separate cookie and storage stores per profile, and you are willing to read a SwiftUI codebase to understand what the fingerprint seed actually changes. Skip it if you need Windows or Intel support, cloud launches, team seats, RPA or a write API; the README lists those as out of scope for the current product.
- Can I use it commercially?
- Yes, with conditions. MPL-2.0 is a weak copyleft licence: you can use it inside commercial and closed-source software, but if you distribute changes to its own files, you must publish those changes under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly Swift, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 20, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What problem NeAntik solves, and for whom
Most antidetect browsers are cloud products. You sign in, your profiles live on someone else's disk, and the vendor decides when the session ends. NeAntik takes the opposite position: a native SwiftUI manager on your Mac launches a bundled Chromium, and each profile gets its own cookies, local storage and site data directory. There is no account, no cloud sync and, per the README, no telemetry in the Direct build.
The audience is narrow by design. The README names Mac users on Apple Silicon who want a free antidetect browser without registration, plus developers and QA engineers who need reproducible separation of cookies, local storage, proxy settings and browser configuration across profiles. The README is equally blunt about who should look elsewhere: Intel Macs, Windows, Linux, team collaboration, cloud launches, RPA and API automation are all listed as reasons to pick a different product. That honesty is worth more than a feature matrix, because it tells you the project is not pretending to be GoLogin or Multilogin.
One caveat the README states in its own words: NeAntik does not promise full anonymity or undetectability, and it is not intended for bypassing CAPTCHAs, bans, antifraud systems or site rules. Treat it as a session isolation tool, not a stealth guarantee.
How the manager, the bundled Chromium and the profile store fit together
The architecture is two processes and a directory tree. A SwiftUI app manages profiles; a bundled ARM64 Chromium build, version 152 according to the README, does the browsing. Each profile owns a separate BrowserData directory, so cookies and site storage never cross between profiles. Duplicating a profile produces new UUIDs, a new fingerprint seed and a new BrowserData directory, and the proxy configuration is copied along with it.
Proxies come in three shapes: Direct, HTTP/HTTPS with authentication through Chromium's native window, and SOCKS5 without a username or password. Passwords for authenticated proxies are stored in the macOS Keychain and are not passed as command-line arguments, which keeps them out of process listings. Chromium is launched with a minimal allowlist of system variables, so proxy variables, TLS key logs and tokens present in your Terminal session are not inherited by the browser.
Two details stand out as engineering choices rather than marketing. New profiles are distributed by the system CSPRNG across four validated Apple Silicon cogroups, and existing profiles are not rotated afterward. The project also ships a release-only A to B to A check that verifies profile stability and distinctness, which the README says does not complicate the normal user flow. Both are the kind of thing you normally only see described in a changelog, and the README does not explain how the seed maps to specific Chromium surfaces, so that part you would have to read in Sources.
Installing NeAntik and opening a first workspace
The README is explicit that the GitHub Code button downloads source, not an application. The ready-to-run build is published on the GitHub Releases page as a notarized ZIP and DMG with the version number in the filename, alongside SHA-256 hashes for both files. macOS 14 or newer and Apple Silicon are required. If you build from source instead, the repository root contains Develop-NeAntik.command and Release-NeAntik.command, plus a Package.swift for Swift Package Manager.
After downloading, check the hash of the file you saved against the one published beside the same asset on the release page. The README does not spell out the hashing command, so use whatever tool you already trust for SHA-256 verification on macOS, and if the value does not match, delete the file and download it again.
The first workspace needs no configuration. The README describes the flow as: create a workspace, optionally edit the suggested name, optionally paste a proxy as a single line, then press Create and open. NeAntik prepares the connection before launching the browser. Returning later uses Continue, which brings back the verified window; Stop is available separately from the catalog. If a workspace still has its original blank start page, reopening it restores the previous tabs, but an explicitly chosen start address takes priority. Keyboard shortcuts are Command-1 for home and Command-2 for the catalog, and the macOS menu bar item lets you pick a workspace without finding the main window first.
Where NeAntik stops being the right tool
The README's own scope list is the first limitation: Intel Macs, Windows, Linux, cloud execution, team workflows, RPA and API automation are all outside the current product. If your workflow assumes a REST endpoint that creates profiles on demand, NeAntik has nothing to offer you today.
There are smaller failure modes documented in the feature list. A profile cannot be launched twice at once; the manager detects live helper processes to enforce that. Bulk proxy import parses a list locally and can create up to 100 separate profiles without network requests, and if an error occurs the profiles are not saved. An interrupted Keychain password cleanup is marked and retried on the next launch, which means a failed cleanup leaves state behind until that retry happens. Deleted profile data goes to the Trash rather than being erased immediately, and the Keychain secret is cleared in a separate step.
The larger caveat is conceptual. Profile separation here means separate storage directories, separate UUIDs and a stable fingerprint seed inside a compatible Chromium runtime. The README does not claim this defeats fingerprinting or antifraud detection, and it explicitly disclaims anonymity guarantees. Anyone treating a green profile list as proof of undetectability is reading more into the project than it offers.
How NeAntik differs from Vision, GoLogin, Dolphin, Multilogin, AdsPower and Octo Browser
The README includes a comparison table framed as an answer to the search query for an analog, and it opens by saying NeAntik is not a full copy of those services. The distinction is the model, not the feature count. Vision Browser supports several desktop operating systems plus accounts, teams and cloud sync. GoLogin offers cloud launches, tiered plans, collaboration and an API depending on plan. Dolphin {anty} prices by number of profiles and users. Against all of them, NeAntik is a local Mac-only public alpha with no registration and no team functions.
That framing matters because the trade is real in both directions. You give up multi-platform reach, cloud profiles and automation hooks. You get a native app you can inspect, a manager licensed under MPL-2.0, and a release process that publishes Developer ID signing, notarization, stapling, Gatekeeper acceptance, SHA-256 hashes and A to B to A evidence. For a solo developer or a QA engineer on an M-series laptop, that trade is often favorable. For an agency running dozens of profiles across contractors, it is not, and the README says so.
Licence, maintenance and what an upgrade costs you
The manager is licensed under MPL-2.0, which means modifications to MPL-covered files stay under MPL when distributed, while the rest of your codebase is unaffected. The bundled Chromium keeps its upstream licences and notices, listed in THIRD_PARTY_NOTICES.md, and the repository also carries TRADEMARKS.md. None of this is legal advice; if you plan to redistribute a modified build, read those files rather than this paragraph.
Maintenance looks current. The last push was on 2026-09-17, the same day as release v0.6.13, and the repository is not archived. The release cadence visible in the repository is fast: v0.6.11 on 2026-09-16, then v0.6.12 and v0.6.13 on 2026-09-17. That is a public alpha moving quickly, which cuts both ways. Fixes arrive fast, and so does churn. The README notes that a separate landing page carries the product description, installation steps and changelog history, and that the affpapa.org/neantik page is maintained separately by the owner and is not a release condition. If you pin a version, treat GitHub Releases as the source of truth for files and hashes.
Upgrade cost is mostly operational. Because profiles live locally and there is no cloud sync, moving a setup to another Mac is your problem, not the vendor's. Because Chromium is bundled rather than installed separately, a Chromium update arrives with a NeAntik release rather than through your system updater, so staying on an old release means staying on an old engine.
Editorial conclusion
Adopt NeAntik if you are on an Apple Silicon Mac running macOS 14 or newer, you want separate cookie and storage stores per profile, and you are willing to read a SwiftUI codebase to understand what the fingerprint seed actually changes. Skip it if you need Windows or Intel support, cloud launches, team seats, RPA or a write API; the README lists those as out of scope for the current product. Before relying on it, verify the SHA-256 published next to the release asset, confirm Gatekeeper accepts the notarized build, and read the A to B to A evidence the project publishes rather than assuming profile separation is stronger than it is.
Frequently asked questions
What is NeAntik?
NeAntik is an open source, local antidetect browser for Mac with Apple Silicon. A native SwiftUI manager launches a bundled Chromium and keeps cookies, settings and site data separate for each profile, without an account, cloud sync or product telemetry.
How do I install NeAntik on a Mac?
Download the notarized ZIP or DMG from the latest GitHub Release; the Code button downloads source code, not the app. macOS 14 or newer and Apple Silicon are required, and SHA-256 hashes for both files are published next to them.
Does NeAntik require an account or cloud sync?
No. The README states that profiles are stored locally on the Mac with no cloud synchronization, and that the Direct build contains no telemetry.
Which proxy types does NeAntik support?
Direct, HTTP/HTTPS with authentication through Chromium's native window, and SOCKS5 without a username or password. Proxy passwords are kept in the macOS Keychain rather than passed as command-line arguments.
Can NeAntik run on Windows, Linux or Intel Macs?
No. The README limits the product to macOS 14 or newer on Apple Silicon and lists Intel Mac, Windows and Linux among the reasons to choose another product.
Community notes