OMEGA Ω™
3.6MB browser that never tracks, profiles, or sells data
545 followers
3.6MB browser that never tracks, profiles, or sells data
545 followers
OMEGA: an ultra-fast, security-first 3.6 MB native browser for macOS built on Apple architecture with Swift + WebKit. Opens in under a second, blocks trackers at the network level, fights fingerprinting, and refuses the surveillance economy. YouTube ads get neutralized. Amnesia Mode browses in RAM, leaves no trace, and disappears on quit. Hit Nuke to wipe cookies, cache, history, and site data. No profiling. No data brokerage. Just speed. Browse light. Browse free.
Free
Launch Team
Render: Get up to $100K in startup creditsCloud infrastructure for founders who want to move fast and NOT break things
Promoted
@chrismessina Absolutely. Since launch on Product Hunt, I’ve been heads-down on both of the items you called out. Passkeys should ship within the next day or so.
On extensions, there are two viable routes. One is “Omega-built” extensions authored in native Swift (what we’re already prototyping internally, with a path to public distribution). The other is a manifest-driven model using HTML/CSS/JS, which would let creators port or repurpose a meaningful portion of existing Chrome extension logic. I’m currently leaning toward the latter, while keeping Swift as the premium, first-party track for deeper integrations, but I’m not fully decided. I’m happy to put this to a community vote since Omega was built for you all.
More capabilities like this will roll out over the coming days, and once Omega is genuinely “ready,” we’ll distribute via Apple’s App Store. In the meantime, beta builds will remain available on the official site at www.omega.bz
@micheltrillo This is vibe coded, right? You forgot to delete an AI system message and posted it on your website: "If you want to be more aggressive, set the Chromium bar value to a specific headline example (650 MB) and keep the label “varies by browser”.
Funny but sloppy.
@atmos_ The website was absolutely vibe coded, which explains why it looks terrible. I built it last-minute because I wanted a trusted place where people could download the DMG directly. So yes...it's both funny and sloppy 😂 The browser itself was not vibe coded.
Historically, I’ve had limited success with tools like Bolt and Cursor. In both cloud and IDE contexts, the effective context window feels too constrained, and the recursive reasoning is not consistently strong enough for the way I build. I'm truly amazed by the successful outcomes of individuals who strictly vibe code with zero actual development experience, however. I wish I had that same "luck."
That said, I’ve shipped apps for years on iOS and Android. For this macOS build, I have leaned on AI primarily for debugging and for implementing features that are new to me in the macOS environment. It has been a genuine accelerant. In particular, Gemini has been extremely effective as a troubleshooting companion and has helped me navigate a more rigorous development path.
I seldom called upon ChatGPT for this specific workflow because it has felt slower and less aligned with the kind of answers I need, though that may be on me in how I’m prompting. So yes, there are traces of “vibe coding” in the broader sense, but the core product work is very deliberate. I care about correctness, performance, and visual coherence more than current AI tooling can reliably guarantee on its own.
@atmos_ @kn0wn Thank you both for your precious time to even comment. Honored to have you here, regardless. I appreciate the discourse nonetheless. 🙇🏽🙏🏽
@chrismessina Great share. “3M+ lines across thousands of files” 😳 is serious output, especially if Cursor was effectively running for a week and the browser was AI authored end-to-end.
To that post's comment "It kind of works! It still has issues and is of course very far from Webkit/Chromium parity...", my target with Omega has been the opposite philosophy: the smallest possible native footprint that still delivers a credible web experience, where the only latency you feel is the network and the remote server, not the app itself.
To your question, though, I’m at a 50/50 right now as macOS is newer terrain for me, even if Swift isn’t. If this were iOS, Liquid Glass would be almost trivial, where on macOS I had to fabricate the illusion manually. The Standard vs Fortress toggle, the page Zoom slider, and the ON/OFF switches are all hand-built “glass” experiments, and they landed better than expected.
Now I’m curious what Omega’s code line count is...shall I count? I'll get back to you on that. 🫡
And going forward, I’ll absolutely lean harder into AI to accelerate feature velocity. I can’t type fast enough, and some of what users will expect next, especially AI integrations and more complex capabilities, benefits from this machine-assisted augmentation.
3.6MB Swift+WebKit + “Amnesia Mode” is a bold privacy/perf bet 🔥
The scale pain is “block hard without breaking banking/Figma”; best practice is NetworkExtension filtering + WKContentRuleLists with per-site allow/deny + signed/ETag’d rule updates + clear breakage telemetry (local).
How are you preventing RAM→swap leakage in Amnesia Mode, and are Passkeys/WebAuthn + extension-style rule packs on the roadmap?
@ryan_thill Excellent questions. Figma seems to run smoothly on my end. Omega includes an “Exceptions” list by default, so you can allowlist specific sites for passthrough. Passkeys should be completed tonight, no extension needed. Your question about RAM was addressed in another thread, so I’ll reply shortly with that same explanation.
Regarding "Amnesia Mode browsing in RAM": how does this interact with macOS virtual memory/swap? If the OS pages that RAM out to disk (which macOS loves to do), isn't the data technically recoverable? Curious how "forensically clean" this actually is compared to a standard incognito window.
@tony_hsieh2 Amnesia Mode in OMEGA is implemented using WKWebsiteDataStore.nonPersistent(), which means WebKit keeps cookies, cache, local storage, and other website data in an ephemeral in-memory store and does not write that session into the normal on-disk browser profile.
That said, macOS virtual memory can page portions of RAM to disk under memory pressure, so in a strict sense any in-memory browsing session could be paged out. Practically, macOS swap is protected via encrypted virtual memory, so it is not a straightforward “recover plain text from disk” situation, but I still would not market it as “forensically guaranteed.”
The right comparison is that it is in the same class as standard incognito or private browsing, which is designed to prevent local persistence after the session ends, not to defeat a compromised machine, live memory capture, or network-side logging.
More precisely, yet in theory, some session data could be written to disk if macOS pages memory out to swap. In practice, that swap is encrypted by the OS, so it is not meaningfully “recoverable” by someone doing normal disk forensics after the fact. The edge case is a high-capability attacker with live access to the machine (or encryption keys/memory state) while you are browsing, in which case “private browsing in RAM” does not protect you, and that is also true for standard "Incognito."
To reiterate, Amnesia Mode is designed to prevent your browser from saving a trail on your own disk after you are done, but it is not a magic cloak against these three classes of risk:
A Compromised machine
If your Mac is infected or someone has admin or root access, they can observe what you do in real time. They can read browser memory, capture keystrokes, take screenshots, or hook the network stack. Private or RAM-only storage does not matter if the attacker is already inside the house.
Live memory capture
Even on a clean machine, if someone can capture RAM while you are browsing (debug tools, malicious endpoint software, physical access with high privileges), they may extract session data like page contents, tokens, or cookies from memory. Amnesia Mode reduces what is left behind later, but it cannot stop someone from reading what exists right now in RAM.
Network-side logging
Even if your local browser leaves no trace, the network can. Your ISP, corporate proxy, DNS resolver, Wi-Fi operator, and the sites you visit can log traffic patterns, DNS queries, IP addresses, and server-side logs. Amnesia Mode is local. It does not erase logs that exist outside your computer. This part we are actively working on, meaning we can "blind" the intermediaries, but we cannot prevent network-side logging completely, as you already know, I'm sure.
In short, Amnesia Mode is about minimizing local persistence after the session ends, not about defeating active surveillance during the session or logs that live elsewhere.
3.6MB is tiny. My Mac’s tired of browsers acting like OSes. The YT assassin bit is the hook. If it holds up on banking + Figma, I’ll keep it pinned. Amnesia mode for quick lookups is nice. Does it import Safari/Brave bookmarks?
@alexcloudstar I hope to meet your expectations, sir. Bookmark import is a priority, so I’ve added it to the roadmap. Stay tuned!
can you support older macos versions.
i am unable to use in macos 13.2.1 (ventura).
Mine is 2019 macbook pro btw.
@vamshi9666 Let me get back to you on that. I'm on a 2020 MacBook Air, although my OS is Sequoia 15.7.3
Kudos on launch. Clean philosophy, reducing browser surface area at the network layer feels like the right primitive. Curious how per-site tuning evolves.
@anupamsingh0211 Thank you so much. I plan to improve it as time progresses.