Aboard vs Cowpin: AI Boards vs Exportable Link Library

Aboard is built around boards: flexible collections where you arrange saves, notes, and AI-assisted structure for a project or topic. It fits when the unit of work is a workspace — “everything for this launch,” “this client,” “this research thread.”

Cowpin is built around a personal link library: every save is a URL with archived text, tags, highlights, and standard exports. It fits when the unit of work is recall years later — “find that article,” “export to Obsidian,” “let my agent search what I saved.”

Neither is wrong; they optimize for different shapes of memory.

What Aboard is optimizing for

Boards as the primary metaphor: group items, reshape layout, lean on AI to suggest structure. Strong when your saves are mixed media and context inside a project, not when you need a single flat list you can grep or POST to from a script.

If you already think in Kanban-ish or mood-board workflows, Aboard’s model matches how you file things mentally.

What Cowpin is optimizing for

URLs as durable records. Cowpin fetches and stores page text (plus optional HTML snapshot on Pro), so search and highlights survive layout changes better than a thumbnail-only save.

Tags and bundles instead of free-form boards — less canvas, more librarian.

Export and automation: Pinboard-compatible API, bulk HTML/JSON export, importers for Pocket, Instapaper, Karakeep, Reddit, and more, and MCP/API access for coding agents — not “export the whole board as PDF” as the main escape hatch.

Highlights live in the reader and export to Markdown for Obsidian/Notion — see highlights export.

Side-by-side (honest)

Cowpin does not ship an Aboard importer. If you leave Aboard, plan to re-save URLs (or export links from Aboard if their export gives you hrefs) and accept that board layout does not transfer — tags and bundles are how Cowpin replaces “which board was this on?”

When Aboard is the better pick

You want one surface per initiative with flexible grouping and AI helping you arrange work — and you rarely need Pinboard-style POST /v1/posts/add from a script.

Your team already lives in board-shaped tools; links are ingredients, not the whole product.

When Cowpin is the better pick

You have been burned by lock-in or shutdown exports and want a library that still makes sense in plain files and APIs in ten years.

You highlight heavily, care about full-text search, or want Cursor/Claude to search saves without re-uploading PDFs.

You migrate from Raindrop, Recall, or Reader and care more about export than live sync.

Both (split workflow)

Use Aboard for active project boards while a sprint runs; Cowpin as the canonical URL + highlight archive you export and point agents at when the board goes stale. Duplicate URLs intentionally — not duplicate mental models.

Try Cowpin on your links

Import a Pinboard or Pocket export, or save from the extension, and see whether tag + search + export beats board layout for your habit.

Start free →