Clear answers about the backend foundation

Apso is the backend foundation for AI-built software. Your agent helps define the product and data model. Apso turns that intent into consistent APIs, migrations, infrastructure, and normal TypeScript, Python, or Go code in your repository.

Firebase and Supabase provide hosted backend capabilities through their platform model. Apso generates the application service itself as code your team can inspect, modify, test, and operate. The important distinction is where the backend logic lives and what your team can take with it.

An agent is excellent at turning product intent into a proposed system. Apso gives that agent a repeatable generation boundary, so APIs created at different times follow the same service structure and security patterns. The agent shapes what you need, and Apso keeps the resulting foundation consistent.

Apso generates TypeScript with NestJS, Python with FastAPI, and Go with Gin. The output follows each framework's normal project structure and tooling.

Yes. The generated backend lives in your repository. Your team can extend it, run it without Apso, and move it to another infrastructure provider. There is no proprietary Apso runtime required by the generated service.

Apso turns Claude, Codex, or another compatible coding agent into an Apso specialist. Rules teach the agent Apso's architecture and guardrails. Task skills teach workflows such as schema design, auth, migrations, and feature development. MCP tools ground that expertise in the current project and let the agent inspect, validate, generate, and test without making you translate the work into CLI commands.

Generated services use PostgreSQL. TypeScript services use TypeORM, Python services use SQLAlchemy, and Go services use GORM. Deployment configuration depends on the infrastructure model you choose.

Apso supports a bring-your-own-auth approach. The generated service receives a normalized authentication context while your team chooses the identity provider and session model that fit the product.

Yes. The service is normal framework code. Generated areas and extension points are separated so your team can add business logic while continuing to evolve the underlying schema and generated resources.

Tenant boundaries are represented in the schema and enforced in the generated application layer. Resources can be scoped to a workspace or tenant so list, read, create, update, and delete behavior applies the same boundary.

The Free plan is $0. Pro managed services are $25 per service each month. Team is $99 per workspace each month with unlimited members. Your Cloud starts at $40 per service each month plus your cloud costs. Enterprise pricing is based on infrastructure and governance requirements.

No. The Team plan includes unlimited members in the workspace. Managed production services are billed separately.

The generated service has no required Apso runtime. The code remains in your repository and can continue running if you stop using Apso. Managed infrastructure and automation are separate from your ownership of the backend code.

Yes. Your Cloud keeps Apso generation and deployment automation while the infrastructure, credentials, and cloud bill stay in your account.