Develop
Follow the path from product idea to production service. Each stage ends with something you can inspect or run, so backend decisions stay visible while the application grows.
Build with your coding agent
Connect Claude, Codex, or another MCP-compatible agent to Apso. The agent receives the schema reference, the current project, backend operating rules, and tools for design, validation, generation, diagnostics, and deployment.
“Add team invitations with owner and admin roles. Explain the tenant boundary, then build and test the workflow.”
- 01InspectRead the current project and schema.
- 02ModelPropose entities, scope, and permissions.
- 03GenerateBuild from the validated contract.
- 04VerifyRun migrations, tests, and one real workflow.
Set up AI-assisted development →
Find the right guide
| Goal | Start here | Verify before moving on |
|---|---|---|
| Model a product domain | Schema design | Entities, relationships, indexes, and tenant ownership are explicit |
| Generate or change a service | Tools and workflows | The schema validates and the framework build passes |
| Choose a backend stack | Frameworks | Your team can run its normal build and test commands |
| Protect API requests | Authentication | Identity, authorization, and tenant scope are separate decisions |
| Connect a web or mobile client | Frontend integration | Credentials stay server-side and one real workflow succeeds |
| Test a product change | Testing | Schema, generated code, extensions, and API behavior are covered |
| Prepare a schema change | Migrations | Destructive operations are reviewed before they run |
| Ship the service | Deployment | Configuration, migrations, health checks, and rollback are ready |
Keep the ownership boundary clear
Treat .apsorc as the contract. Regenerate structural code when that contract changes, and keep product-specific behavior in the preserved extension layer. This keeps changes predictable without hiding the framework code your team runs.