1U Application Server -- the entry model. 6 CPU units, 6 RAM units, which is enough for the Base Runtime plus two or three modest services, not enough for a hosting stack.
An application server does nothing at all on its own. It is a host for SOFTWARE: give it a NAS share the same way you would a game server, then open its Inspector and press Install software. Pick what you want -- anything it depends on is installed with it, and the price on the button is for all of it.
IT WILL NOT START WITHOUT STORAGE. Every service installs onto a NAS share and running services keep writing to it. Add a share for this device from any NAS in the rack before you buy software, or the installer will refuse.
Prefer a keyboard? `svc list`, `svc install <id>`, `svc status`, `svc start|stop`, `svc rm` do the same things from any terminal or KVM console, faster once you know the ids. See man appservers.
Storage fills FASTER here than anywhere else in the rack, and that is deliberate -- a logging or hosting service that never grew would not be much of a simulation. Watch the storage bar in the Inspector, and treat the Backup Agent as the first thing you install after the runtime, not the last.
Power scales with what is actually running. An idle app server draws close to its 90W typical; one running a full service load approaches 260W. `svc status` and the Inspector both show the current draw and what is causing it.
Services can depend on other services. Alert Manager without a Metrics Collector is inert, and the installer will tell you so rather than letting you buy something that cannot run.
Takes the Redundant PSU upgrade -- see man redundancy.
Browse and install software from any terminal with svc list and svc install <id>. The full breakdown — every service, dependencies, storage growth and the tenant seats that pay you — is in the Player Guide.