What ships
REST or GraphQL when you need it. Auth, roles, files, billing hooks, admin, jobs, and migrations. Documented so your team can extend it.
Server side is where money events, auth, and truth live. One API per product. PostgreSQL is the default. Web, mobile, and agents all speak to the same core.
REST or GraphQL when you need it. Auth, roles, files, billing hooks, admin, jobs, and migrations. Documented so your team can extend it.
Kotlin, Node, or Python. Pick for the job. This is not a logo wall. PostgreSQL, Redis, and search when the product needs them.
Domain first. Versioned APIs. Tests on the money and auth paths. The same deploy rail as the rest of the product.
RAG, tools, and agents attach here with guardrails. They are not a chatbot beside the product. See AI in the company.
Web and mobile need one API, one data model, and one place for money events.
A thin API behind one workflow can come before a platform. That first slice is valid.
Integrations and data migration dominate cost. Discovery lists them as dependencies. This page does not assume them.