2U Application Server -- the middle model. 14 CPU units and 16 RAM units, roughly two and a half times the 1U, in twice the rack space.
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.
Tenants occupy SEATS on hosting, analytics and communication services, and each occupied seat pays. More seats means more revenue, more storage growth and more power -- the three move together on purpose.
90W idle, 480W under a full service load. That is a wide band, so a rack that was comfortable with this device idle can trip a PDU once you fill it with services. Size the feed for the load you intend to run, not the load it arrives with.
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.