Skip to Content
Apso is in public beta. Get started
Home

Apso developer documentation

Build a backend you can own

Give your coding agent Apso’s backend expertise, define the application in .apsorc, and generate consistent APIs, migrations, infrastructure, and service code your team can extend and own.

NestJSTypeScript + TypeORM
FastAPIPython + SQLAlchemy
GinGo + GORM
PostgreSQLLocal or hosted

Why Apso

Apso gives teams a direct path from a product model to backend source code they can inspect, extend, and deploy.

Schema as the contract

Entities, fields, relationships, and generation settings live in one version-controlled file.

Consistent backend generation

Apso applies one repeatable structure to NestJS, FastAPI, or Gin service code without requiring an Apso runtime.

Custom logic stays separate

Regeneration rewrites autogen/ and preserves the endpoints, hooks, and business rules in extensions/.

Choose your starting point

Use the path that matches how you work. Every path produces the same schema contract and generated service structure.

Start with a product-shaped backend

The Apso service builder includes 27 starter briefs. Each starter describes the entities and relationships for a working application domain.

See all 27 starter backends →

Connect your frontend

Call the generated REST API directly or use @apso/sdk from a JavaScript or TypeScript application.

Understand the system

Four boundaries keep the workflow understandable as the application changes.

01Product modelRequirements or starter brief
02.apsorcReviewable schema contract
03autogen/Generated framework layers
04extensions/Product-specific behavior
Read the architecture guides →
Last updated on