The independent developer field guide
Make sense of the technologies behind your next build. Explore APIs, frameworks, AI systems, developer tools, and hosting—with practical guides for the decisions between them.
Your route through the stack
Thirty focused guides. Six ways to explore. Follow the layer that matters to your project, then connect it to the rest of your system.
Map the system, define the API, and connect architecture choices to real project needs.
Compare publishing workflows, application frameworks, starter templates, and design decisions.
Plan model boundaries, evaluation, data handling, and the meaning of API tokens.
Make macOS, Linux, Cursor, and VS Code fit a reproducible development process.
Understand VPS and dedicated hosting, self-hosting, service ownership, and recovery.
Read public technology signals carefully and keep observation separate from inference.
New to the terminology? Start with components, responsibilities, and the connections between them. You do not need to choose every technology at once.
Start with the fundamentalsFrameworks & publishing
Trace the change your team needs to make: publish a page, add a permission, expose a resource, or ship a new workflow. That path tells you more than a feature checklist alone.
AN AI APPLICATION, LAYER BY LAYER
A conceptual planning map. Select a layer to explore its design decisions.
AI Stacks API / LLM Stacks API
An AI feature belongs to a larger system. Map where context comes from, what the model may influence, how you evaluate behavior, and what happens when a dependency fails.
Technology research
Build a useful picture of web technologies by documenting what you observe, how you interpret it, and what remains unknown.
Keep the source, page, date, and exact signal together. A script reference, header, or repository declaration belongs to a specific observation.
Understand “built with” evidenceSeparate a visible clue from the architectural claim you draw from it. Consider stale assets, shared services, and incomplete external visibility.
Plan a fair comparisonPublic technology research and authorized forensic examination have different purposes. Define the question and the access you actually have.
Read about evidence and scopeStacks API Lab
Long-form guides for people evaluating, building, and maintaining software stacks.
A technology list becomes useful when every entry explains what it describes, how it was verified, and who maintains it. Build an inventory that supports upgrade planning, developer onboarding, and honest conversations about uncertainty.
Read the guide : Build a Tech Stack Inventory That Developers Can Trust
An LLM feature needs more than a model choice. Map the application, data, evaluation, and operating responsibilities first, then compare architectures using representative tasks and measured outcomes instead of unsupported performance promises.
Read the guide : Design an AI and LLM Stack Around Boundaries and Evidence
A SaaS starter can shorten setup while introducing assumptions you must own. Evaluate one through a real product journey, tenant boundaries, accessible interfaces, operating costs, and the ability to maintain or replace its dependencies.
Read the guide : How to Evaluate a SaaS Starter Template Before Building on ItA little more context
Start here, then follow the guide that matches your project.
StacksAPI.com is an independent guide to software technology stacks and APIs. Explore practical explanations of frameworks, developer environments, AI architecture, hosting, and technology research. Start with the Stacks API guide to understand the scope.
The site provides editorial guides and decision frameworks. To plan your own inventory or assess a third-party service, use the tech stack inventory guide and public technology evidence guide.
Start with your workload, team skills, maintenance ownership, and the change you need to make. The framework evaluation guide proposes a repeatable project spike; the hosting guide traces operational responsibilities.
These names identify the technologies discussed in the guides. StacksAPI.com is an independent publication. Use each project’s official documentation to verify its behavior and requirements; the guides link to relevant primary sources.
Tokenized API design can refer to access credentials, metered service credits, or blockchain-linked entitlements. They solve different problems. The tokenized Stacks API guide separates identity, authorization, accounting, and transfer rules.
Map one application you know: its interface, runtime, data, services, and hosting. Then read Build a Tech Stack Inventory That Developers Can Trust. You can use the stack atlas to explore the next unfamiliar layer.
Start with one useful question. Follow it through the system.