llms.txt
Compare with other sites' llms.txt files →# Pear
> Empowering Developers, Disrupting the Norm!
## Overview
- [Pear | Unleash the Power of P2P](https://pears.com/): Empowering Developers, Disrupting the Norm!
- [Guided Setup](https://pears.com/start): Pick how you want to use Pear and we will assemble a starter kit from real recipes and modules.
- [Vision](https://pears.com/vision): Welcome to the Internet of Peers. The web was meant to connect people directly.
- [Partner Program](https://pears.com/partners): We work with teams shipping real products on the Pear stack, from first prototype to production rollout.
## Products
- [Pear Runtime & CLI](https://pears.com/products/runtime-cli): One embeddable runtime keeps your app updated, and one CLI takes it from pear touch to a live pear:// link.
- [Bare](https://pears.com/products/bare): Bare is the engine room of Pear: a small, fast, embeddable JavaScript runtime that runs the exact same code on desktop, mobile, and the terminal.
- [Building Blocks](https://pears.com/products/building-blocks): The Hypercore building blocks are a suite of small, composable JavaScript modules for peer-to-peer data and connectivity.
- [Pear SDK](https://pears.com/products/sdk): Everything you need to build peer-to-peer software, in one module. Pear SDK strips away server-side bloat to give you raw data replication, device-to-device connectivity, and unified deployment across all platforms.
## Resources
- [Blog](https://pears.com/blog): Peer-to-peer engineering, release notes and stories from the pears ecosystem.
- [Recipes](https://pears.com/recipes): Ready-made, runnable examples for building with Pear. Each recipe shows you exactly how to wire together the building blocks into a working peer-to-peer app.
- [Changelog](https://pears.com/changelog): Release notes for Pear — what shipped, release by release.
- [Events](https://pears.com/events): Meetups, workshops and community calls from the people building peer-to-peer software on Pears.
## Blog posts
- [Bare Can Now Seal the Door to Native Code](https://pears.com/blog/bare-can-now-seal-the-door-to-native-code): Bare can now lock down native code before it runs code you don't fully trust. Bare v1.32.0 adds Bare.Addon.seal() and a written threat model. Bare v1.33.0 brings bare-module v7.0.0 along with the new embedder context API.
- [Pear Mobile: Deploy P2P OTA Updates to React-Native Apps](https://pears.com/blog/pear-mobile-deploy-p2p-ota-updates-to-react-native-apps): Pear mobile OTA updates are here. `pear-mobile` and `pear-runtime-react-native` bring peer-to-peer over-the-air updates to React Native applications on iOS and Android, deployed with the same Pear CLI flow that ships terminal binaries and desktop applications. An update carries the JavaScript bundle and arrives from peers. This article covers the architecture, the version rules that keep native and OTA releases in step, and how to quickly get started.
- [Ecosystem Spotlight: oglr - inspect application-internal filesystems](https://pears.com/blog/ecosystem-spotlight-oglr-inspect-application-internal-filesystems): Inspect applications by pear:// link or by path, view the file contents of remote application drives, standalone binaries, Bare bundle files, AppImage, MSIX, AppImage and tar/tar.gz files.
- [Ecosystem Spotlight: swap - evergreen one-shot atomic exchange CLI](https://pears.com/blog/ecosystem-spotlight-swap-evergreen-one-shot-atomic-exchange-cli): Ship a command as a standalone binary that updates itself peer-to-peer. swap is an applied demonstration of a peer-to-peer installable self-updating single-operation program. This is the first in our Ecosystem Spotlight series, looking at the libraries, tools and applications growing out of the Ecosystem of Pears.
- [Pear Revolution](https://pears.com/blog/pear-revolution): A few weeks ago we shared the story of how Pear has evolved from a single application platform to an embedded runtime supported by CLI tooling. Today those changes are officially live in Pear CLI v3.0.0. We have also completely reworked our documentation so getting started on Pear or transitioning to the new architecture is easier.
- [Hello Pear Boilerplates](https://pears.com/blog/hello-pear-boilerplates): What if a terminal application could update itself without relying on servers, package registries, or centralized infrastructure? Introducing Hello Pear Bare, a new boilerplate for building standalone Bare executables with peer-to-peer over-the-air updates built in. Package your application and runtime into a single binary, distribute it anywhere, and let updates flow directly between peers. This article explores the architecture behind the next generation of peer-to-peer software distribution.
- [Pear Evolution](https://pears.com/blog/pear-evolution): Pear is evolving. What began as a peer to peer application runtime inside the Pear CLI is now becoming something far more flexible: an embeddable runtime library that can integrate into any JavaScript environment. This shift marks a major step forward for the Pear ecosystem, making peer to peer over the air updates, distributed deployment, and Bare workers available beyond the CLI itself. In this article, we explore the history behind Pear, why the runtime architecture is changing, and what developers need to know as Pear moves toward a more modular and production ready future.
- [Where does your data actually live? The architecture behind PearPass's no-cloud promise](https://pears.com/blog/where-does-your-data-actually-live-the-architecture-behind-pearpasss-no-cloud-promise): Most password managers encrypt your vault and upload it to the cloud. PearPass does something radically different: your data never leaves your devices. No central server. No cloud copy waiting to be stolen. This deep dive explores the peer to peer architecture behind PearPass, from Hypercore and Hyperswarm to Autobase and end to end encrypted device syncing — and why removing the server changes everything.
- [P2P from Scratch — Part 1: The Internet is Hostile](https://pears.com/blog/p2p-from-scratch-part-1-the-internet-is-hostile): You want two computers to talk directly to each other. No server in the middle, no middleman, no monthly bill. Sounds simple — the Internet is a network, after all. But the moment you try it, you discover something uncomfortable: the Internet was never designed for this. Here's why, and how Hyperswarm punches through anyway.
- [Introducing PearPass: A fully local, open-source password manager.](https://pears.com/blog/introducing-pearpass-a-fully-local-open-source-password-manager): Your passwords. Your devices. Nothing in between. PearPass is a fully local, open source password manager built by Tether Data. Unlike traditional tools that store your vaults in the cloud, PearPass keeps your data on your devices — encrypted, private, and under your control.
- [Interview with the creator of WhereFam: Decentralized Location Sharing That Puts Privacy First](https://pears.com/blog/interview-with-the-creator-of-wherefam-decentralized-location-sharing-that-puts-privacy-first): WhereFam is a secure, real-time location-sharing app that uses peer-to-peer (P2P) technology to enable private, scalable communication—without relying on centralized servers. Built with Pear Runtime, the app allows users to share their live location directly with trusted contacts, maintaining full control over who sees what, and for how long.
- [Interview with the creators of P2P Chess](https://pears.com/blog/interview-with-the-creators-of-p2p-chess): Playing traditional offline games using peer-to-peer technology highlights the essence of direct connection that Pear Runtime offers. In the offline world you play games directly with friends - face-to-face in real time. When these games were brought online you can still play one-on-one, but a centralized server has been inserted between you and your friend, and your actions and data travel across the internet to servers far away that have nothing to do with you and your friend. So even if you are playing in different rooms in the same house, you need to access a far-away server.
- [Interview with the creators of Hypersketch: A collaborative P2P whiteboard built entirely on Pear Runtime](https://pears.com/blog/interview-with-the-creators-of-hypersketch-a-collaborative-p2p-whiteboard-built-entirely-on-pear-runtime): Collaboration is a quintessential peer-to-peer activity—no intermediary is needed to facilitate joint creativity. So when two or more people want to work together on a visual creation or a joint brainstorming session, this pure connection does not need to be interrupted by centralized servers and latency.
- [Introducing Bare: Actually run Javascript Everywhere](https://pears.com/blog/introducing-bare-actually-run-javascript-everywhere): The Holepunch team has introduced Bare, a groundbreaking minimal JavaScript runtime designed for both desktop and mobile. Built to be fast, modular, and efficient, Bare revisits the original vision of Node.js by embracing modularity and universal compatibility.
- [Interview with Jose Landabaso, creator of Rewind Bitcoin: A Wallet that reverts theft & extortion.](https://pears.com/blog/interview-with-jose-landabaso-creator-of-rewind-bitcoin-a-wallet-that-reverts-theft-extortion): What if you could protect your Bitcoin from theft—even if someone had your private keys? José Luis Landabaso, creator of Rewind Bitcoin, set out to solve this challenge with time-based vaults and peer-to-peer backups, powered by Pear Runtime.
- [Building Apocalypse-Proof Applications with Pear Runtime](https://pears.com/blog/building-apocalypse-proof-applications-with-pear-runtime): In an age where centralized systems dominate and the specter of data breaches, censorship, and single points of failure looms large, Pear Runtime is carving out a revolutionary path toward decentralization. Modern digital landscapes are plagued by escalating cyberattacks, privacy breaches, and increasing AI monopolization. These challenges highlight the pressing need for a shift away from server-dependent infrastructures. Enter Pear Runtime, an open-source, peer-to-peer protocol poised to transform app development by eliminating server dependencies and ensuring data sovereignty.
- [Pears.com to participate in the third annual Plan₿ Forum](https://pears.com/blog/pears-com-to-participate-in-the-third-annual-plan-forum): Forum Brings Together Key Players to Envision the Future of Finance, Technology & Freedom of Speech
- [Interview with Suryaansh Singh, the creator of Holesail.io](https://pears.com/blog/interview-with-suryaansh-singh-the-creator-of-holesail-io): Suryaansh Singh shares his journey from a 7th-grade coding passion to creating Holesail, a peer-to-peer networking app, and discusses its potential to replace traditional DNS and port forwarding systems, emphasizing a secure, decentralized future.
- [Holepunch unveils groundbreaking open-source peer-to-peer app development platform: Pear Runtime](https://pears.com/blog/holepunch-unveils-groundbreaking-open-source-peer-to-peer-app-development-platform-pear-runtime): Launch Enables Anyone, Anywhere to Create Cost-Efficient, Scalable and Secure Apps with Zero Server Infrastructure Costs Forever Visit www.pears.com to Explore Pear Runtime’s Open-Source Code
- [Interview with creator of 🍐PeerViewer: Revolutionizing Remote Access: The Journey of PeerViewer and the Power of 🍐P2P Technology](https://pears.com/blog/an-interview-with-the-creator-of-peerviewer-revolutionizing-remote-access-the-journey-of-peerviewer-and-the-power-of-p2p-technology): In an era where peer-to-peer technology is reshaping the digital landscape, Thomas Farstrike introduces PeerViewer, a revolutionary tool designed with the power of P2P to facilitate seamless remote desktop access. Farstrike, a seasoned technologist with a rich history in the evolution of the internet and open-source software, leverages his vast experience to create an alternative to traditional remote desktop solutions. By harnessing the decentralized capabilities of Pear Runtime and Holepunch, PeerViewer emerges as a testament to the potential of P2P technology in offering privacy, efficiency, and a new level of connectivity. In this exclusive interview, Farstrike shares his journey from the inception of PeerViewer, through the challenges and triumphs of developing a P2P application, to his vision for the future of decentralized applications and the broader P2P ecosystem.
- [🍐 Pear Runtime: Empowering Developers to Disrupt the Web 2.0 Giants](https://pears.com/blog/pear-runtime-empowring-developers-to-distrupt-the-web-2-0-giants): In the ever-evolving landscape of digital innovation, a seismic shift is on the horizon, heralding a new era of internet freedom and empowerment for developers worldwide. At the heart of this revolution lies 🍐Pear Runtime, a groundbreaking framework poised to democratize app development and challenge the dominion of Web 2.0 giants.
## Changelog entries
- [v0.1.3 (v0.1.3)](https://pears.com/changelog/bare-pointer-0-1-3)
- [v0.1.2 (v0.1.2)](https://pears.com/changelog/bare-pointer-0-1-2)
- [v0.4.2 (v0.4.2)](https://pears.com/changelog/bare-gtk-0-4-2)
- [v0.1.1 (v0.1.1)](https://pears.com/changelog/bare-user32-0-1-1)
- [v2.1.1 (v2.1.1)](https://pears.com/changelog/bare-pack-drive-2-1-1)
- [v0.3.2 (v0.3.2)](https://pears.com/changelog/bare-ui-kit-0-3-2)
- [v0.3.2 (v0.3.2)](https://pears.com/changelog/bare-app-kit-0-3-2)
- [v7.5.0 (v7.5.0)](https://pears.com/changelog/bare-module-7-5-0)
- [v3.0.2 (v3.0.2)](https://pears.com/changelog/bare-pack-3-0-2)
- [v2.7.2 (v2.7.2)](https://pears.com/changelog/bare-module-traverse-2-7-2)
- [v3.0.1 (v3.0.1)](https://pears.com/changelog/bare-pack-3-0-1)
- [v1.6.2 (v1.6.2)](https://pears.com/changelog/hyper-multisig-cli-1-6-2)
- [v1.3.1 (v1.3.1)](https://pears.com/changelog/hyper-health-check-1-3-1)
- [v2.5.0 (v2.5.0)](https://pears.com/changelog/hyper-multisig-2-5-0)
- [v0.1.0 (v0.1.0)](https://pears.com/changelog/bare-rpc-test-0-1-0)
- [v0.1.4 (v0.1.4)](https://pears.com/changelog/bare-native-test-0-1-4)
- [v0.1.10 (v0.1.10)](https://pears.com/changelog/bare-device-0-1-10)
- [v0.1.2 (v0.1.2)](https://pears.com/changelog/pear-ci-0-1-2)
- [v2.3.0 (v2.3.0)](https://pears.com/changelog/hypertracker-2-3-0)
- [v0.1.1 (v0.1.1)](https://pears.com/changelog/bare-pointer-0-1-1)
- [v0.1.8 (v0.1.8)](https://pears.com/changelog/bare-stow-0-1-8)
- [v0.1.2 (v0.1.2)](https://pears.com/changelog/bare-stow-target-react-native-0-1-2)
- [v1.0.1 (v1.0.1)](https://pears.com/changelog/hypertracker-cli-1-0-1)
- [v1.4.1 (v1.4.1)](https://pears.com/changelog/bare-webp-1-4-1)
- [v1.1.1 (v1.1.1)](https://pears.com/changelog/bare-svg-1-1-1)
- [v1.2.1 (v1.2.1)](https://pears.com/changelog/bare-heif-1-2-1)
- [v0.5.9 (v0.5.9)](https://pears.com/changelog/bare-sidecar-0-5-9)
- [v3.0.0 (v3.0.0)](https://pears.com/changelog/bare-pack-3-0-0)
- [v0.2.0 (v0.2.0)](https://pears.com/changelog/bare-tui-paparam-0-2-0)
- [v1.6.1 (v1.6.1)](https://pears.com/changelog/bare-ffmpeg-1-6-1)
- [v3.1.12 (v3.1.12)](https://pears.com/changelog/bare-tls-3-1-12)
- [v3.4.1 (v3.4.1)](https://pears.com/changelog/bare-fetch-3-4-1)
- [v0.1.0 (v0.1.0)](https://pears.com/changelog/bare-pointer-0-1-0)
- [v0.3.4 (v0.3.4)](https://pears.com/changelog/bare-ndk-0-3-4)
- [v0.4.1 (v0.4.1)](https://pears.com/changelog/bare-gtk-0-4-1)
- [v0.1.0 (v0.1.0)](https://pears.com/changelog/bare-x11-xtest-0-1-0)
- [v0.1.0 (v0.1.0)](https://pears.com/changelog/bare-user32-0-1-0)
- [v0.1.0 (v0.1.0)](https://pears.com/changelog/bare-x11-0-1-0)
- [v2.7.1 (v2.7.1)](https://pears.com/changelog/bare-module-traverse-2-7-1)
- [v0.3.1 (v0.3.1)](https://pears.com/changelog/bare-ui-kit-0-3-1)
- [v0.3.1 (v0.3.1)](https://pears.com/changelog/bare-app-kit-0-3-1)
- [v0.3.7 (v0.3.7)](https://pears.com/changelog/bare-win-ui-0-3-7)
- [v2.2.5 (v2.2.5)](https://pears.com/changelog/bare-pack-2-2-5)
- [v0.1.0 (v0.1.0)](https://pears.com/changelog/bare-ui-kit-touch-0-1-0)
- [v2.13.0 (v2.13.0)](https://pears.com/changelog/hyperblobs-2-13-0)
- [v1.2.0 (v1.2.0)](https://pears.com/changelog/bare-exif-1-2-0)
- [v3.6.0 (v3.6.0)](https://pears.com/changelog/pear-3-6-0): v3.6.0
- [v0.1.2 (v0.1.2)](https://pears.com/changelog/bare-native-react-0-1-2)
- [v3.4.0 (v3.4.0)](https://pears.com/changelog/hypercore-storage-3-4-0)
- [v11.39.0 (v11.39.0)](https://pears.com/changelog/hypercore-11-39-0)
- [v6.11.0 (v6.11.0)](https://pears.com/changelog/hyperdb-6-11-0)
- [v2.19.0 (v2.19.0)](https://pears.com/changelog/hyperbee2-2-19-0)
- [v0.6.3 (v0.6.3)](https://pears.com/changelog/bare-bluetooth-0-6-3)
- [v0.7.1 (v0.7.1)](https://pears.com/changelog/bare-bluetooth-apple-0-7-1)
- [v0.11.4 (v0.11.4)](https://pears.com/changelog/bare-bluetooth-android-0-11-4)
- [v1.2.0 (v1.2.0)](https://pears.com/changelog/bare-heif-1-2-0)
- [v1.1.0 (v1.1.0)](https://pears.com/changelog/bare-svg-1-1-0)
- [v4.4.0 (v4.4.0)](https://pears.com/changelog/bare-pipe-4-4-0)
- [v0.1.5 (v0.1.5)](https://pears.com/changelog/bare-sqlite-0-1-5)
- [v1.4.0 (v1.4.0)](https://pears.com/changelog/bare-webp-1-4-0)
- [v1.1.0 (v1.1.0)](https://pears.com/changelog/bare-png-1-1-0)
- [v1.2.0 (v1.2.0)](https://pears.com/changelog/bare-gif-1-2-0)
- [v1.1.0 (v1.1.0)](https://pears.com/changelog/bare-tiff-1-1-0)
- [v1.1.0 (v1.1.0)](https://pears.com/changelog/bare-image-resample-1-1-0)
- [v1.1.0 (v1.1.0)](https://pears.com/changelog/bare-bmp-1-1-0)
- [v1.1.0 (v1.1.0)](https://pears.com/changelog/bare-ico-1-1-0)
- [v0.1.2 (v0.1.2)](https://pears.com/changelog/bare-wasi-0-1-2)
- [v2.7.0 (v2.7.0)](https://pears.com/changelog/bare-module-traverse-2-7-0)
- [v2.11.0 (v2.11.0)](https://pears.com/changelog/bare-media-2-11-0)
- [v0.11.3 (v0.11.3)](https://pears.com/changelog/bare-bluetooth-android-0-11-3)
- [v0.3.6 (v0.3.6)](https://pears.com/changelog/bare-native-0-3-6)
- [v1.2.0 (v1.2.0)](https://pears.com/changelog/bare-jpeg-1-2-0)
- [v0.1.1 (v0.1.1)](https://pears.com/changelog/bare-wasi-0-1-1)
- [v1.35.1 (v1.35.1)](https://pears.com/changelog/bare-1-35-1): What's Changed Run prepack before publishing by @kasperisager in https://github.com/holepunchto/bare/pull/248
- [v1.6.0 (v1.6.0)](https://pears.com/changelog/bare-build-1-6-0)
- [v0.1.0 (v0.1.0)](https://pears.com/changelog/bare-directory-0-1-0)
- [v1.4.0 (v1.4.0)](https://pears.com/changelog/bare-thread-1-4-0)
- [v1.35.0 (v1.35.0)](https://pears.com/changelog/bare-runtime-1-35-0)
- [v1.35.0 (v1.35.0)](https://pears.com/changelog/bare-headers-1-35-0)
- [v1.35.0 (v1.35.0)](https://pears.com/changelog/bare-1-35-0): What's Changed Run ASan on Windows Intel by @kasperisager in https://github.com/holepunchto/bare/pull/232 doc: add pointer for sanitizer by @tonygo in https://github.com/holepunchto/bare/pull/233 Add riscv64 to the Bare.arch type by @lucastortora in https://github.com/ho…
- [v0.1.9 (v0.1.9)](https://pears.com/changelog/bare-device-0-1-9)
- [v0.1.0 (v0.1.0)](https://pears.com/changelog/bare-gpac-0-1-0)
- [v2.2.0 (v2.2.0)](https://pears.com/changelog/hypertracker-2-2-0)
- [v0.3.5 (v0.3.5)](https://pears.com/changelog/bare-native-0-3-5)
- [v4.5.3 (v4.5.3)](https://pears.com/changelog/bare-worker-4-5-3)
- [v0.6.3-0 (v0.6.3-0)](https://pears.com/changelog/bare-bluetooth-0-6-3-0)
- [v11.38.0 (v11.38.0)](https://pears.com/changelog/hypercore-11-38-0)
- [v0.3.3 (v0.3.3)](https://pears.com/changelog/bare-ndk-0-3-3)
- [v0.1.1 (v0.1.1)](https://pears.com/changelog/bare-animation-frame-0-1-1)
- [v0.4.0 (v0.4.0)](https://pears.com/changelog/bare-web-kit-gtk-0-4-0)
- [v1.5.0 (v1.5.0)](https://pears.com/changelog/bare-build-1-5-0)
- [v7.4.0 (v7.4.0)](https://pears.com/changelog/bare-module-7-4-0)
- [v2.5.5 (v2.5.5)](https://pears.com/changelog/bare-url-2-5-5)
- [v0.1.3 (v0.1.3)](https://pears.com/changelog/bare-native-test-0-1-3)
- [v0.4.0 (v0.4.0)](https://pears.com/changelog/bare-gtk-0-4-0)
- [v0.1.2 (v0.1.2)](https://pears.com/changelog/bare-refresh-loop-0-1-2)
- [v0.1.2 (v0.1.2)](https://pears.c