LMSY Match — reuse analysis for your project
LMSY Match reads your idea, URL, GitHub repository, Figma file or screenshot and shows exactly what you can reuse from the LMSY catalog — with hours saved, price and a build plan. Every number is computed from the live catalog of 229 production-ready building blocks: 49 business modules and 180 platform connectors, backed by 1,741 API endpoints.
How the numbers are computed
Match decomposes your project into required capabilities, then matches them deterministically against catalog modules. AI only decomposes the request — module selection and all numbers (hours, price, reuse percentage) are derived server-side from real per-module data.
Nothing is invented: if a capability has no matching module, it is honestly counted as custom work. Draft and hidden modules are never counted.
Definitions
- Business Module
- A Business Module installs real backend and frontend logic into YOUR project (Express routes, React components, database schema). You bring your own API keys (BYOK) and the installed code stays yours forever, even if the subscription ends. The catalog currently contains 49 business modules.
- Platform Connector
- A Platform Connector installs a thin, license-gated proxy plus a typed SDK and React hook. The code is local, but the functionality runs on the LMSY-hosted platform, so an active LMSY subscription is required at runtime. The catalog currently contains 180 platform connectors.
- API Endpoint
- A concrete HTTP route (method + path) exposed by the LMSY platform. The live inventory currently counts 1,741 API endpoints; the number is scanned from running code, not maintained by hand.