CompassPad — Find what was just built.

Plane is a project management tool in the issue-tracker category, positioned as an open-source alternative that can be self-hosted. It covers the familiar surfaces: issues, cycles, modules, and views, with a project structure on top. The differentiator is deployment. The product ships as a hosted service and as a self-hostable deployment, and the source is published. Teams that need their project data on their own infrastructure can run it, at the cost of operating it. Plane's model adds modules alongside cycles. A cycle is a timebox; a module is a grouping of issues by theme that can span cycles. Views are saved filters that can be shared across a project, which is how a team keeps a consistent board without rebuilding it per person.

Anki is a flashcard application built on spaced repetition. A card has a front and a back, and after each review the learner rates how difficult the recall was. That rating determines when the card is shown again, so material that is easy is seen rarely and material that is hard is seen often. The scheduling algorithm is the product. Decks are user-created, and the shared deck library means a learner can start from someone else's deck for a standard subject. Because the algorithm is open and the file format is documented, decks can be generated programmatically from other data. The interface is functional rather than polished, and creating good cards is work: a poorly written card produces poor recall no matter how good the schedule is. The application is free on desktop and Android, with a paid iOS client that funds development, and synchronisation runs through a free account.

tldraw is two things at once: a drawing application at tldraw.com and an SDK that other products use to add a canvas. The SDK is the more consequential half - it is a set of React components and a document model for building an infinite canvas into an application. The document model is the part that distinguishes it from a plain canvas library. Shapes are records with types and properties, the store is a reactive document, and collaboration is expressed as changes to that document. That structure is what lets an application persist a drawing, sync it between clients, and extend it with custom shape types. The editor is published as a package, and the hosted application at tldraw.com is a demonstration of what the SDK can build. For a product that needs a whiteboard, a design surface, or an annotation layer, the SDK is the reason to look at it.

Twenty is a customer relationship management tool built as an open-source alternative to established CRM platforms. Its distinguishing design decision is that the data model is editable: a team defines its own objects, fields, and relationships rather than adapting to a fixed schema. A CRM's value comes from the shape of its records, and most platforms fix that shape. Twenty exposes it. Companies, people, and opportunities are the defaults, but a team can add objects, add fields to existing objects, and define relations between them. Views and filters are built on top of whatever model the team creates. The product is published as open source and can be self-hosted. The hosted service is the commercial layer. For teams whose CRM requirements do not match a standard sales pipeline, the editable model is the reason to consider it.

Raycast is a macOS launcher: a keyboard shortcut opens a search field that reaches applications, files, clipboard history, and window management. The launcher is the surface; the extension API is what makes it a platform. An extension is a small program that adds commands to the launcher. A command can render a list, a form, or a detail view, and it can call an API. Because the UI primitives are provided, an extension that talks to a service is a few hundred lines rather than a full application. The store distributes extensions, and installing one adds its commands to the same search field as everything else. That consolidation is the practical argument: instead of remembering which app owns which action, a user reaches all of them through one shortcut. The product is proprietary and macOS-only, which is the main constraint to weigh.

Payload is a content management system that installs into an existing application rather than running beside it. Instead of a separate admin service reached over an API, Payload mounts its admin panel and its API inside a Next.js or Express application, sharing the same database and the same deployment. The configuration is code. Collections, fields, access control, and hooks are declared in TypeScript files, which means the content model is versioned with the application and can be type-checked. The generated admin panel reflects that configuration. Because it mounts into the application, the deployment story is the application's deployment story. There is no second service to host, and the database is the one the application already uses. The source is published, and the product can be self-hosted, which is the norm for this category.

Mintlify is a documentation platform for product and API docs. The workflow is content-first: a team writes Markdown and an OpenAPI specification in a repository, and the platform builds a documentation site with navigation, search, and an API reference generated from the specification. The generated API reference is the part that saves the most work. Instead of hand-writing a page per endpoint, a team points the platform at an OpenAPI document and the reference pages are produced from it, with request and response examples and a try-it panel. Because the source of truth is files in a repository, documentation changes go through the same review as code. The platform renders the result, hosts it, and provides the search and navigation layer. Content is written in MDX, so a page can include components beyond plain Markdown when a diagram or a tabbed example is needed.

Medusa is an open-source commerce backend for teams building a storefront that does not fit a hosted platform's model. The core is a modular Node.js server that exposes commerce primitives - products, carts, orders, customers, regions - through an API. The architecture is the differentiator. Commerce capabilities are modules with defined boundaries, so a team can replace the default implementation of one area without forking the whole system. A custom pricing module or a custom fulfillment integration plugs into the same interfaces the defaults use. Medusa is headless: it provides the backend and the API, and the storefront is a separate application. The project publishes a starter storefront alongside the server, but the server does not assume a particular front end. That separation is what lets a team use it with a custom storefront, a mobile app, or a marketplace model.

Sanity is a content platform built around structured documents rather than pages. Content is stored as typed documents with references between them, and the editing interface is configured in code to match that model. The Studio is the distinguishing piece. It is a React application that a team configures and deploys, so the editing experience can be shaped to a content model - custom field components, validation, and previews - rather than accepting a fixed admin panel. The content itself is served through a query API over the Content Lake. Because content is structured, the same document can render into a website, a mobile application, and a feed without duplication. References between documents are resolved by the API rather than by embedding copies, which is what keeps a change in one place from drifting across surfaces.

n8n is a workflow automation tool that connects services through a visual node editor. A workflow is a graph: a trigger node starts it, and subsequent nodes call APIs, transform data, or branch on conditions. The product sits between two categories. It is more visual than writing an integration script, and more code-friendly than a consumer automation tool: nodes can include JavaScript expressions, and a code node can run arbitrary logic inside the workflow. That combination is what lets it handle a transformation that a purely visual builder cannot express. n8n is published as source and can be self-hosted, which matters for teams that need automation to run inside their own network. The hosted cloud is the commercial layer. The self-hosted deployment is the same core, so a workflow can move between them.

Excalidraw is a virtual whiteboard that renders shapes with a hand-drawn line style. The aesthetic is deliberate: a diagram that looks sketched reads as a work in progress, which changes how a team treats it during a discussion. The product runs in the browser with no account required for a basic session. A drawing can be exported as an image or a file, shared through a link, and embedded in another page. For teams that need persistence and collaboration, an end-to-end encrypted room or a self-hosted deployment is available. The source is published and the project is widely embedded: several documentation tools and editors use Excalidraw's component rather than building their own diagram surface. That reuse is the clearest evidence that the drawing layer is separable from the hosted app.