Frequently Asked Questions

Apso is a backend generation platform. You define your data model in a .apsorc schema file, and Apso generates a complete production backend with REST API endpoints, authentication, multi-tenancy, database migrations, and AWS deployment infrastructure. The output is real TypeScript, Python, or Golang backend code in your repository. You own every line.

Firebase and Supabase are managed platforms. You build on top of their proprietary runtime and your backend logic lives inside their system. Apso generates standard backend code that you own and deploy yourself. There is no Apso runtime in the output. Stop using Apso and the code keeps working. Apso also supports Bring Your Own Auth, so you are not locked into a single provider.

When an AI agent writes your backend, the output varies with the model, the prompt, and the day. Two services built a week apart follow different patterns. When the model upgrades, your code changes. Apso puts the guardrails in the generator, not the model. The same schema produces the same output on any model. The agent decides what to build. The CLI decides how.

TypeScript, Python, and Golang. The generated code follows each language's conventions and includes full type definitions, so your team works with familiar tools.

Yes. The generated code is standard backend code with no Apso imports, no vendor SDK, and no proprietary runtime. It compiles, runs, and deploys with or without Apso. The templates are Apache-2.0 licensed.

PostgreSQL on Amazon RDS. Each service gets its own database instance with automated backups, point-in-time recovery, and encryption at rest. The generated code uses TypeORM for TypeScript, SQLAlchemy for Python, or GORM for Golang.

Apso uses Bring Your Own Auth (BYOA). Configure BetterAuth, Auth0, Clerk, AWS Cognito, API keys, or custom sessions. The generated auth guard produces a normalized AuthContext interface, so your business logic works the same regardless of which provider you choose. Switch providers by regenerating.

Yes. Generated code lives in src/autogen/ and is rewritten on every regeneration. Your custom business logic goes in src/extensions/ and is never touched. Regenerate as many times as you want without losing your work.

Application-layer data scoping. Add a scopeBy field to your entities and Apso generates guards that automatically filter queries by the authenticated user's workspace. This works at the application layer, not at the database layer, so it is portable across databases and cloud providers.

Yes. The CLI includes a built-in MCP server. Any MCP-capable editor (Claude Code, Cursor, Copilot) can discover and operate Apso without leaving the IDE. The agent calls the CLI, and the CLI enforces the guardrails.

CLI generation is free forever on every plan. The Free tier includes 1 hosted service for testing. Pro is ~$25 per service per month with always-on compute, backups, custom domains, and 100 credits. Team is ~$99/mo flat with unlimited members. Enterprise plans have custom pricing with SSO, audit logs, and SLA guarantees.

A shared balance for AI actions and deployments. About 1 AI action equals 1 credit, and 1 deploy equals 1-2 credits. Paid services include ~100 credits per month. Bring your own AI key to make AI actions free. No silent billing. Opt-in capped auto-refill only.

No. The generated code has no Apso runtime dependency. It is standard TypeScript, Python, or Golang backend code that compiles and runs without Apso. Ejection from managed hosting is free and clean. You pay for the automation, not for access to your own code.

Yes. With Your Cloud (BYOC), you pay a per-service automation fee to Apso and your cloud provider directly. Apso never marks up your cloud bill. Available on Pro and above.