Architecture

Understand how Apso works under the hood. This section is for developers and technical leads who need to know what Apso generates, where platform boundaries are, and how the generated backend behaves after it leaves Apso.

Overview

Apso is a code generation platform that produces production-ready backend applications. Unlike traditional BaaS platforms, Apso generates real code that you own.

Architecture Topics

How APSO’s code generation platform works

Platform Architecture

Structure and layers of generated applications

Generated Code

Authentication, authorization, and data isolation

Security Model

Horizontal scaling, caching, and performance

Scaling

Key Principles

Code Ownership

You own 100% of the generated code. There are no:

Runtime dependencies on APSO
Black box components
Vendor lock-in

This is the core architecture decision. Apso should help you get to a working backend faster, but your production system should remain understandable as standard NestJS, FastAPI, or Go code.

Clean Architecture

Generated code follows clean architecture principles:

Domain-driven design patterns
Clear separation of concerns
Dependency injection
Interface-based abstractions

Extensions Over Modifications

The extensions pattern keeps your customizations safe:

Generated code is regeneratable
Custom logic lives in extensions/
Schema changes merge cleanly

Security First

Built-in security patterns:

Multi-tenancy with data isolation
JWT-based authentication
Input validation on all endpoints
SQL injection prevention