“Open-source GIS is too hard.”
That is the honest default view of open-source GIS, and it is usually right. Assembling your own stack moves the cost from the license line to setup and maintenance. Talus exists to be the exception, and each claim below comes with receipts.
“It will take weeks to stand up, and someone who’s an open-source specialist to do it.”
One host with Docker. One installer script brings up the whole stack from one compose file: portal, database, identity, authorization, tiles, and the TLS edge.
Receipt: 1 minute 59 seconds from a clean machine to a healthy stack on the shipped installer, with zero hand holding.“Things break at the integration points.”
There are no integration points to break. Talus is one product with one configuration, not a bundle of projects glued together. The portal is the coherence layer: every surface, including QGIS and ArcGIS Pro, goes through one authorization-gated API.
Receipt: no publish step, no slot pools, no separate map server to babysit. A layer exists the moment you create it, everywhere.“Upgrades on open-source stuff are a nightmare.”
An upgrade is a versioned release you pull, not a project you plan. Every container image is pinned by content digest, migrations run in order on their own, and every release is rehearsed on a test server, so it never depends on anything hand-tuned on our machines.
Receipt: the upgrade runbook and the restore runbook ship in the repository, and both are rehearsed.“Open source means there is nobody to call.”
Talus GIS LLC builds it, maintains it, and takes responsibility for it. Talus Community is free and stays free under the AGPL. Talus+ adds support, the paid modules, and the AI assists, on legible, predictable pricing.
Receipt: stop paying if you want, and you keep everything installed, forever. There is no kill switch and no license server that can turn your GIS off.“How can I host open source GIS in the cloud?”
Run Talus on any cloud server with Docker, using the same installer as everyone else: a Linux virtual machine of four vCPUs and 8 GB at whatever provider you already use. Nothing about a cloud copy is special, and nothing on it is shared with anyone else.
Receipt: the where it runs section lists the options. Your backups can be encrypted to a key only you hold, and moving between a cloud server and your own is a restore, not a migration.“But can it handle our data?”
Validated against real data: 12,000+ signs, over 300,000 address points, 35,000 street segments, a 308,000-polygon county parcel layer, and orthoimagery. Bulk import moves layers of that size through the product doors on flat memory, and the photos and documents attached to features ride along as managed objects: access-controlled, visible in the web portal, ArcGIS Pro, and QGIS, and backed up with the database.
Receipt: a 300,000+ feature parcel layer on four vCPUs serves roughly 150 named users at typical duty cycles. Adding CPU raises that ceiling.“Is it secure?”
Standards-based sign-in, fine-grained authorization that fails closed, and an audit trail of every change to a record, with actor attribution. A negative-test suite ships in the repository so you can prove deny-by-default on your own install rather than take our word for it.
In practice: TLS everywhere out of the box, with certificates obtained and renewed automatically, or issued from a private CA for air-gapped sites. Stored third-party credentials are encrypted at rest, access tokens are kept only as hashes, and backups can be encrypted client-side to keys the server never holds. Every new data path gets a security review and negative tests, every change must pass CI scanners that fail on high and critical findings that have a fix, and every release ships a software bill of materials with digest-pinned images.See for yourself.
Download the release, read the installer and the compose file, and bring the stack up on one machine. Then compare editions when you know it fits.