V26.12:show hn: ledge.sh – runnable markdown notes

Overview

Ledge solves a genuine, daily frustration for developers, DevOps engineers, and technical operators who constantly shuttle commands between notes and terminals. The value proposition is clear: eliminate copy-paste friction while keeping notes executable and interactive. The SSH-hosted ledger-server feature is particularly interesting — it allows running commands from mobile, effectively turning a phone into a remote terminal launcher tied to organized notes. The open-source model lowers adoption barriers, and the Bun/Electrobun stack keeps builds lightweight and modern. Cross-platform support (macOS, Linux, Windows/WSL, iOS, Android) is ambitious for an indie project and signals strong execution momentum since July. The key opportunity: this could become the "terminal-native Obsidian" — a workspace where notes and actions live in the same surface. If it gains traction, there's a natural path toward a pro tier (shared ledgers, team workspaces, cloud sync) or a hosted version of ledge-server.

Score Breakdown

What They Do

Hi HN, Ledge is a Markdown notebook that runs shell commands, code, SQL, etc from inside your own notes. I built Ledge because I spend much of my day copy/pasting commands from my notes into the terminal. I was inspired by how much cmux helped me organize my terminals - but there was still a split brain between my notes and frequently run commands. I've been daily-driving it for the past few weeks and use it for deploys, API calls, smoke tests, etc. Ledge runs your real shell just like a terminal app and can be hosted locally or remotely over SSH using ledge-server. I've been building it since July and have recently added support for all the major platforms: Mac (Silicon), Windows (WSL required), Linux, iOS, Android. Mobile devices require SSH access to a ledge-server and Android is still in beta and looking for beta testers (see link on website)! It's built on Bun and Electrobun and is free and open-source. Feel free to review the code and contribute at https://github.com/ledgesh/ledge Feedback is very much welcome. Any must-have features that are missing?

Why It Matters

Business Model

To be determined based on project analysis.

CRP Decision Report

🧠 Advisor

[score: 7]

[score: 7.0]

🧨 Devil

Risk 1: The "Jupyter already exists" problem. Jupyter, VS Code Notebooks, and even Apple's Swift Playgrounds already solve executable notes. Ledge must differentiate sharply or get dismissed as "yet another notebook." The shell-command focus helps, but the incremental value over code --notebook + tmux needs to be undeniable.

Risk 2: Mobile is a real UX challenge, not a gimmick. Android is in beta; iOS requires SSH setup. Both platforms have severe input constraints for a tool centered around command execution. Mobile may be a novelty that drains resources without meaningfully growing the user base.

Risk 3: Open source + indie = hard monetization path. Being free and open-source limits conversion to paid. There's no obvious freemium hook yet — no team features, no cloud hosting, no API integrations. Without a clear upgrade path, this remains a hobby project regardless of HN upvotes.

Risk 4: Security surface from running arbitrary shell commands. A tool that executes user-defined shell commands from markdown files is an attack vector. If someone shares a ledger with a malicious snippet, the trust boundary is unclear — especially over SSH.

[score: -6]

[score: -6.0]

📚 Historian

This follows the well-trodden path of developer tools that gain momentum via Hacker News launches (think devto, tldr, neofetch, or btop). The pattern: strong organic first-week traction, then a slow taper unless the creator ships consistently and finds a niche. Tools with a "run your own shell" positioning have historically been adopted by power users but rarely scale beyond that — they stay niche (e.g., iTerm2 profiles, tmux plugins). However, the SSH+mobile angle is underexplored in this space. The "open-source first, monetize later" model has mixed results: Obsidian succeeded with a pro tier, but Obsidian had a much broader audience (note-takers, not just devs). The cmux inspiration is smart positioning — terminal organization tools have shown willingness to convert to paid (e.g., Tabby). The biggest historical concern: many HN-shipped solo tools fizzle within 6 months without a clear monetization or team angle.

[score: 3]

[score: 3.0]

🧮 Budget Steward

Development costs: The core app (Electrobun) is already built and running. Remaining cost is finishing mobile (Android beta, iOS polish), which for an indie could range from 0 (solo dev) to 5,000–8,000 if outsourced. **Infrastructure:** ledge-server hosting is optional/local-first. Self-hosted model means near-zero infra cost. If a managed cloud version is offered later, that's additional cost but post-MVP. **Third-party services:** Minimal — no heavy APIs needed (runs user's own shell). Code signing for iOS (~99/year) and Google Play (~25 one-time) are small. Legal/templates for open-source: 0–200. **Total cost to MVP + first paying customers:** ~1,000–2,000 if solo, up to ~8,000–10,000 if mobile work is outsourced. Well within the 15,000 budget. Even the outsourced scenario leaves comfortable runway.

[score: 0]

[score: 0.0]

🧱 Founder

Yes, build this — but with a sharpened focus. The core product already works and has proven demand (daily-driving confirms it). The priorities should be: (1) nail macOS/Linux first as the primary workflow platform, (2) make the SSH/ledger-server the differentiator (not an afterthought), (3) delay full mobile investment until the core is validated and funded. Timeline: 2–3 months to ship a polished v1 for desktop, 1 month to launch, iterate based on feedback. After that, decide whether to build a pro tier or a hosted cloud version. The open-source model is a strength for distribution but needs a plan for monetization before commiting to expensive mobile ports.

[score: 7]

Overall Score: 5.3 (Moderate — promising tool with clear pain-point fit, but monetization uncertainty and mobile distraction are real concerns)

[score: 7.0]

Why This Made Only 10

This project was selected because it scored highly across our evaluation framework. The CRP analysis confirmed strong potential, making it one of the most promising opportunities this week.