CompassPad — Find what was just built.

Framer is a design and publishing tool where the canvas and the live site are the same artifact. A designer lays out breakpoints visually, and publishing produces a hosted site with no separate build step or handoff to an engineer. The product covers the ground a design tool and a site builder would otherwise cover separately. Components can have variants and interactions, content can be bound to a CMS collection, and animations are configured on the canvas rather than written as code. Effects such as scroll transforms are set up through the same visual interface. The tradeoff is the boundary of the tool. A site that fits Framer's model ships quickly and looks polished; a site that needs custom server logic, unusual routing, or a data layer outside the CMS reaches the edge of what the canvas can express. Teams sometimes publish a marketing site in Framer while the product itself is built elsewhere.

Turso is a managed SQLite service built on libSQL, an open-source fork of SQLite that adds replication and network access. Each database is a SQLite file, which means the operational model is a file rather than a cluster: small, fast to copy, and trivial to isolate per tenant. Databases can be placed in multiple regions, with one primary accepting writes and read replicas serving queries locally. The embedded replica mode goes further, keeping a local copy inside the application process so reads avoid a network round trip entirely and sync in the background. The appeal is cost and simplicity at high database counts. A multi-tenant product can give every customer their own database without running a fleet of Postgres instances. The constraint is that SQLite is a single-writer system, so write-heavy workloads need the primary and do not benefit from the replica topology.

Sourcegraph is a code search and intelligence platform for organisations with many repositories. It indexes source across a codebase so a query can find a symbol, a pattern, or a usage across repositories that would otherwise be searched one at a time. Beyond search, the platform provides code intelligence: go-to-definition and find-references that work across repository boundaries, which matters when a shared library is consumed by many services. Batch changes apply a scripted edit across many repositories and track the resulting pull requests, which is how a large-scale refactor is coordinated. The product is open source in its core and available as a self-hosted or cloud deployment. It is aimed at organisations large enough that code is spread across many repositories; a small team with a handful of repositories will find a local search tool sufficient and the indexing overhead unjustified.

Ghost is a publishing platform that combines a website, a newsletter, and paid membership in one system. A publication runs on Ghost, posts are delivered by email to subscribers, and paid tiers are managed through the same admin rather than through a separate membership plugin. The product is open source and can be self-hosted, and the hosted service is the commercial offering. Subscriptions are handled through Stripe, with the platform managing member records, tiers, and gated content. Because the site and the newsletter are the same system, a post does not have to be maintained in two places. The tradeoff compared with a hosted newsletter service is that Ghost expects the publication to be a website first. It is a good fit for a writer or a small media business that wants a domain, an archive, and a subscriber list under its own control; it is a heavier tool for someone whose only need is to send an email to a list.

Biome is a toolchain that replaces a formatter and a linter with a single Rust binary. It formats JavaScript, TypeScript, JSX, JSON, and CSS, and it lints the same file set, so a project configures one tool and runs one command instead of coordinating several. The project began as a fork of Rome Tools after that project was discontinued, and it inherited the goal of unifying the tools that a JavaScript project normally assembles from separate packages. Because the implementation is compiled, checks run without the startup cost that accumulates when several Node-based tools each parse the project separately. Diagnostics are designed to be actionable: a lint error points at the rule, explains the problem in prose, and in many cases offers a safe fix that can be applied automatically. The main limitation is breadth. Biome's rule set does not yet cover everything a mature ESLint configuration with type-aware rules can express, so projects with heavy custom lint requirements sometimes run both.

Discourse is forum software designed for threaded, long-form discussion. Unlike a chat product, a topic is a first-class object with a title, a category, and replies that can be read in order, which makes a community's history searchable and referenceable. The platform adds the mechanics a community needs to stay healthy: trust levels that grant permissions as a member participates, flagging and moderation queues, and automated summaries. Topics can be categorised and tagged, and a topic can be marked as solved so the answer is visible without reading the thread. Discourse is open source and can be self-hosted, with a hosted plan as the alternative. It is a good fit for a product community, a support forum, or a standards discussion where answers should be findable later. It is a poor fit for real-time conversation, which is what a chat product is for.

Hono is a web framework for JavaScript runtimes. The same application code runs on Cloudflare Workers, Deno, Bun, Node.js, and several other environments, because the framework targets the standard Request and Response interfaces rather than a runtime-specific API. The core is deliberately small. Routing is built on a radix tree, middleware composes as a chain, and the framework adds typed helpers for the things an HTTP service needs: parsing input, validating it, setting headers, and returning JSON. Type inference carries path parameters and request bodies through to the handler, so a route can be typed without a separate schema layer. Hono is a good fit for APIs, edge functions, and small services where a full application framework would be excess weight. It is not trying to be a batteries-included framework: there is no built-in ORM, no opinion about the frontend, and no plugin ecosystem of the size a larger framework has accumulated.

Directus is a layer that sits on top of an existing SQL database rather than replacing it. Point it at a database and it introspects the schema, then generates a REST and GraphQL API plus an admin application for the tables it finds. The database remains the source of truth. That inversion is the main difference from a conventional CMS. Content is not locked in an application-specific structure: the tables are ordinary SQL tables, readable by other tools and migrations. Custom fields, relations, and permissions are configured in Directus and stored in the same database, so a DBA can still work with the schema directly. The product is open source and self-hostable, with a paid cloud offering. It fits teams that already have a database and want an admin interface and API over it without migrating. It is a weaker fit when the schema is expected to change constantly, since the database is the contract.

Lemon Squeezy is a payments platform for software businesses that acts as the merchant of record. That means the company is the legal seller of record for each transaction, and it takes on the obligations that follow: sales tax and VAT registration, collection, and remittance in the jurisdictions where a customer buys. For a small software business selling internationally, that is the whole proposition. Instead of registering for VAT in the EU, the UK, and elsewhere as revenue grows, the seller handles one counterparty. The platform provides checkout, licence keys, subscription management, and a customer portal, and it pays out on a schedule. The cost is a higher percentage per transaction than a plain payment processor, because the merchant-of-record role absorbs tax and compliance work. Businesses with high volume sometimes move to a processor and handle tax themselves once the fee difference exceeds the cost of doing so.

Zed is a code editor written in Rust and rendered on the GPU. The performance goal is the product's identity: startup, scrolling, and search are fast enough that the editor stays out of the way on very large files. The second distinguishing feature is collaboration. A shared project gives other people the same buffer, cursor, and terminal, so pairing is a mode of the editor rather than a separate screen-share. Channels let a team keep a persistent room for a project. Zed is open source. The editor itself is published in a public repository, and the collaboration service is the commercial layer. That split - an open editor with a hosted service on top - is the same pattern several developer tools use, and it means the editing experience can be inspected and self-built while the multiplayer backend remains a paid product.

Duolingo is a language learning application built around short, frequent practice sessions. A lesson is a few minutes of exercises: translate a sentence, match a word to an image, or complete a phrase by tapping word tiles. Progress is measured in a streak of consecutive days rather than in completed units. The design choices are deliberate. Lessons are short enough to fit into a gap in the day, the streak creates an incentive to return, and the difficulty curve is gentle enough that a beginner is not blocked early. A spaced-repetition system decides which vocabulary to revisit, and mistakes are reintroduced rather than dropped. The limitation is depth. The platform builds vocabulary and recognition well but does not, on its own, produce conversational fluency: there is no live conversation partner and limited open-ended production. Learners aiming at fluency typically combine it with speaking practice elsewhere.