Origyn Web Browser

👤 tarun basu • 📅 April 5, 2026 • 👁️ 22 views • 🔄 Updated May 15, 2026

browsers listofbrowsers webbrowser

## What is Origyn Web Browser (OWB) **Origyn Web Browser** (often abbreviated *OWB*) was an open-source browser project synchronized with Apple’s **WebKit** engine, initially sponsored by a French company called **Pleyo**. Its goal was to serve as a browser optimized for **embedded systems** and **consumer electronics** (CE) — devices like set-top boxes, portable media players, GPS units, etc. A key architectural feature was an **abstraction layer (“OWBAL”)** that allowed porting more easily to different platforms, using whatever graphics/input/etc. libraries that the target already had. ## Timeline & Major Milestones Here’s how OWB evolved over time: | Time / Date | Event / Release / Change | Details | | --- | --- | --- | | 2006 | Project started by Pleyo | Origyn Web Browser was created by Pleyo in Montpellier, France. | | August 2007 | Public reports & early builds | Wired published about OWB showing its aims, use of WebKit, OWBAL, and ports to devices, with exposure via an open source model. | | November 22, 2007 | Version “Robespierre” released | One of the milestone version names. | | 2008-2009 | Multiple milestone versions | Examples: “Blastoise” (July 1, 2008), “DoDuo” (July 1, 2008), “Galekid” (Dec 19, 2008), “Galegon” (Feb 11, 2009), “Galeking” (June 4, 2009), “Pukapuka” (Oct 8, 2009). | | ~2009-2010 | Growth of ports & features, esp. on Amiga/MorphOS/AROS | OWB became popular in the Amiga-like OS world. Newer versions supported HTML5, media playback, e.g., OWB 1.7 for MorphOS added HTML5 audio/video via FFmpeg. | | After Sand-Labs stops | MorphOS developer takes over; rename to *Odyssey Web Browser* | Fabien Coeurjoly (MorphOS) took over maintenance. When no original Sand-Labs code remained, the project was renamed **Odyssey Web Browser**. | | 2014 | Last known stable releases on Amiga-like OS | For example, AROS had version 1.25; MorphOS / AmigaOS versions as of mid-2010s. | ## Features & Technology OWB offered a robust set of features, particularly given its target embedded/smaller-device usage, and its adaptability across platforms: Full (or near-full) support for CSS 2.1 and growing CSS3; support for Web standards like SVG (partial to full in different ports), MathML, XPath/XSLT; HTML5 features including media playback in later versions. Support for plug-in architecture (NPAPI) in certain ports (e.g. MorphOS / GTK) including Flash Player (where possible) and others. Good compliance with standard tests: e.g. Acid2: 100% on all ports; Acid3: 99-100% depending on port. Abstraction layer (OWBAL) that allowed reuse of existing graphics / input / system libraries on each platform, easing porting effort. ## Platforms & Ports OWB was used on or ported to: **Embedded / consumer electronics** devices: set-top boxes, STBs, digital TV decoders, Media Players, GPS devices etc. This was part of its original target use. **Amiga-like operating systems**: **AmigaOS** (classic Amiga OS / AmigaOne / etc.) **AROS** (Amiga Research OS, an open source OS) **MorphOS** There were also ports using GTK, Qt, SDL etc for more generic desktop / lightweight Linux environments. ## Limitations & Discontinuation The project is **discontinued** — no longer under active development under the name Origyn Web Browser. As noted above, Sand-Labs disappeared, and ownership / maintenance shifted. When the original codebase from Sand-Labs was no longer present, the project was renamed to **Odyssey Web Browser** for the MorphOS community. Because it was synchronizing with WebKit, keeping up with changes in WebKit (new web standards, security patches, performance etc.) was a challenge. Embedded and smaller OSes also have constraints (hardware, memory, etc.) that make adopting newer features harder. ## Legacy OWB has left a legacy in the embedded systems / Amiga-like OS world: it showed that WebKit-based browsers, with the right abstraction architecture, could be viable for lightweight devices. The successor name **Odyssey Web Browser** continues in the MorphOS / Amiga community. Many of the features that OWB developed (video/audio playback, HTML5 features, etc.) became standard expectations over time in lightweight / embedded browsers. ## Origyn Web Browser: The Protocol and Digital Identity Browser The Origyn Web Browser is not a standalone application like Chrome or Firefox for general web surfing. Instead, it is the central application and reference implementation for the **Origyn Protocol**, a decentralized platform focused on identifying, authenticating, and unlocking the value of luxury goods and digital assets (like NFTs). ## The Timeline of Origyn’s Development ### 1. Conception and The Big Problem (2019 - 2020) **The Foundational Problem:** Origyn was conceptualized to solve a major issue in two distinct markets: **Luxury Goods:** The markets for high-value physical assets like watches, handbags, and jewelry are plagued by counterfeiting, lack of provenance, and illiquidity. **Digital Art & NFTs:** The emerging NFT market was (and still is) filled with “right-click saves,” copies, and scams, with no sophisticated technological way to prove the authenticity or provenance of a digital file itself. **The Big Idea:** The founders, including **Mike Schwartz** and **Vincent Periard** (industry veterans from companies like Funko and Microsoft), envisioned a protocol that could create a **digital twin** or a **“certificate of authenticity”** for any valuable asset, both physical and digital. This certificate would be immutable, traceable, and live on a blockchain. ### 2. Development and The Role of the “Browser” (2020 - 2021) **Choosing the Platform: The Internet Computer (IC).** The Origyn team chose to build its protocol on the **Internet Computer (IC)**, a blockchain network developed by the DFINITY Foundation. The IC’s key advantage is its ability to host and serve web content and run applications at web speed, making it ideal for a user-facing product. **What the “Origyn Web Browser” Actually Is:** The term “browser” here is used in its most fundamental sense: **an application to look at and interact with assets on the Origyn Protocol.** It is the user interface that allows anyone to view the provenance, authenticity, and ownership history of an asset certified by Origyn. It is the wallet interface that allows owners to manage, trade, and transfer their certified assets. It is the marketplace where buyers and sellers can connect. In essence, it’s a **"browser for certified luxury and digital assets."** ### 3. Launch, Expansion, and The Porsche Partnership (2021 - 2022) **Initial Focus on Luxury Goods:** The protocol and its browser application were first demonstrated with high-end Swiss watches. The process involved using advanced techniques like computer vision and AI to create a unique, unforgeable fingerprint for a physical watch, which was then minted as an NFT on the blockchain. **Pivotal Porsche Partnership (2022):** A major validation of the technology came when **Porsche AG** partnered with Origyn. They used the Origyn technology to authenticate and create digital certificates for a rare, $1 million+ Porsche 911 “Sonderwunsch” (Special Wish) program car. This was a landmark moment, proving the protocol’s utility for ultra-high-value industrial goods. **Expansion into Digital Art:** Concurrently, Origyn expanded its focus to the digital art world. The browser became a platform for what they termed **“Dynamic, Non-Fungible Tokens” (dNFTs)**, where the digital asset itself could be authenticated, not just the token on the blockchain. ### 4. Recent Developments and The ORIGYN Foundation (2022 - Present) **Establishment of the ORIGYN Foundation:** To steward the protocol long-term, the non-profit ORIGYN Foundation was established in Switzerland. This decentralized the governance of the protocol and emphasized its community-owned nature. **GYToken:** Theecosystemispoweredbyitsnativeutilitytoken,‘*GYToken*:∗∗*Theecosystemispoweredbyitsnativeutilitytoken*,‘GY`. **The Browser’s Evolving Role:** Today, the Origyn Web Browser continues to be the primary dApp (decentralized application) for the ecosystem. It is constantly updated to support new asset classes, including: **Physical Luxury Goods** (Watches, Bags, Jewelry) **Digital Art & Media** **Credentials and Certificates** ## Key Reasons for Its Historical Significance **Redefining the “Browser”:** Origyn Web Browser is a prime example of the Web3 philosophy, where a browser is not just a window to the *information* web, but a gateway to the *ownership* and *value* web. **Bridging Physical and Digital Worlds:** It is one of the most ambitious and technically sophisticated projects attempting to create a seamless, trustworthy link between high-value physical objects and the blockchain. **A Pioneer on the Internet Computer:** It stands as one of the flagship, real-world applications built on the Internet Computer, demonstrating the blockchain’s potential beyond simple smart contracts to host complex, user-friendly dApps. **Solving for Authenticity:** Its core mission addresses a fundamental problem of trust in both physical and digital markets, using technology to provide a solution. ## Conclusion The full history of the Origyn Web Browser is not a story of competing with Google Chrome. It is the story of a specialized tool built for a new, decentralized economy. It represents a paradigm shift where a “browser” is re-imagined as a verifiable ledger of ownership and authenticity for the world’s most valuable assets, both tangible and digital. Its legacy will be tied to the success of the broader Origyn Protocol in transforming how we prove and trade value.