Choose a Service Target
The target determines what StationOps builds and where the resulting artifact runs. Choose it before filling in target-specific settings.
Select a Build Method
Server targets can build from commands with Nixpacks or from a repository Dockerfile. Static targets produce static assets, while function targets use a ZIP or container image depending on the service configuration.
For functions, choose the runtime and CPU architecture supported by the application. For servers, configure CPU, memory, port, health checks, and scaling per environment.
Control Function Concurrency
Function services can set Reserved Concurrency separately for each environment. Leave it blank to use the AWS account's unreserved concurrency pool. Set it to 0 to deliberately throttle all invocations, or enter a positive whole number to reserve and cap concurrent executions for that function.
Use the bulk-edit panel when the same reservation should be applied across several function services or environments. Removing a reservation returns the function to the account's unreserved pool. Review this setting carefully before deployment: reserving capacity can limit the concurrency available to other functions in the account.
Decide Before You Configure
- Choose Static only when the deployed artifact does not need a server process.
- Choose Function for bounded executions that fit Lambda's runtime model.
- Choose Managed Server for most containerised web services and workers.
- Choose Server when the workload specifically requires EC2-backed capacity.
- Choose Runner for build or automation jobs.
- Choose Mobile when StationOps should produce signed store artifacts.
Changing Targets
Changing a target can replace the deployed AWS resources and may make existing build settings invalid. Review the infrastructure diff and the service's removal behavior before deployment.