Capsule ships single-file .capsule apps that store their data in local SQLite, built and updated through AI prompts
- Capsule bundles a web UI, assets, and a local SQLite database into one portable
.capsulefile that opens in a host player, with v0.4.0 downloads for macOS, Windows, and Linux (macOS build about 10MB, since it uses the OS webview via Tauri, not bundled Chromium). - The selling point is a document-like app: send a
.capsuleover WhatsApp, AirDrop, or email, and the recipient taps it to launch with data preloaded and works fully offline with no cloud, account, or network. - Apps are generated and edited from AI prompts: ChatGPT, Claude, or Gemini read instructions at
withcapsule.app/prompt.txtto produce a complete capsule with HTML UI, schema, and local SQLite data, and later prompts (or MCP coding tools) modify features, dark mode, or the schema. - For multi-copy merging, each record carries a UUID and timestamp, deletes leave tombstones, and conflicts currently resolve by keeping the newest record, with a merge UI promised later.
- The author says data stays schemaless to avoid migration complexity and to ease CSV import and merging, and that capsules are sandboxed with no file-system access, though commenters raised injection and malware concerns.
Hacker News opinions
Pretty cool, but who is this actually for? What problem does it solve, and how would I know I need this over anything else?
If you're abusing Excel for data management or downloading a whole app just to save recipes, this is the alternative. You can track time and billing with a decent UI without paying for a SaaS subscription.
Wait, doesn't this require a host app installed to read the file? That's friction for distribution. Browsers already run HTML and CSS, isn't that a better delivery mechanism?
You can't save user data into a single clickable file like a Word or Excel doc that way. An Excel spreadsheet is basically UI plus data in one file too.
Browsers have basically lobotomized local HTML files. Try loading a JS file from the same directory and you get a CORS error. That's why we ship 200MB Chromium copies to run 1MB of web code.
I got a cheap approximation of this with Chromium plus the Filesystem API and a PWA manifest. AI actually reignited my interest in building purely on browser-native features.
If you're distributing to many users, the browser route is probably better. The point of Capsule is the personal document: move it to a USB stick or your cloud storage and it's still the same doc, same UI, same data.
The whole pitch gives me Lotus Notes flashbacks.
Big companies are testing agentic coding to automate business processes, and this could distribute apps for workflows too small to justify a traditional web backend. It's the modern MS Access.
What's wrong with just using IndexedDB?
For storing data inside the capsule file it would add migration complexity when you update the HTML to add a form field. Keeping data schemaless also makes merging and CSV import easier.
This seems ripe for an injection attack. Can you inspect the file before it runs?
The HTML has no permission to touch the file system, and ideally the whole app runs sandboxed on desktop. On mobile that's the default anyway.
If your app needs to update and preserve state, you probably don't want to pass it around as a bundled file. Every state change means emailing everyone a new capsule. Just host it, the DB updates live for everyone.
Why not put it on a shared drive like Dropbox? Concurrent editing won't work though.
You're glossing over the recurring cost and annoyance of hosting and securing the data. Share and run local is the whole point. If you need to share data between people your objection holds, but for individual notes or recipe apps this works.
New way to deliver viruses just dropped. Great idea, but it can definitely be abused.
I've been building this exact thing using sqlar as the format, in the browser plus desktop and Android on Tauri. Firefox blocks my demo with CORS and it never loads, for what it's worth.
If the state is meant to be shared, why keep it with the code? You'll end up building a complex sync system to a central DB anyway.
Killer feature idea: let authors expose their capsule to the internet, and users type the name of the capsule into the app to pull it onto their device.
Hear me out, here's a name for that: PWA, Probably Web Again.
Looks useful, but on Mac the download says Capsule is damaged and can't be opened, and it seems ripe for malicious payloads too.
One fallout of AI adoption I keep seeing: models are great at making visual artifacts, but if you need to hand over the data inside them there's no clean way to share it without hard-coding. This fixes that.
How exactly do you reconcile changes? If two people each edit a copy and want to merge, you've got two capsules with different data.
Each record is saved with a UUID and timestamp, and deletes leave a tombstone with only the ID. Right now the newest wins on conflict, but a merge UI to confirm which record to keep is coming.
Really practical idea. My first jobs out of college were Tkinter mini-apps replacing abused Excel spreadsheets, and a sales friend of mine would use this. Not sure about the business model though, since he already generates HTML mini-apps with Gemini for free.
I love this. It's like making a standalone binary, though cross-platform support makes that hard. The capsule file is the standalone binary, like a PDF or Word doc, and you just need the viewer to open any of them.