Bangle-io
Bangle-io handles WYSIWYG note-taking app storing notes locally in Markdown as a self-hosted solution.
A local-first note-taking web app, honestly reviewed. No marketing fluff, just what you get when you run your notes through a browser instead of a subscription.
TL;DR
- What it is: A web-only WYSIWYG note-taking app that reads and writes plain Markdown files directly from a local folder on your computer — no cloud account, no sync service, no install required [website].
- Who it’s for: People who want Notion-style editing but refuse to put their notes in someone else’s database. Writers, researchers, and founders with existing Markdown files who want a cleaner interface than a raw text editor [website][README].
- Cost savings: Notion charges $10–18/user/month. Bangle-io is free, open source, and runs entirely in your browser. The only cost is the browser you already have [website].
- Key strength: Zero friction to start. No sign-up, no download, no account. Open a browser tab, point it at a folder, and write. Notes stay on your disk in plain Markdown, readable by any tool forever [website].
- Key weakness: 1,209 GitHub stars and a sparse independent review record signals this is a small indie project, not a battle-tested platform. Browser dependency (Chrome or Edge for the File System Access API) is a hard constraint. No mobile app, no sync, no collaboration [merged profile][website].
What is Bangle-io
Bangle-io is a browser-based note-taking application that uses the browser’s Native File System Access API to read and write Markdown files directly from a folder on your computer. The pitch is simple: you get a Notion-like WYSIWYG editing experience, but your notes never leave your machine [website][README].
The project is built on a sister library called bangle.dev, which provides the rich text editor layer. The result is an editor that looks and behaves more like a modern document tool than a Markdown preview panel — you see formatted text as you type, not raw syntax [README].
What makes it structurally different from most note-taking apps is the storage model. Bangle-io doesn’t have its own database, its own cloud, or its own sync protocol. It opens a folder from your file system directly in the browser, reads whatever Markdown files are in it, and writes back to them in real time. When you close the tab, your notes are still ordinary .md files that any other tool — Obsidian, VS Code, a plain text editor — can open without conversion [website][README].
The GitHub repository sits at 1,209 stars. The app is live at app.bangle.io with a v2 in staging. It is described as free and open source, though the specific license isn’t prominently disclosed in the available documentation [merged profile][website].
Why people choose it
Independent reviews of Bangle-io are thin. The tool’s small GitHub footprint (1,209 stars versus Obsidian’s 100K+ or Logseq’s 35K+) means it hasn’t attracted the depth of third-party coverage that larger projects have. What does surface in aggregators [3][4] describes a consistent positioning: an accessible, browser-native Markdown editor for people who want local file ownership without the setup overhead of a desktop app.
The core use case that keeps appearing in the way Bangle-io presents itself: you already have Markdown notes somewhere, or you use Notion and resent that your writing lives in a proprietary database, and you want something that formats nicely without locking you in [website]. Bangle-io doesn’t try to compete with Obsidian’s plugin ecosystem or Logseq’s graph database. Its pitch is narrower and more honest: WYSIWYG editing on top of a folder of plain files, in a browser tab.
The “no install” angle is legitimately useful for people who work across machines, manage notes on locked-down work laptops, or simply don’t want another Electron app eating RAM. The browser-first architecture means the app is always up to date, doesn’t require system permissions, and doesn’t accumulate background processes [website][README].
Features
Based on the official website, README, and project description:
Core editor:
- WYSIWYG editing with Markdown storage underneath — you see formatted text, the file stays plain
.md[README][website] - Rich text formatting: headings, bold, italic, lists, and standard document blocks [README]
- Multi-tab interface for working with several notes side by side [website]
File and folder management:
- Opens any local folder directly via the browser’s File System Access API [website]
- Notes organized as standard folders — no proprietary structure, no database [website]
- Backlinks support for wiki-style cross-referencing between notes [website]
- Handles large vaults: the README explicitly cites compatibility with a 10,000 Markdown Files test project [README]
Offline and portability:
- Works fully offline once loaded [website]
- Installable as a PWA for a desktop-like experience with enhanced offline caching [website]
- No Electron — pure browser. No background services, no system tray [README]
- No account, no sign-up, no telemetry on your notes [website]
Extensibility:
- Built on bangle.dev, an open editor framework designed for extension [README]
- Community extensions described as “coming out soon” in the README — the current state of that ecosystem is unclear [README]
What it doesn’t have:
- Mobile app (no iOS, no Android)
- Cloud sync (by design)
- Real-time collaboration
- Plugins in the Obsidian sense
- PDF export or publishing
Pricing: SaaS vs self-hosted math
Bangle-io is free. There is no pricing page, no tier structure, and no usage-based billing. The website states: “We plan to keep the core product free. To ensure a sustainable future for the project, we may consider offering optional add-on services.” What those add-ons might be isn’t defined [website].
For context on what you’re avoiding:
| Tool | Model | Cost |
|---|---|---|
| Notion (Personal) | Cloud SaaS | Free (limited) / $10–$16/mo |
| Notion (Team) | Cloud SaaS | $15–18/user/mo |
| Obsidian Sync | Add-on to free app | $4/mo |
| Obsidian Publish | Add-on | $8/mo |
| Roam Research | Cloud SaaS | $15/mo |
| Bangle-io | Browser app, local files | $0 |
The savings math is simple because Bangle-io costs nothing. The real comparison isn’t financial — it’s capability. You’re trading cloud sync, mobile access, and a mature plugin ecosystem for complete local ownership, zero subscription risk, and notes that remain readable in any text editor forever [website][README].
If you have a team that needs shared notes with real-time collaboration and mobile access, Bangle-io isn’t the right call regardless of price. If you’re a solo founder or writer who wants a clean editor and full ownership of your writing, the cost of the alternative (Notion, Roam) is entirely avoidable [website].
Deployment reality check
Deployment for most users is: open app.bangle.io in Chrome or Edge, grant folder access when prompted, start writing. No server, no Docker, no configuration [website].
The browser constraint matters. Bangle-io’s local file access depends on the Native File System Access API, which Chrome and Edge support fully. Firefox does not support this API. Safari support is partial. If you use Firefox as your primary browser, Bangle-io’s core feature doesn’t work as advertised. The website recommends installing as a PWA for the best experience, which is essentially pinning the Chrome-hosted app to your dock [website].
Self-hosting the web app itself: The GitHub README documents a development setup (pnpm install, pnpm start, runs on localhost:4000). This is a development server, not a production deployment guide. If you want to host Bangle-io on your own server — so colleagues can use it internally, for example — there’s no documented production deployment path in the available materials [README].
Backup story: Because notes are plain files in a folder you choose, backup is whatever you already use for important files — Time Machine, rsync, rclone, git. The website explicitly recommends git for version-controlled backups. This is an honest, no-vendor-lock-in answer [website].
What to watch for:
- Chrome or Edge required for the file system API. Not optional.
- The v2 is labeled as “staging” in the project documentation — production stability expectations should be calibrated accordingly [merged profile].
- With 1,209 GitHub stars, this is a small indie project. Long-term maintenance depends on a small team. The website acknowledges this directly, describing it as “a small indie project” worth supporting [website].
Pros and cons
Pros
- Zero friction to start. No account, no install, no subscription. Browser tab plus a folder and you’re writing [website].
- Genuine local ownership. Notes are plain
.mdfiles. If Bangle-io disappears tomorrow, every note opens in any text editor without conversion [README][website]. - WYSIWYG on top of Markdown. The editing experience is closer to Notion or Google Docs than to a Markdown preview pane — you see formatted output, not raw syntax [README].
- Offline capable. Works without internet once loaded. PWA install improves this further [website].
- No telemetry on your content. The website explicitly states it doesn’t track or analyze you or your data [website].
- Handles large vaults. The README tests it against 10,000 files. Performance isn’t the problem [README].
- Backlinks included. Wiki-style note linking without a plugin [website].
- Free. No trial, no freemium gotcha, no CC required [website].
Cons
- Chrome/Edge only for file system access. Firefox and Safari users are second-class citizens. This is a browser API limitation, not a bug Bangle-io can fix — but it’s a real constraint for a significant slice of users [website].
- No mobile. You cannot use Bangle-io on iOS or Android. For anyone whose workflow crosses devices, this is a dealbreaker [website].
- No sync. Local-only by design. If you work across multiple computers, you manage sync yourself (git, Dropbox, Syncthing — all valid, all manual) [website].
- Small project with unclear license. The license field in the project metadata is empty. The website says “open source” without naming the license. Before building any process around this tool, verify what the license actually allows [merged profile][website].
- Thin third-party review record. 1,209 GitHub stars and sparse independent reviews mean there’s limited community knowledge about edge cases, bugs, and long-term reliability [merged profile][3][4].
- Extension ecosystem is unbuilt. The README mentions community extensions “coming out soon” — that was presumably written some time ago, and it’s not clear how mature the extension story is today [README].
- No collaboration. Single-user, single-machine tool. No shared editing, no comments, no permissions model [website].
- Production deployment undocumented. If you want to self-host the server for a team, there’s no documented path to get there [README].
Who should use this / who shouldn’t
Use Bangle-io if:
- You want Notion-style editing with zero subscription and zero cloud dependency.
- You already have a folder of Markdown notes (from Obsidian, VS Code, or any other tool) and want a cleaner editing interface for them.
- Your workflow is single-computer and you manage your own backups.
- You’re on Chrome or Edge and plan to stay there.
- You want to support a small open-source project and don’t need enterprise guarantees.
Skip it (use Obsidian instead) if:
- You need a rich plugin ecosystem — Obsidian has hundreds of community plugins and a large, stable community.
- You want a tool with clear commercial backing and documented long-term maintenance.
- You need mobile access. Obsidian has iOS and Android apps.
- You want to publish notes as a website (Obsidian Publish handles this directly).
Skip it (use Logseq instead) if:
- You organize thoughts as an outliner or graph rather than linear documents.
- You want a more mature open-source alternative with active development and a larger community.
- You need daily notes, task management, and query-based views.
Skip it (stay on Notion) if:
- You need real-time collaboration with a team.
- You need mobile access that stays in sync.
- You’d rather pay $10/mo than manage your own file organization and backup.
Skip it (use Joplin instead) if:
- You want a self-hosted sync server with end-to-end encryption and a proper desktop app across all platforms.
- You need mobile support with real sync.
Alternatives worth considering
- Obsidian — The dominant local-first Markdown notes tool. Free core, large plugin ecosystem, mobile apps, optional paid sync. Not open source, but the files are plain Markdown. The practical benchmark for anything in this category.
- Logseq — Open source, graph-based, outliner-first. Stores notes as plain Markdown or Org files. Has a larger community than Bangle-io and more active development. Better if you think in connected ideas rather than documents.
- Joplin — Open source, full desktop and mobile apps, self-hosted sync via Joplin Server or third-party WebDAV. More mature deployment story for teams. Less polished UI than Bangle-io, better cross-device story.
- AppFlowy — Open source Notion alternative with self-hosted server, collaboration, and mobile apps. Closer to Notion’s feature set. More setup overhead than Bangle-io, more capable.
- Standard Notes — Open source, end-to-end encrypted, subscription sync. Prioritizes privacy and longevity over features.
- Markdown editors (Typora, iA Writer) — Paid desktop apps with excellent WYSIWYG Markdown editing. Not free, not browser-based, not self-hosted — but mature and polished.
For a non-technical founder whose primary pain is Notion’s pricing or vendor lock-in, the honest shortlist is Bangle-io vs Obsidian vs Logseq. Pick Bangle-io if zero friction and browser-first matter. Pick Obsidian if ecosystem depth and mobile access matter. Pick Logseq if you want the most actively developed open-source option.
Bottom line
Bangle-io does one thing cleanly: it gives you a Notion-like editor on top of a folder of Markdown files, with no account, no subscription, and no cloud involved. For that specific use case — a solo writer or founder who wants local ownership and a better editing experience than VS Code — it works. The file model is honest (plain .md, never proprietary), the offline story is solid, and the zero-cost, zero-signup entry point removes every typical objection to trying a new tool.
The limitations are real and unsurprising for a 1,209-star indie project: Chrome/Edge only, no mobile, no sync, no collaboration, and a thin independent review record. If any of those constraints breaks your workflow, the alternatives above are more mature. But if your workflow fits the constraints, there’s nothing to pay and nothing to lose by trying it.
Sources
- Bangle-io — Official website — https://bangle.io
- Bangle-io — GitHub repository README — https://github.com/bangle-io/bangle-io
- SaaSHub — Newsy Alternatives (lists Bangle-io as a competitor with feature summary) — https://www.saashub.com/newsy-alternatives
- SaaSHub — Ideanote Alternatives (lists Bangle-io as a competitor with feature summary) — https://www.saashub.com/ideanote-alternatives
Primary sources:
- Application (v2 staging): https://staging.app.bangle.io
- Merged product profile: GitHub repository at https://github.com/bangle-io/bangle-io (1,209 stars)
Category
Related Documents & Knowledge Base Tools
View all 226 →Stirling-PDF
75KThe most popular self-hosted PDF platform — merge, split, convert, OCR, sign, and process documents with AI, all running on your own infrastructure.
AppFlowy
69KAn open-source Notion alternative with AI, wikis, projects, and databases — cross-platform (desktop, mobile, web) with offline-first architecture and full data ownership.
AFFiNE Community Edition
66KAn open-source workspace that merges docs, whiteboards, and databases into one platform — a privacy-focused alternative to Notion and Miro with AI built in.
Docusaurus
64KA static site generator built on React for documentation websites — write in Markdown/MDX, version your docs, and deploy anywhere. Created by Meta.
Crawl4AI
62KOpen-source LLM-friendly web crawler that generates clean markdown from any website, purpose-built for RAG pipelines, AI data extraction, and automated research.
Atom
61KGitHub's hackable text editor, officially sunset in December 2022. The codebase remains archived on GitHub as a reference for community forks like Pulsar.