The parts that deserve a page.
Most of Talus fits in a bullet on the home page. Some capabilities carry a promise you should understand before you trust them. Each page here follows the same three headings: what it does, what you need, and what it deliberately does not do.
Where it runs
Talus runs on a Linux virtual machine: under Hyper-V on your Windows server, under VMware or Proxmox, or directly on any Linux server with Docker. It is the same product in each case, with the same data, the same upgrades, and the same backups. On Windows, VMware, or Proxmox you create one Ubuntu virtual machine (the install guide has the page for it, about twenty minutes once) and the installer does the rest in under three minutes; you never need to work in Linux beyond the commands in the guide. On a Linux server one command brings up the whole stack.
Your databases
A read-only, scheduled copy of a table or view from SQL Server, PostgreSQL, MySQL, or MariaDB: work orders, permits, billing, an SDE geodatabase. Talus never writes back, your DBA's view is the filter, and a failed refresh keeps the last good copy.
More pages arrive as capabilities grow. If one you care about is missing, ask; the answer may already be in the FAQ.