Integration for local governmentPart of the Sentra family

Connect anything
with an API. Keep nothing.

SentraBridge moves records between your agency's systems, databases, maps and files, on a schedule or the moment they change. Records pass through in memory and are never stored.

Request a demo See live examples

Pass-through: no stored records
See the data at every step
Our cloud or your servers

A SentraBridge flow on the canvas with its data inspector open

Pre-built forThe Sentra family, the systems cities already run, and any database, map or file drop. All 52 connectors →

§ Watch it run

One flow, start to finish. Under a minute.

§ How it works

From two systems to one flow, in an afternoon.

Every SentraBridge integration is a flow you can see. Here's the whole path.

01ConnectSystems, databases, maps, files, or an OpenAPI file
02DrawRead, change, check, decide, write
03InspectReal records on every wire; nothing written
04RunBy hand, schedule, webhook or row change
05WatchCounts and IDs per run; replay failures

§ The core promise

Your records go from one system to the other. Not to us.

SentraBridge reads records into memory, changes them, delivers them, and drops them when the run ends. No copy to breach, retain or produce under a public-records request, and nothing extra for a data-sharing agreement.

How data is handled Why it matters

Records pass through SentraBridge in memory. The run log keeps what happened, not what was in the records.

§ 01 / Designer

Draw the flow. 42 step types.

Build integrations on a canvas instead of in code: read records, change and check them, decide, then write them somewhere else. Branches, rules, lookups, summaries and sub-flows are all boxes you can see.

Start by hand, on a schedule, by webhook or when rows change
Autosave, undo, tidy layout and YAML export
AI drafts a flow from a sentence; you review it

The SentraBridge designer with a payment file flow and the data inspector.

§ 02 / Data inspector

See the data before it's sent.

Like FME's inspector: record counts on every wire, and a click shows the records as a table, JSON, CSV or a field summary. Preview reads real records and never writes.

5, 25 or 100 records per source
Valid and Invalid outputs side by side
Download what you see as CSV

Wire: Clean and check → Email bad rows3 records

account	amount	paid_on	problem
40-118-22	86.40	2026-11-09	No account match
	112.00	2026-11-09	Account is required
40-771-05	-12.00	11/09/26	Amount must be positive

Table · JSON · CSV · Field summary | 5 · 25 · 100 records | Preview never writes

Illustration: counts on every wire; click a wire to see the records that crossed it.

§ 03 / Connectors

Pre-built where it matters. Any API where it doesn't.

Pre-built connectors know each system's records, fields, paging and sign-in. Plain APIs need an address and a key, and any OpenAPI or Swagger file becomes a connector.

43 pre-built connectors, 9 plain APIs
SQL Server, PostgreSQL/PostGIS and MySQL both ways
SFTP, SharePoint, S3 and Azure Blob for files

§ 04 / Operations

Know what ran. Fix what didn't.

Every run keeps counts, timings and record IDs, never contents. Failures email the people you choose; replay reads failed records again from the source. Trace any record across every flow it touched.