Your databases
Work orders, permits, utility billing, and SDE geodatabases: the systems an enterprise already runs keep their data in RDBMS databases. Talus can hold a read-only copy of a table or view from one of them and refresh it on a schedule, so the asset and its open work sit on one map without anyone exporting a spreadsheet on Monday morning.
What it does
A publisher adds a connection to SQL Server, PostgreSQL, MySQL, or MariaDB, tests it, and picks a table or view. The wizard shows what identifies a row, lets them choose the columns, and asks how rows are placed: not at all for a plain table, from two coordinate columns, or, for an address column, as a plain table you geocode as a separate step; that point layer is a copy made then and does not refresh with the pull. They set a refresh, nightly at an hour of their choosing or every few hours, and run it. The result is an ordinary Talus table or point layer that goes on maps and into dashboards and reports and can be shared like anything else in the catalog.
A refresh writes only what changed. Rows that are the same cost nothing; a changed row is updated in place and keeps its Talus id, so bookmarks, relates, and selections survive; rows gone from the source are removed from the copy. A table with a primary key or a unique index is matched by that key, OBJECTID included. A view with no key is matched by the content of each row, so it works too.
When a refresh fails, because the server is down, a column was renamed, or the login was revoked, the last good copy stays exactly as it was and the pull shows a stale badge with the plain-language reason. The schedule keeps trying at its next slot. While a source is attached the copy is locked against editing inside Talus, enforced by the database rather than a checkbox; detaching the pull turns the copy into an ordinary editable table and ends the refresh.
What you need
The host, port, database name, and TLS requirement; if the server presents a certificate from your own certificate authority, the CA bundle pastes into the connection. The server's local time zone, for timestamp columns that carry none.
A Talus install inside your network. The Talus server has to reach the database server directly. Use a read-only SQL login, the same kind of viewer account most shops already keep for public-facing database or SDE access. Talus stores the password encrypted, shows it to no one afterwards, and keeps it out of every log.
Connections belong to the person who made them. Another publisher cannot see, use, or remove them. An administrator's overview lists every connection with its host and owner, never the secret, and can remove one for oversight. If the owner is disabled or set to a role below publisher, their pulls stop refreshing and say why; if a pulled layer is transferred to someone else, it is detached at that moment, because a personal credential does not follow a layer to another person.
What it deliberately does not do
It never writes to your database. The only statements it issues are SELECTs against the table or view you chose. On PostgreSQL, MySQL, and MariaDB the session is also set read-only; SQL Server only declares read-only intent, so give Talus a login that can only read. There is no WHERE clause and no free-text SQL. If you want a subset, your DBA creates a view; the view is the filter, and it is also where the permission lives. It is not an ETL tool. A column list, a type mapping, and a coordinate pair are the whole shape of a pull; transforms, merges across sources, and scripting are not coming. It does not read an SDE shape column directly yet: expose the coordinates as two columns in a view. Lines and polygons are a later step. Classes stored as SDEBINARY or ST_GEOMETRY cannot be read outside ArcGIS by anything; Esri's Migrate Storage tool converts them. Not yet: Oracle, and Windows authentication to SQL Server. Ask your DBA for a SQL login, and if your shop cannot issue one, tell us.
Talus also refuses to connect to its own services, loopback, and cloud metadata addresses, by name and by resolved address, so the connection form can never become a door into the Talus stack itself.
See for yourself.
Bring the stack up on one machine inside your network, add a read-only login, and pull one view.