Open-source GIS for enterprise deployments

An enterprise GIS you can run yourself — without running a pile of parts.

Talus GIS replaces ArcGIS Enterprise for organizations that don't need exotic features. One install, upgrades that are tested before they ship, and a company that supports it.

Talus GIS mark
Why Talus?

Self-hosting usually brings back the complexity you were trying to leave.

Talus is built to be the exception: one product, not a pile of parts. We make that case objection by objection, each claim paired with its receipt.

Read why Talus →

What is in the box

The 80% of enterprise GIS.

Field data collection, web maps with simple editing, and sharing. A system that cleans up after itself, works with ArcGIS Pro and QGIS, with strong disaster recovery options.

Portal and governance

  • One catalog for layers, tables, rasters, and web maps: ownership, favorites, transfer, delete protection, where-used
  • Sharing that is private, group, organization, or public, enforced fail-closed
  • ISO 19115 metadata with a completeness gate and a curated Open Data portal with a DCAT-US feed
  • User management with SSO and local accounts, service accounts, backups, and maintenance in one admin area

Data and editing

  • Hosted point, line, polygon, and table layers provisioned on demand, with no publish step
  • Owner-defined fields, coded-value domains, constraint rules and defaults, all on PostgreSQL primitives
  • Bulk import of Shapefile, GeoPackage, GeoJSON, and CSV at county scale, with dry-run preview and reprojection
  • Optimistic concurrency, per-row audit trails, attachments, and view layers as sanitized shareable lenses

Mapping

  • Web map authoring: basemaps, filters, labels, popups, bookmarks, map notes, docked attribute tables
  • Fuzzy feature search and address geocoding, including a fully air-gapped internal geocoder over your own addresses
  • Street maps from the first sign-in: streamed from OpenStreetMap, or downloaded to your own server for offline use. No metering either way
  • GeoTIFF, JPEG 2000, and ERDAS IMG rasters served as tiles
  • PNG and one-page PDF export from the browser; the PDF is georeferenced and opens as a map in Avenza Maps and QGIS

Interoperability

  • OGC API Features, WMTS, and a GeoServices (FeatureServer) façade: ArcGIS Pro and QGIS read and edit Talus layers, attachments included
  • One credential-free connection file exposes the whole viewable catalog in Pro or QGIS
  • A documented /api/v1 with scoped service-account tokens, so you script from your own compute
  • Read-only copies of tables from the databases other systems own, work orders, permits, utility billing, refreshed nightly. SQL Server, PostgreSQL, MySQL, and MariaDB today, through a read-only login; Talus never writes back

Operations and trust

  • Scheduled backups of every database plus media with optional encryption to keys only you hold, an off-host destination with a connection test, and rehearsed restore drills
  • Self-maintenance jobs that structurally cannot touch your layers, features, or audit log
  • Nothing phones home: no telemetry, no update checker, no license server
  • Per-release software bill of materials and digest-pinned images

Deliberately not

3D, routing, Utility Network, Parcel Fabric, and heavy imagery analytics are non-goals, not gaps on a roadmap. Shedding the exotic 20% is what keeps Talus one host and one install.

Two editions

Talus Community and Talus+

Community is the complete GIS, free under the AGPL, with no AI in it at all. Talus+ is the one paid tier: support, the paid modules, and the AI assists. Either edition runs air-gapped.

Compare editions →

Built with AI, in the open

Directed by GIS professionals, implemented with AI, disclosed up front

Talus is built by a team with more than thirty years of GIS experience, with AI as the implementer, under a decision-before-code discipline. We say so plainly, because the safeguard is the process, not a secret.

How it's built →

Try it on one machine this afternoon.

Download the release, read the installer and the compose file, and bring the stack up. The install runbook is in the repository, and there is a person at the other end of the mailbox.