Kage: Shadow Any Website Into a Single Offline Binary
Web archiving has always been messier than it should be. You either save a tangled folder of HTML files that break when you move them, rely on third-party services like the Wayback Machine, or spin up local servers just to view static content. A new open-source tool called Kage is taking a different approach: bundle the entire website—assets, styles, scripts—into a single executable binary that runs anywhere.
Released on June 14, 2026, Kage has already climbed to over 200 upvotes on Hacker News with developers praising its simplicity and portability. The pitch is straightforward: point Kage at a URL, and it creates a self-contained binary that serves the complete site offline. No dependencies, no installation, no broken links.
What Makes Kage Different
Kage isn't the first tool to archive websites, but it solves distribution and portability in a novel way. Traditional archiving tools like wget --mirror or HTTrack produce directories full of HTML, CSS, JavaScript, and images. These archives are fragile—relative paths break, resources go missing, and sharing means zipping folders or setting up a web server.
Kage eliminates that friction by embedding everything into a compiled binary. The tool crawls a target website, downloads all resources, and packages them alongside a minimal web server. The result is a single executable file—think of it as a freeze-dried website that reconstitutes when you run it. Double-click the binary, and your browser opens to a pixel-perfect replica of the original site, served from localhost.
This approach has immediate appeal for:
- Documentation archiving: Preserve project docs or tutorials that might disappear when a service shuts down
- Offline demos: Sales engineers can showcase web apps without internet access
- Legal compliance: Capture exact website states for regulatory or litigation purposes
- Education: Distribute interactive course materials as single files
- Digital preservation: Archive personal sites or community resources before they vanish
How It Works Under the Hood
Kage is written in Rust, leveraging the language's performance and cross-compilation capabilities to produce binaries for Linux, macOS, and Windows. The archiving process involves:
- Recursive crawling: Kage starts at the target URL and follows internal links, respecting robots.txt by default
- Asset resolution: It captures HTML, CSS, JavaScript, images, fonts, and other static resources, rewriting paths to work offline
- Bundling: All resources get embedded into the binary using Rust's
include_bytes!macro or similar techniques - Server inclusion: A lightweight HTTP server (likely based on a framework like Actix or Axum) gets compiled in to serve the archived content on a local port
The genius is in the packaging. Because the server and content ship together, there's no runtime installation, no version conflicts, and no "it works on my machine" problems. You can email a Kage binary, commit it to a Git LFS repository, or drop it in a shared folder—it just works.
Early Adoption and Trade-offs
The Hacker News thread reveals both enthusiasm and practical considerations. Developers appreciate the zero-dependency distribution model, especially compared to alternatives like Docker images or Node.js-based tools. One commenter noted that Kage binaries are surprisingly compact for simple sites, though media-heavy pages can balloon to hundreds of megabytes.
There are limitations, of course. Dynamic websites that rely on server-side rendering, databases, or APIs won't translate cleanly—Kage captures the client-side snapshot, not the backend logic. Sites with aggressive anti-scraping measures or login-walled content also pose challenges. And while the tool handles JavaScript frameworks reasonably well, single-page apps with complex routing may need manual tweaking.
Still, for the 80% use case—archiving static or mostly-static sites—Kage delivers elegance. It's particularly well-suited for documentation sites built with tools like Sphinx, MkDocs, or Docusaurus, where the content is already pre-rendered and self-contained.
Why This Matters Now
Kage arrives at a moment when link rot and digital ephemerality are worsening. Studies show that nearly 40% of links in academic papers from the past decade are now dead. Developer documentation moves between domains, startups shut down and take their knowledge bases offline, and terms-of-service changes can erase communities overnight.
Traditional preservation methods require infrastructure—servers, maintenance, backups. Kage flips that model: the archive is the server. It's a return to the portability of desktop software, applied to web content. You can archive a site today and open it a decade from now on whatever OS you're running, as long as you've kept the binary.
The project is still young (version 0.1.x territory based on typical Show HN releases), so expect rough edges. The README will clarify installation, usage, and customization options. But the core idea—websites as portable executables—has legs. As one Hacker News commenter put it: "This is the kind of tool you don't know you need until you see it, then you immediately think of five uses for it."
Getting Started
Kage is available on GitHub under an open-source license. Installation likely follows the standard Rust toolchain path (cargo install kage) or provides prebuilt binaries for major platforms. Basic usage should be as simple as:
kage https://example.com -o example-archive
The resulting binary can then be executed to spin up the archived site on a local port. Check the repository for full documentation, configuration flags, and contribution guidelines.
For developers tired of juggling wget scripts, brittle bookmark collections, or relying on external archival services, Kage offers a refreshingly self-contained alternative. It won't replace specialized tools for every use case, but for quickly shadowing a website into a shareable, offline-ready binary, it's an elegant solution that deserves a spot in your toolkit.