lanework/research/08-competitive-analysis.md

Competitive Analysis — The Direct Set

This is the first item of the narrow pass: the positioning, pricing, feature, and traction study of the direct competitive set named at the end of 01-market-overview.md. It profiles each competitor as it stands today, builds the cross-cutting matrices, and closes with the strategic read — what changed since the broad pass, where the differentiation actually is, and what it implies for positioning and launch. Sources are cited inline on load-bearing claims; facts are snapshots of the research date.

Researched: 2026-08-07

The headline reads

Five things changed or sharpened since the 2026-08-01 broad pass.

1. The whitespace is confirmed, and narrower claims survive scrutiny. A Mac App Store field check found every sampled native kanban app (Sprout, Kanba, Boards, and company) storing data in an opaque database or app container, with at most a manual JSON/PDF export. Nothing offers user-legible files as live source of truth, let alone one file per card. "No polished native Mac kanban app uses files the user can read as its source of truth" holds as a checkable fact, not a marketing claim.
2. Signboard is smaller than the broad pass implied. The closest philosophical competitor is a solo side project: 85 GitHub stars, roughly 750 direct installer downloads over six months, an active install base in the low hundreds by auto-updater telemetry, no community, no launch, no press beyond a blog roundup. It ships monthly and its feature direction is exactly Lanework's axes (MCP, CLI, Obsidian, local AI), but as a business threat it is currently negligible — and as a demand signal it is sobering (see read 5).
3. Obsidian Bases' native kanban view is now the top external threat, and it is imminent. The legacy Kanban plugin is formally abandoned (unmaintained since May 2024, 2.4M downloads, 592 open issues, maintainer publicly seeking successors), and a native "Display files in side-by-side kanban boards" view is the single Active item on Obsidian's official roadmap as of August 2026 (obsidian.md/roadmap). When it ships, "markdown kanban" as a phrase commoditizes inside the largest file-based audience.
4. The agent-board cluster commoditized and split, and its GUI branch is not a task-management competitor. Vibe Kanban's company (Bloop) shut down in April 2026 — 27.7k stars, "the vast majority are free users," no viable business model (vibekanban.com/blog/shutdown); Conductor raised a $22M Series A and monetizes cloud compute for engineering teams; Cursor and Cline shipped their own boards; OpenAI open-sourced Symphony as a spec rather than a product. All of it is session orchestration — cards are agent runs bound to worktrees and PRs, state is app-owned, and none of it manages tasks a human authors. Adjacent, validating, not direct.
5. The demand is provably in the developer channel, and the pure-product players all have near-zero traction. Beads (~26k stars, 650k downloads) refuses to build a GUI, and its community keeps building board viewers over it anyway — a running proof that people want a human surface over agent-legible task state. Backlog.md (6.4k stars) is actively building that surface, web-first. Meanwhile every paid product in the file-based kanban niche — Signboard, Kanbanero, FileBoard, Sprout, Kanban MD — has effectively zero measurable users. The demand signal at scale lives entirely in GitHub/HN channels; the Mac-indie channel has so far bought none of this. That is the strongest answer yet to the broad pass's audience-funnel question, and it points the launch strategy firmly at the developer channel first.

Tier 1 — direct competitors

Signboard

The philosophical twin: local-first kanban writing Markdown files, tagline "Open source. Local-first. No account. … private, portable, and agent ready" (cdevroe.com/signboard).

• What it is: Electron (deliberately framework-free vanilla JS), macOS/Windows/Linux, distributed via GitHub Releases only — notarized but outside the App Store, so first launch hits the Gatekeeper malware warning (issue #39).
• Business: solo side project of Colin Devroe (day job at NerdPress), MIT-licensed, free for personal use, $49 one-time honor-system "sponsorship" for commercial use, tip jar. Bootstrapped, team of one.
• Activity: monthly releases, v1.0 March 2026 → v1.6 July 2026. Shipped in that span: Trello/Obsidian/Tasks.md import, a Planner workspace (calendar/week/day/agenda), Table view with filtering and bulk actions, linked objects, an Obsidian community plugin, a published calendar feed, and "Smart Actions" — off-by-default local-LLM automation via Ollama (title/summary/task-list/label/due-date generation, card Q&A) (releases).
• Agent story: built-in MCP server with board allowlisting plus a standalone CLI with JSON output; markets to "Claude, Codex, Gemini, OpenCode or any agent."
• Traction: 85 stars, 9 forks, ~750 direct installer downloads across six months of releases, auto-updater pings suggesting an active base in the low hundreds. No Discord, no subreddit, no Show HN, no Product Hunt — growth is the developer's blog and word of mouth.
• Weaknesses: Electron; Gatekeeper friction; no manual card ordering within a list (open request as of July 2026, issue #46); renaming or moving a board's folder breaks board switching (issue #27); CLI-created cards invisible to the Obsidian plugin (issue #47); linked objects only — no real attachment model; no first-party sync stance beyond "it's files."
• Read: the schema comparison (07) already established the structural differentiation; this pass establishes the scale difference. Signboard's feature velocity is real and its positioning language is nearly Lanework's own, so it defines the messaging territory Lanework must beat on execution — native speed, ordering that works, attachments, rename-safety, a board model with rigor. Its traction failure despite a year of shipping is a distribution lesson, not proof of no demand: it never launched anywhere.

Backlog.md

The most serious dual-audience trajectory in the set: "Trello or a lightweight Jira that lives right in your repo," for humans and agents (github.com/MrLesk/Backlog.md).

• What it is: MIT, Bun/TypeScript, tasks as Markdown files with YAML frontmatter in a backlog/ directory inside a git repo. Three surfaces: CLI, terminal kanban, and a localhost web UI with drag-and-drop.
• Agent story: first-party MCP server with workflow resource URIs; explicit three-checkpoint human-review workflow (spec, plan, code) before an agent implements.
• Activity: the standout — 4–5 releases a month through mid-2026, concentrated on the human board UI: deep links, task types, custom priorities, label filters, acceptance-criteria counts on cards.
• Traction: ~6.4k stars, 254-point HN launch (July 2025), large fork ecosystem, VS Code extension, multiple third-party MCP wrappers.
• Weaknesses: web UI, not a native app; scoped to one git repo (a dev-project tool, not a life tool); no real multi-agent concurrency story (sequential "one task = one context window = one PR" by design); community sees it as small-project-scale.
• Read: proof that "markdown tasks + polished human board + MCP" wins developer traction when actually launched. It competes for Lanework's developer buyer inside repos; it does not compete for boards as documents, native experience, or anything beyond code projects. Watch its web UI polish — it is the yardstick for "good enough" in the dev channel.

Tasks.md

The demand-proof incumbent of folder-as-board: lanes are folders, cards are Markdown files, self-hosted web app (github.com/BaldissaraMatheus/Tasks.md).

• Traction: 2.2k stars, 100K+ Docker pulls, listed across self-hosting directories — by far the most-adopted pure folder-as-board tool.
• Activity: tapering — multiple releases a month through late 2025, then a single 2026 release (v3.3.0, March, i18n) and nothing in the five months since. README states scope is "purposefully kept narrow."
• Weaknesses: requires a self-hosted Docker container; recurring open issues around lane/file rename propagation, image upload failures, silent backend-unreachable failures; no API, no MCP, no agent story at all.
• Read: unchanged from the broad pass as a demand signal, sharpened as a competitor: it serves the self-hoster who will run a container, and it has left the agent axis completely unclaimed. Its 100K pulls against Signboard's hundreds of installs also says the free self-host channel dwarfs the download-an-app channel in this niche today.

Obsidian — the Kanban plugin's corpse and the Bases trajectory

• The plugin: 2.4M downloads and functionally dead — last real release May 2024, repo moved to a community-archive org, MAINTAINERS.md openly soliciting successors, 592 open issues, "is this maintained?" threads unanswered (github.com/community-archive/obsidian-kanban).
• Bases: four official views today (Table, List, Cards, Map); Kanban is the current Active roadmap item ("Display files in side-by-side kanban boards"), with community Bases-kanban plugins already filling the gap (obsidian.md/roadmap, forum thread).
• Agent story: app-mediated, not file-direct — the official CLI (GA Feb 2026) remote-controls a running Obsidian instance, and the dominant Local REST API + MCP plugin (591K downloads) also requires the app open. Pure-disk access falls back to generic filesystem tools with no board semantics.
• Read: when Bases kanban ships, the largest file-based audience gets a first-party markdown board, and "kanban over markdown files" stops being a differentiator as a phrase. What Bases will not be: a board as a self-contained portable document (it is a view over vault-wide note queries), agent-legible without Obsidian running, or a native-feeling board surface. Lanework's messaging should pre-position against it now: boards as documents you can zip and send, agents that need no app and no plugin, and a surface built for the board rather than a view bolted on a vault.

Tier 2 — adjacent competitors

Beads

Steve Yegge's agent-memory tracker: ~26.1k stars, 650k downloads claimed, MIT (github.com/steveyegge/beads).

• Migrated away from flat files to Dolt (version-controlled SQL) in early 2026 — the substrate bet is now "git-semantics database," explicitly not human-legible markdown.
• Deliberately no first-party GUI, ever; Yegge moved up-stack to Gas City (multi-agent orchestration SDK). The community keeps shipping board viewers over it — TUI kanbans, web boards, a Tauri desktop app, a VS Code board — none with traction, all evidence of the unbuilt human surface.
• Carries real trust baggage: install-script re-signing flagged as bypassing Apple's malware checks (issue #1857), "pseudo-malware" discourse on HN, and Yegge's own "crummy architecture" admission.
• Read: not a competitor for the human board; a competitor for the substrate claim and the loudest demand proof in the space. Lanework's counter-story: the substrate that needs no daemon, no database, and no trust decision — folders and Markdown an agent's existing file tools already speak, with the app as the human surface Beads users keep asking volunteers to build.

Vibe Kanban, Conductor, Kanban Code — the agent-session cockpits

• Vibe Kanban: 27.7k stars, SQLite-backed board over git worktrees, broadest agent support — and a dead company (Bloop shut down April 2026; community-maintained, Apache-2.0). Its post-mortem is the niche's clearest business-model datum: free OSS orchestration couldn't monetize.
• Conductor: native Mac agent cockpit from Melty Labs, $22M Series A (March 2026), 2–3-day release cadence, free local tier with $50/mo cloud, enterprise logos (Google, Meta, Amazon among cited users). Workspace-centric — no general task management at all. GitHub-clone-only flow and a full-account OAuth-permissions controversy are its friction points.
• Kanban Code: LangWatch's AGPLv3 native SwiftUI app (macOS 26 only), 303 stars, six fixed agent-lifecycle columns, deep session/worktree/tmux/PR binding, JSON-file state. Unnotarized, build-from-source, tiny.
• New entrants since May: Cursor's agent-kanban SDK example, Cline Kanban, a half-dozen smaller clones; OpenAI's Symphony released as an open spec (April 2026) that OpenAI explicitly will not productize.
• Read: the cluster validates board-as-agent-control-plane and simultaneously demonstrates it is a different product: cards are runs, not tasks; state is app-owned; the human is a reviewer, not a planner. The overlap with Lanework is one buyer persona (the developer running agents) at a different moment of their day. The risk is vocabulary collision — "kanban for agents" now means these — so Lanework's language should stay "your board is files agents can work" rather than "orchestrate agents from a board."

Tier 3 — the native-Mac field (positioning foil)

• Sprout: CoreData + iCloud, subscription-first ($0.99/mo / $9.99/yr with a lifetime IAP muddle across channels), macOS 15+, launched Dec 2025, 16 Product Hunt upvotes, too few MAS ratings to display. Positioning is "quiet native kanban"; storage is opaque; traction is negligible.
• Kanbanero: $8.99 one-time, native, whole board as a single YAML/JSON file (not per-card files), no markdown/search/images, ~14 months without an update, zero visible traction.
• FileBoard: $0.99 lifetime IAP, genuinely folder=column/file=card — but over arbitrary files as a Finder-view utility, with no card authoring, no task semantics, brand-new, unrated.
• banban / Kanban MD: effectively out of scope on inspection — banban is SQLite-backed (not file-based at all), unlicensed, and a year dormant; Kanban MD is Linux-only, one Markdown file per whole board, explicitly unsupported by its author.
• MAS "kanban" field: Kanba (free + IAP, 4.8★/20 ratings), Boards – Personal Taskboards (.board ZIP archives, stale since Jan 2023), sundry $0.99–$4.99 utilities — all opaque storage, all thin.
• Read: the native channel contains no credible file-over-app player and no breakout of any kind; its lesson is that nobody has yet given the Mac-indie buyer a reason — the wedge that makes files matter to them is agents, which is exactly the story none of these apps can tell.

Feature matrix

Legend: ● yes · ◐ partial · ○ no. Lanework column reflects what has shipped plus Pro's built git core (remotes still ahead).

	Lanework	Signboard	Backlog.md	Tasks.md	Beads	Vibe Kanban	Conductor	Obsidian (Bases now)	Sprout
Native Mac app	●	○ Electron	○ web	○ web	○ CLI	○ web	●	○ Electron	●
Files as live source of truth	●	●	●	●	◐ Dolt db in git	○ SQLite	○	●	○ CoreData
One file per card	●	●	●	●	○	○	○	● (notes)	○
Byte-faithful to foreign edits	●	○ not contractual	○	○	n/a	n/a	n/a	◐	n/a
Agent-usable with app closed	● no tooling needed	◐ CLI/files	◐ CLI/files	◐ files	●	○	○	○ app must run	○
Written agent contract in-board	● CLAUDE.md, versioned	○	◐ MCP resources	○	◐	○	○	○	○
MCP server	○ unneeded by design	●	●	○	●	●	○	◐ plugin	○
Board as portable document	● folder = board	◐	○ repo-bound	◐	○	○	○	○ vault-bound	○
Manual card ordering	● ranks	○ open request	●	●	○	●	n/a	◐	●
Attachments model	● files + Quick Look	○ links only	○	◐ buggy	○	○	○	◐ vault files	○
Git integration in-app	● Pro: auto-commit, undo-as-commits, branches	○	◐ lives in repo	○	● core model	◐ worktrees	● worktrees	○	○
Multi-writer reconciliation	● provenance ledger	○	○ sequential by design	○	● hash IDs	n/a	n/a	◐	n/a
Full keyboard operability	●	◐	◐	◐	● CLI	◐	◐	◐	◐
Accessibility (VO, contrast, motion)	● verified	◐ claims	○ unknown	○	n/a	○	○	◐	○ unknown
Active development	●	● monthly	● weekly	◐ tapering	●	◐ community	●	●	◐

Pricing landscape

Player	Model	Price	Note
Lanework (planned)	free tier + Pro subscription	Pro unlocks git	one app, complete board experience free
Signboard	free + honor-system commercial	$49 one-time, unenforced	MIT source; tip jar
Backlog.md / Tasks.md / Beads / Kanban Code	free OSS	—	no monetization anywhere
Vibe Kanban	free OSS (+ dead cloud tier)	was $30/user/mo	company folded on this model
Conductor	freemium compute	$50/mo Pro, $60/user/mo Teams	monetizes cloud, not the board
Sprout	subscription + lifetime IAP	$0.99/mo, $9.99/yr	muddled across channels
Kanbanero	one-time	$8.99	stale, no traction
FileBoard	freemium lifetime IAP	$0.99	utility pricing
Obsidian	free + optional services	Sync/Catalyst	the free ceiling once Bases kanban ships

Three pricing facts stand out. Nobody in the direct set runs a functioning paid product — the field is free OSS, honor-system, or sub-$10 apps with no users, so there is no established price anchor and no evidence of price resistance either. The one venture-funded board company that stayed free died of it, and the one that charges monetizes compute, not software. And nobody anywhere charges for git-native features — Lanework Pro's "git as the paid tier" has no direct precedent, which cuts both ways: unclaimed ground, unproven willingness to pay. The broad pass's pricing-model question (Agenda hybrid vs Curio dual-track vs Things one-time) remains open and is not answered by this field; the closest datum is that subscription-first Sprout has zero traction while pay-once Things thrives, but neither is this niche.

Differentiation — where Lanework actually wins

1. The only native, polished human surface over per-card files. Confirmed unique across every ring examined. Everything native is opaque; everything file-based is web, CLI, or Electron.
2. Agents need zero tooling. No MCP server to install, no CLI, no app running: the board is files, and the in-board versioned CLAUDE.md teaches any file-capable agent the schema on arrival. Every competitor's agent story requires their bridge (MCP/CLI) or their app process. This is the sharpest single differentiator and should lead the developer-channel messaging.
3. Contractual byte-fidelity and multi-writer honesty. The round-trip guarantee, write-provenance ledger, foreign-edit reconciliation, and mid-drag re-grounding address the exact failure modes competitors demonstrably have (Signboard's rename breakage and CLI/plugin inconsistency, Tasks.md's rename propagation bugs) and the space's acknowledged hard problem (Beads' whole thesis). "Other writers are normal, not exceptional" is an architecture posture nobody else took.
4. Boards as documents. A board is a folder you can zip, send, template, and version — not a vault, a repo, or a server. Nobody else in the set has this shape; Bases specifically cannot.
5. Git as product, not plumbing. Auto-commit with composed messages and structural authorship, undo-as-forward-commits, per-card history — the agent-era audit trail as a first-class human feature. The cockpits use git as isolation machinery; Beads uses it as transport; nobody surfaces it to a human as legible board history.
6. Ship the basics the twin is missing. Manual ordering, a real attachments model, rename-safety, App Store distribution without Gatekeeper friction — table-stakes wins over Signboard that require no strategy, only the existing build.

Threats, ranked

1. Obsidian Bases kanban (high, imminent). Commoditizes the phrase and satisfies the casual markdown-board user inside a 2.4M-download demand pool. Mitigation: position on what Bases structurally isn't (document boards, app-free agent access, native surface) and ship before or fast after it lands.
2. Niche conversion risk (high, structural). The sobering pattern: every product in this niche has near-zero users while every dev-channel OSS tool has thousands of stars. Demand exists; paying customers are unproven. Mitigation: launch where the demand demonstrably is (Show HN, the agent-tooling audience), free tier genuinely complete, and treat the Mac-indie channel as a second wave.
3. Signboard velocity (medium). One committed builder shipping monthly with the same philosophy and a five-platform surface. Mitigation: out-execute on native quality and schema rigor (the durable moats from doc 07); watch its 1.x cadence for an ordering/attachments catch-up.
4. Vocabulary collision with the cockpit cluster (medium). "Kanban + agents" increasingly parses as "run coding agents from a board." Mitigation: language discipline — Lanework manages work, agents are first-class users of the board, not processes it launches.
5. Backlog.md expanding out of the repo (low-medium). If it ships a desktop app or repo-independent boards, it becomes the free developer default. Currently no sign of either.

Positioning recommendation

Hold the line from the charter, now with evidence: the best human surface over the substrate agents already speak — a real Mac app for boards that are just folders and Markdown, where anything that reads files is a first-class user and the app never holds the data hostage. Against the cockpits: Lanework is for the work, not the runs. Against Beads/Backlog.md: the human surface they refuse to build or can't make native. Against Bases: boards as documents, no app required for agents. Against Signboard: the same philosophy executed with native speed, schema rigor, and the basics done right. Against Sprout and the MAS field: your data in your files, forever, agent-ready.

Launch implication, stated plainly: the buyer who gets it today reads Hacker News, runs Claude Code, and already keeps markdown in git. The Tasks.md/Beads/Backlog.md star counts are the addressable early market; the Mac-indie channel converts later, once "agents work my board" is a demonstrable trick rather than a pitch.

What this pass leaves open

• Launch case studies with real numbers (HN/PH for file-based task apps) — still unfound; Backlog.md's 254-point launch is the one hard datum and deserves a dedicated tear-down.
• Pricing-model design for Pro — this field gave anchors' absence, not answers; the Agenda/Curio/Things comparison still needs doing on its own terms.
• Superlist's post-merger direction (untouched this pass).
• A Bases-kanban watch item: re-check the Obsidian roadmap monthly; its ship date sets Lanework's messaging clock.