Infrastructure
The platforms this product runs on and the datastores it needs: what ships inside it, and what you supply.
For the platform owner deciding whether this fits the estate you already run.
After reading it you can say which of your hosts can run it, in which form, and which datastore you will have to supply.
Before you start: nothing. These three answers come before an install, not after.
Two questions decide whether this product fits your estate, and they have short answers.
| question | answer |
|---|---|
| which platforms | Linux and macOS run it natively. Windows runs it virtualized — the server as a container, agent machines as Linux containers or virtual machines — see Supported platforms |
| which form for agent machines | a host, a container image (the Team and Enterprise shape, with a template per language class), or a Linux virtual machine — see Agent machines |
| which datastores | a single-file store is built in and needs nothing from you. PostgreSQL and CouchDB are the stores you supply when you outgrow it — see Datastores |
⚠ This section is deliberately short today. The platform answer is complete; the datastore pages are a first pass — enough to plan an installation around, not yet enough to tune one. Where a page stops, it says so rather than leaving you to discover the edge.
What this section does not cover
⚠ Sizing and tuning. The datastore pages are enough to plan an installation around and not enough to tune one — no capacity model, no sizing table, no benchmark. ⚠ Backup and restore of the record has no page anywhere on this site; what the databases hold, and which of them are the only copy, is here.