NeAntik

NeAntik is an open-source, local-first browser profile manager for Apple Silicon Macs. The manager is native SwiftUI and launches an embedded, source-pinned Chromium runtime. It does not require Electron, an account, a separately installed Chrome, or telemetry.

Русская версия

NeAntik 0.9.5 (205), Chromium-only public alpha is published on GitHub. ZIP/DMG hashes and qualification scope are recorded in the release record. It ships Chromium 156.0.8078.80; the effective external proxy route is unverified and WebKit is deferred. The 1.0 program remains open.

Security advisory

Security update, October 16: the runtime shipped in 0.8.18 lacked upstream fixes. 0.8.20 includes the backports; install the signed DMG/ZIP manually. Candidate 0.8.19 (131) was not published. History, evidence and scope.

Download

Download the signed and notarized application from GitHub Releases. Do not use GitHub's Code → Download ZIP button when you want the app: that archive contains source code, not NeAntik.app.

Latest published release: NeAntik 0.9.5 (205), public alpha. Published ZIP/DMG sizes and SHA-256 digests are recorded in the release record; this summary does not imply a new downloaded-byte check.

Update manually from 0.9.2 to 0.9.3 using DMG/ZIP: the older updater cannot apply this update. Quit before replacing the app and keep profile folders.

• macOS 14 or newer, Apple Silicon only;
• Chromium 156.0.8078.80, ARM64, Metal;
• signing, notarization, ZIP/DMG and SHA-256 apply to the exact published release.

Direct downloads: GitHub — 0.9.5. browser.free is updated separately.

The description below reflects the manager contract and this source branch; the exact public binary contents are defined by its release notes and assets.

Quick start

1. Create a profile and give it a clear name.
2. Paste a proxy if needed; NeAntik parses it locally.
3. Click Launch. Cookies and site data stay inside that profile.

Privacy features in the published 0.9.5 release

This release retains coherent presets, Chromium proxy configuration, site protection, ephemeral profiles and a protection passport. Proxy preflight does not measure the browser's request route. See privacy modes for scope and limits. Source availability is separate from binary publication.

WebKit in the current release

The published 0.9.5 (205) public alpha release creates and launches Chromium profiles only. Previously created WebKit profiles and their data are retained, but cannot be launched or duplicated in this release. Published version 0.9.0 included an experimental system WebKit mode; its behavior and limits are described in the guide.

What it does

• keeps cookies, local storage, and browser data in separate persistent profiles;
• searches profiles by name and tags, pins important profiles, archives inactive profiles without deleting data, and duplicates settings into a profile with a new UUID, fingerprint seed, and BrowserData; the proxy configuration is copied too;
• supports direct connections and authenticated HTTP/HTTPS/SOCKS5 through a separate local relay per profile, including HTTPS with certificate verification before credentials;
• before each proxied launch, checks the proxy and refreshes timezone/locale context through it. This preflight does not measure the Chromium window's effective HTTP/DNS route; a failed check does not fall back to Direct;
• locally parses a proxy list and creates up to 100 separate profiles without automatic network requests; a failed import does not save profiles, and any unfinished password cleanup is marked for retry on the next launch;
• keeps proxy passwords in macOS Keychain;
• launches Chromium with a minimal system-environment allowlist instead of inheriting proxy variables, TLS key logs, or Terminal tokens;
• prevents a second launch of the same profile;
• provides deterministic per-profile browser-surface isolation in the bundled patched Chromium runtime; newly created profiles are distributed with the system CSPRNG across four reviewed Apple Silicon cohorts, while existing profiles are never rotated automatically;
• includes a protected release-only A → B → A audit for stability and separation without exposing it in the normal user flow;
• keeps Direct telemetry disabled.

For authenticated HTTP/HTTPS proxies, separate buttons copy the username and password into Chromium's native prompt. The password remains in macOS Keychain and never enters the browser command line. Copied values carry the transient/concealed pasteboard hints and an unchanged clipboard is cleared after 60 seconds; another app can still read it during that interval.

When a proxy is configured by hostname, the system resolver may resolve the proxy's own address. The actual DNS route is not measured; the protection passport reports configured policy, not observed network traffic.

In-app help and local MCP

Searchable in-app help covers profiles, proxies, organization, storage and MCP. Help → Connect MCP to AI… copies workspace-specific JSON/TOML settings. Read access is the default; management enables 18 tools for profile creation, editing, duplication, proxy settings, project folders, tags, pins, archive and normal launch/stop. Profile and folder revisions prevent stale writes; passwords are write-only. Stop is graceful and owned by the live MCP session; reconnect requires manual browser close. No arbitrary JS, cookie/BrowserData access or cloud bridge is exposed. See setup, examples and FAQ.

Security and scope

NeAntik is intended for privacy, separated work sessions, development, and QA. It does not claim complete anonymity or undetectability. It is not designed to bypass CAPTCHAs, bans, anti-fraud systems, or third-party platform rules.

Releases qualify defined isolation and coherence scenarios on the exact runtime. This does not guarantee all external checker results or every host configuration. See release notes for measured evidence and limitations.

The bundled privacy-oriented Chromium is built without Google Safe Browsing. NeAntik does not send browsing history to Google, but it is not a replacement for dedicated phishing, malicious-site, or unsafe-download protection. Do not trust an unknown link merely because it is opened in an isolated profile.

The four cohorts are a reviewed product policy, not market-share evidence or an anonymity guarantee. A stable profile fingerprint intentionally links repeat visits within that profile; cookies, accounts, proxies, locale, behavior, and other signals can also link sessions. The current policy narrows the hardware tuple set; it does not make Canvas, Audio, WebGL, or ClientRects identical across different users.

Source layout

• Sources/NeAntik — native SwiftUI manager;
• Tests/NeAntikTests — manager, profile, proxy, runtime, and privacy tests;
• runtime — Chromium source lock, patch manifest, patches, and third-party licenses;
• scripts — build, verification, signing, and Direct release gates;
• docs — architecture, privacy, runtime, and distribution documentation;
• releases — public binary metadata and checksums, not the binary itself.

The full Chromium checkout and build output are intentionally not committed. The runtime is reconstructed from the pinned upstream Chromium source plus the checked-in patchset. See Building from source.

For profile data boundaries, snapshots, recovery and configuration transfer, see Profiles, privacy, and recovery.

Build the manager

./scripts/verify-native-swift-tests.sh
./Develop-NeAntik.command

Develop-NeAntik.command is the fast loop for UI and Swift changes. It creates an APFS clone of the embedded Chromium once, then rebuilds only the manager and opens an isolated NeAntik Dev.app. Development profiles and proxy credentials are separate from the production app. Use ./Develop-NeAntik.command --no-open for a build-only check.

Run Release-NeAntik.command only for the final exact candidate; that path performs the expensive release gates, A → B → A check, Developer ID signing, Apple notarization, and ZIP/DMG packaging.

Packaging a complete Direct application additionally requires a built Chromium runtime. Apple Developer ID signing and notarization use credentials in the builder's Keychain and are never stored in this repository.

Direct releases use two phases: prepare and sign one exact NeAntik.app with an immutable full-bundle manifest, then bind a fresh GUI A → B → A audit to that candidate. Notarization never rebuilds or re-signs it. The public-alpha and strict production qualification channels are explicit and cannot be substituted for one another.

Contributing

Read CONTRIBUTING.md and SECURITY.md before opening a pull request or reporting a vulnerability.

The synthetic fingerprint conformance corpus reuses the release verifier without publishing user profiles, seeds, proxy configuration, or real audit reports.

NeAntik-owned source files are licensed under MPL-2.0. Chromium-derived files retain their upstream licenses and notices. The NeAntik name and logo are subject to TRADEMARKS.md.

MCP supports modern 2026-07-28 plus legacy handshake, project/tag queries, 18 tools in management mode; read-only mode exposes 7 of these, 3 static prompts and 7 client formats: cookbook. Official configuration compatibility is distinct from end-to-end qualification of each AI client.