Apso Documentation

Define your data model. Generate a production-ready API. Own the code.

Get started with the Quickstart or read the Core Concepts to understand how Apso works.

Why Apso

Apso is for teams that want backend speed without giving up code ownership. It sits between hosted BaaS products and hand-written backend work: you describe the system once in .apsorc, then Apso generates a standard framework service you can run, test, extend, and deploy.

Ship faster. Stop writing repeated CRUD, DTO, controller, and migration code by hand. Start from the schema and spend your time on product logic.

Own your code. Apso generates standard framework code with no runtime lock-in.

Build with AI more safely. Give an assistant a single schema source of truth, then use the CLI to generate coherent backend code instead of one-off files.

Who It Is For

Founders and product engineers building a SaaS backend, internal tool, marketplace, CRM, CMS, or operational API.
Full-stack teams that want BaaS speed but need to own the generated backend and database model.
AI-assisted builders using Claude Code, Cursor, Codex, or similar tools to turn product requirements into working backend systems.

Apso is not a low-code runtime where your product lives inside someone else’s platform. It is a generator and workflow for producing backend code that belongs in your repo.

Use Apso Effectively

Model the smallest useful version of your product in .apsorc.
Generate code with apso generate.
Keep custom business logic in src/extensions/, not src/autogen/.
Test schema changes with apso migrate before touching a real database.
Deploy when the generated API, SDK, and migrations match the workflow your users need.

Get Started

Pick a starting point based on where you are.

Build your first API from a schema definition

Quickstart

Schemas, code generation, extensions, and multi-tenancy

Core Concepts

Install and use the @apso/cli command-line tool

CLI Reference

How Apso Works

You write a .apsorc schema file that describes your entities, fields, and relationships. The CLI generates a full backend with entities, REST controllers, services, DTOs, and database migration support. You extend the service in normal framework code and deploy it wherever you want.

Explore by Topic

Dig into the areas that matter for your project.

Define entities, field types, relationships, and multi-tenancy

Schema Design

Better Auth, BYOA, and API key strategies

Authentication

Apso Cloud, Docker, self-hosting, and CI/CD

Deployment

Platform internals, generated code, security, and scaling

Architecture