Otter

A self-hosted bookmark manager and media tracker built for people who value privacy and ownership.

Live site Repo CSS, TypeScript
Project README


Otter

Otter is a self-hosted bookmark manager and media tracker built with React, Supabase, and Cloudflare Workers

Otter is released under the MIT license. PRs welcome! Follow @zander

FeaturesPackagesGetting startedTech stack

Features

  • Private bookmarking app with search, tagging, collections, and filtering
  • Starred items and public/private visibility per bookmark
  • Dark/light colour modes
  • Media tracking — kanban-style board for tracking movies, TV shows, games, and more
  • AI-powered title and description rewriting via Cloudflare Workers AI
  • RSS feed parsing and URL scraping
  • Mastodon integration — backup your own toots and favourite toots
  • Cross-browser web extension (Chrome & Firefox)
  • Raycast extension to search, view, and create bookmarks
  • Native macOS/iOS app
  • Bookmarklet

Screenshots

Feed (dark mode)
Feed (light mode)
New bookmark
Search
Feed (showing tags sidebar)
Toots feed

Packages

This is a pnpm monorepo containing the following packages:

Package Description
packages/web Web app and Hono API on Cloudflare Workers
packages/app Native macOS/iOS app
packages/web-extension Cross-browser extension (Chrome & Firefox)
packages/raycast-extension Raycast extension
packages/chrome-extension Legacy Chrome extension (superseded by web-extension)

Getting started

Prerequisites

  • pnpm v10+ — install with corepack enable && corepack prepare pnpm@latest --activate
  • Supabase account and the Supabase CLI
  • Cloudflare account — used for hosting, Workers AI, and the API

For a full walkthrough — including Supabase database setup, Cloudflare configuration, and deployment — see the Setup Instructions.

Quick start

pnpm install
pnpm web:dev

Releasing

Otter uses semantic-release with the semantic-release-monorepo plugin to version each package independently based on Conventional Commits. Packages are not published to npm — releases are GitHub releases only.

Commit message format

Prefix Release type
fix: Patch (1.0.x)
feat: Minor (1.x.0)
feat!: or BREAKING CHANGE: Major (x.0.0)

Per-package versioning

Each releasable package has its own release.config.mjs that extends semantic-release-monorepo. The plugin filters commits to those that touch files inside the package's directory, so a commit changing only packages/web will only bump and release @mrmartineau/otter-web.

Releasable packages:

The app and raycast-extension packages are released through their own platforms (App Store / Raycast Store) and are not part of this workflow.

CI / automated releases

Releases are triggered manually via the "Release" workflow in GitHub Actions (.github/workflows/release.yml). The workflow:

  1. Installs dependencies
  2. Runs semantic-release inside each releasable package via pnpm --filter ... exec semantic-release
  3. For each package with relevant new commits: bumps package.json, updates that package's CHANGELOG.md, commits the bump back to main, and creates a GitHub release with package-scoped tag and notes

GITHUB_TOKEN is provided automatically by GitHub Actions — no additional secrets required.

Scoping commits

To target a specific package, use a Conventional Commits scope, e.g. feat(web): ... or fix(chrome-extension): .... The plugin uses changed file paths (not the scope) to decide which package releases, but scopes make the changelog clearer.

Tech stack

  • Frontend: React 19, TanStack Router, React Query, Tailwind CSS v4
  • API: Hono on Cloudflare Workers with AI bindings
  • Database: Supabase (Postgres)
  • Hosting: Cloudflare
  • Tooling: pnpm workspaces, Biome (formatting & linting), Vite

License

MIT © Zander Martineau

Made by Zander • zander.wtfGitHubMastodon