Deployment

Generated services can run through Apso Cloud or with the normal deployment process for NestJS, FastAPI, or Gin. Choose the path from your team’s ownership, network, compliance, database, and operations requirements.

Deployment pathsChoose where the backend runs.

Same repository

Your serviceFramework code + migrations + infrastructure

Managed path

Apso Cloud

Use Apso's deployment workflow for the service, database, migrations, and environment configuration.

apso deploy

Portable path

Your cloud

Deploy the generated application with Docker or your existing AWS, CI/CD, and observability stack.

docker build .

Hosting can change without changing the product contract or giving up the generated source.

Options

Link a service, synchronize its repository, validate migrations, and trigger a platform build

Apso Cloud

Run the generated framework in infrastructure managed by your team

Self-hosting

Build and run the generated service as a container

Docker

Validate generated diffs and deploy committed source from automation

CI/CD

Choose the boundary

Question	Apso Cloud	Self-hosted
Who operates the service deployment?	Apso platform workflow	Your infrastructure team
Where are runtime variables managed?	Service Environment view	Your secret and configuration system
How is source delivered?	Connected GitHub repository	Your build pipeline or image registry
Who owns network and runtime policy?	Platform according to the selected plan	Your team
Can the framework source be moved later?	Yes	Already in your repository

Required checks

Validate .apsorc and regenerate.
Review the generated diff.
Run apso migrate and inspect database changes.
Run framework tests and the production build.
Configure runtime variables outside source control.
Verify /health and /_docs after deployment.
Exercise one authenticated read and write.
Record the deployed commit and rollback process.

Framework builds

Target	Typical checks
TypeScript	`npm test` and `npm run build`
Python	`pytest` and `python -m compileall app`
Go	`go test ./...` and `go build ./...`

Use the generated project scripts as the source for its exact build and migration commands.