CompassPad — Find what was just built.

Metabase is a business intelligence tool aimed at the people who have questions rather than the people who write SQL. It connects to a database, reads the schema, and presents a point-and-click query builder alongside a native SQL editor for users who want one. The product's distinguishing choice is that it does not require a modelled semantic layer before it is useful. Connect a database and the tables are immediately explorable, with questions saved as reusable cards and assembled into dashboards. Alerts and subscriptions push a saved question to email or Slack on a schedule. Metabase is open source with a paid enterprise edition that adds features such as granular permissions, sandboxing, and audit logging. It is a good fit for a team that needs self-service reporting over an existing database; it is a weaker fit for heavy financial modelling or for organisations that need a governed semantic layer with versioned metric definitions.

Beehiiv is a newsletter platform built for operators rather than only writers. Publishing and delivery are the baseline; the product's emphasis is on the growth side, with referral programmes, recommendation networks, and paid subscription tiers built in. The referral mechanic is the notable feature. A publication can offer rewards for subscribers who bring in others, and the platform tracks the resulting attribution, which turns the audience into a distribution channel. An ad network connects publications with sponsors, so a free newsletter can earn without introducing a paywall. The platform is hosted and subscription-priced, with a free tier that carries the platform's branding. It suits a publication that intends to grow an audience deliberately; a writer who only wants to send email to a list will find the growth machinery unnecessary.

Polar is a payments platform aimed at developers and open-source maintainers. Like other merchant-of-record services, it takes on sales tax and VAT obligations, but the product is shaped around the way developer projects sell: sponsorships, paid tiers for repositories, licence keys, and usage-based billing for API products. The integration is API-first with SDKs and a checkout that can be embedded, and there is a first-class GitHub integration for funding models where a sponsorship unlocks repository access or a private issue tracker. Usage-based billing supports metered events, which fits API products that charge by request. It is a younger platform than the established merchant-of-record services, so the ecosystem of integrations and the track record are shorter. Teams that want the developer-oriented billing model and are comfortable adopting an earlier-stage vendor are the natural fit; teams that need a long operating history usually choose a more established platform.

Substack is a publishing platform where a writer can start a newsletter and charge for it. The platform handles the website, the email delivery, the payment, and the subscriber list, and it takes a cut of subscription revenue rather than charging a monthly fee. The model is the reason it grew. A writer does not pay for software before earning anything: publishing is free and the platform's revenue comes from the subscriptions it processes. Paid and free subscribers can be on the same list, and a post can be public, free to subscribers, or paid-only. The tradeoff is control and portability. The audience lives on Substack's network, the design is largely fixed, and the platform's recommendations surface other writers to your subscribers. Writers who want a custom domain, their own design, and an exportable list sometimes move to self-hosted publishing software.

Plausible is a web analytics tool that reports on traffic without cookies and without collecting personal data. The tracking script is small, and because no cookie is set, the product does not require the consent banner that cookie-based analytics trigger in many jurisdictions. The interface is deliberately narrow. It reports page views, referrers, entry and exit pages, countries, devices, and goals, and it does not attempt to build user profiles or cross-site graphs. A site can publish its dashboard publicly, which some teams use as a transparency signal. The product is open source and can be self-hosted, though the hosted service is the main commercial offering. It is a good fit for a site that needs to know which pages are read and where visitors arrive from; it is a poor fit for anyone who needs funnels, cohort retention, or per-user behavioural analysis, which is a different class of tool.

Obsidian is a note-taking application whose defining property is that the notes are files on your disk. A vault is a folder; a note is a Markdown file; a link between notes is a wiki-style reference in the text. Nothing requires a server, and the folder can be put in any sync service or version control system. That choice has consequences. The application works offline because there is nothing to fetch, the notes remain readable if the application is uninstalled, and a user can edit them in any text editor. It also means the user owns the sync and backup decision rather than inheriting one. On top of the files, Obsidian adds a graph view of links, a canvas for arranging notes spatially, and a plugin system. Plugins are community-authored and can add views, commands, and editor behavior, which is how the application covers workflows it does not ship itself.

Craft is a document editor built for Apple platforms first, with a native application rather than a web app wrapped in a shell. Documents are composed from blocks, and the editor supports the formatting and media handling expected of a modern writing tool: tables, code blocks, callouts, and embedded content. The product adds structure on top of the document. Blocks can be linked and referenced, documents can be nested into a hierarchy, and a daily-notes surface provides a place to capture without deciding where something belongs first. Sharing produces a web page with a readable layout rather than a raw export. Craft is a good fit for people who write long-form documents and want a native editor with a strong visual result. It is a weaker fit for teams that need a shared wiki with granular permissions, or for anyone who wants their notes stored as plain files rather than in the application's own format.

Langfuse is an observability platform for applications built on large language models. It records traces of model calls - the prompt, the response, the latency, the token count, the cost - so a team can see what an application actually did rather than inferring it from logs. The tracing model follows the shape of an LLM application. A trace is a single request; spans inside it represent retrieval, tool calls, and model invocations. Because the structure is explicit, a slow or expensive step is visible rather than buried in an aggregate. Beyond tracing, Langfuse provides evaluation and prompt management. A dataset of inputs can be run against a prompt and scored, either by a model or by a person, so a change to a prompt has a measured effect. The platform is published as open source and can be self-hosted, which matters for teams whose prompts contain sensitive data.

Strava records physical activity from a phone or a GPS watch and turns it into a social feed. The recording itself is table stakes; the product's value is the network, because a segment or a route is meaningful when other people have also ridden or run it. Segments are the distinctive feature. A stretch of road or trail is defined once, and every activity that passes over it is timed against it, producing a leaderboard. That comparison is what motivates a large part of the user base, and it is the reason the platform has a social layer rather than being a private log. The social and competitive features are also the source of the product's problems. Privacy is a real concern, since a public activity reveals a route and a time, and the platform has added privacy zones and default settings in response. The full analysis features sit behind a subscription, while recording and the social feed are free.

Saleor is a headless commerce platform with a GraphQL API as the primary interface. The backend is written in Python on Django, which matters to teams whose existing services and hiring are in that ecosystem. The product covers the commerce domain: catalogue with variants and attributes, checkout and orders, payments through a plugin interface, warehouses and stock, and multi-channel selling where one catalogue serves several storefronts with different currencies and pricing. The dashboard is a separate application that consumes the same API. Compared with a hosted commerce product, Saleor leaves hosting and the storefront to the team, though a cloud offering exists. It suits organisations that want a GraphQL commerce backend they can extend in Python and operate themselves; it is a heavier starting point for a small store that only needs a working checkout.

Raindrop.io is a bookmark manager that stores more than a URL. When a page is saved, the service captures its content and produces a permanent readable copy, so a bookmark survives the original page changing or disappearing. Organisation is by collections and tags. A collection can be nested and shared, and a saved item can carry tags, a highlight, and an annotation. A full-text search runs over the captured content rather than only the title, which is what makes a large archive useful rather than a list of links. The product has free and paid tiers, with the paid tier adding full-text search across the archive, permanent copies, and larger uploads. It works across browsers and mobile, and imports from other bookmark services. The limitation is that it is a personal archive tool rather than a collaborative knowledge base: shared collections exist, but the product is not built for team editing.