ShipLog

A quality pass across the marketing site:

• Faster pages. Fonts now load from shiplog.ca instead of Google Fonts — one less third-party request on every page.
• Share cards. Links to shiplog.ca shared on X, Slack or LinkedIn now show a proper preview card instead of a bare URL.
• Readable by AI agents. The site ships llms.txt and pricing.md — machine-readable summaries of what ShipLog does and costs, plus a sitemap and structured data. If an AI agent is evaluating feedback tools for you, it can read ours without scraping.
• The legal basics. Real privacy and terms pages, written in plain language. The footer links now go somewhere.

Nothing changes in the product itself — no action needed.

There’s a new comparison page at shiplog.ca/compare: entry prices, free tiers, feature gates and MCP access for all four tools, side by side.

Every claim was checked against the vendors’ live pricing pages on July 13, 2026, and the page says when a competitor is the better pick — because sometimes one is. If you spot something stale, email hello@shiplog.ca and we’ll fix it.

The short version: all four tools do feedback, roadmaps and changelogs. The differences are what’s gated, what your bill does as you grow, and whether your AI agent gets a seat. ShipLog is the only one with MCP on the free plan.

Your public feedback board and changelog got a redesign.

What changed

• A navy masthead with your project name, and tabs to move between the board and the changelog — the two pages now link to each other
• Status filters are one-tap chips instead of a dropdown
• Clearer status badges with color dots, and each item shows when it was submitted
• Changelog posts are properly formatted: lists, code blocks and quotes now render the way you wrote them

Your brand color still drives votes, buttons and highlights — it just gained hover states.

Nothing changes in how feedback is submitted or voted on, and no action is needed on your side.

ShipLog now runs a remote MCP server at https://shiplog.ca/mcp. Claude Code, Claude Desktop, Cursor and any other MCP client can read and act on your feedback and changelog from inside a coding session. Included on every plan, free tier included.

Connecting

Create an API key in Settings → API keys, put it in an environment variable, then:

export SHIPLOG_API_KEY=sl_live_YOUR_KEY

claude mcp add --transport http shiplog https://shiplog.ca/mcp \
  --header 'Authorization: Bearer ${SHIPLOG_API_KEY}'

The single quotes matter: the key is expanded from your environment at runtime, so it never lands in shell history or config files.

What agents can do

Seven tools: get a feedback summary (“what should I build next?”), list and search feedback, file feedback, move items through statuses, and list or write changelog entries.

The loop this enables: your agent checks the top-voted request, you ship it, the agent marks it completed and publishes the changelog entry — without leaving the editor. This entry was published that way.

Scoping and limits

Every key resolves to exactly one project and every tool call is scoped to it. Tool output omits feedback authors’ email addresses, so no user PII ends up in agent contexts. Requests share the API’s 120 req/min per-project rate limit.

Full setup instructions are on the new AI agents page in your dashboard.

We collapsed our pricing tiers into a single all-inclusive plan.

Captain is $9/mo or $90/yr per project and includes everything: unlimited feedback items, the embeddable widget, the public roadmap, the changelog, API access and the MCP server. No feature gates, no “available on Pro” footnotes.

The free plan stays free forever: public feedback board with voting, roadmap and changelog, up to 50 feedback items. Enough to run a real product until feedback volume tells you it’s working.

If you were on Starter, you now have everything Pro had at the same price. Nobody pays more than before.

Also fixed: a crash when opening projects created under the old plan names.

You can now work with your ShipLog project programmatically. The API covers the core loop: read feedback, file feedback, move items through statuses and read your changelog.

What’s available

• GET /api/v1/feedback — list feedback, filterable by status and category, sorted by votes or date
• POST /api/v1/feedback — file a feedback item
• PATCH /api/v1/feedback/:id — update an item’s status (open → planned → in progress → completed)
• GET /api/v1/changelog — list your changelog entries

How auth works

Create an API key in Settings → API keys and send it as a Bearer token. Each key is scoped to exactly one project — no project IDs in URLs, no way to reach another project’s data. Keys are shown once at creation and can be revoked any time.

Requests are rate limited to 120 per minute per project. Responses are plain JSON with a consistent error shape, so scripts and agents can handle failures predictably.

After experimenting with a lot of feedback tools, and feeling disappointed we are product to release, ShipLog is now live and ready for indie SaaS founders.

If you’re tired of feedback scattered across email, Twitter DMs, support tickets, and Slack messages — and you just want one simple place to collect signals, show your roadmap, and ship updates — this is for you.

What’s Included at Launch

Free Plan (Forever)

• Public feedback board with voting
• Up to 50 feedback items
• Captain’s log (changelog) to announce what you ship

Starter Plan ($9/mo per project)

• Unlimited feedback items
• Embeddable widget (the “porthole”) for in-app feedback
• Basic customization to match your brand

Coming Soon: Pro Plan ($29/mo)

• API access
• Custom domain
• Remove ShipLog branding

Why We Built This

We’re solo founders too. We got tired of tools built for enterprise teams with budgets that start at $79/month. We wanted something that:

• Does one thing really well (feedback → roadmap → changelog)
• Doesn’t require a credit card to try
• Actually fits an indie budget
• Loads fast and feels good to use

So we built it. With Elixir, Phoenix LiveView, and a lot of coffee.