Deployment

Server

nagi serve runs as a single process. The following table summarizes deployment patterns for different execution environments.

Pattern	Use case	Storage backend
Local	Development and testing	local
VM	Running as a persistent process	local
Container	Container environments such as Cloud Run	remote (GCS / S3)

For architecture details, see Serve Internals. For storage backend details, see Storage.

Client

When using a remote storage backend, you can use the CLI as a client from an environment separate from the server.

Configure the same remote storage backend as the server in the client environment's nagi.yaml.

• nagi status — Check the state of each Asset
• nagi evaluate / nagi sync — Manual execution
• nagi serve resume / nagi serve halt — Control serve