Files from many partners
Local agencies and vendors send files in different formats on different schedules.
State programs exchange data with local agencies, vendors and the public. SentraBridge moves it through APIs, databases and SFTP files with every run logged, and keeps no copy of the records.
Local agencies and vendors send files in different formats on different schedules.
Datasets on the open-data portal are updated by hand, so they fall behind the source system.
Every system that keeps a copy of shared data has to be covered by the data-sharing agreement.
Upsert records into Socrata / Tyler Data & Insights datasets on a schedule, with public fields only.
Learn more →Rules and value maps clean and check partner data, and route bad rows to a person.
Learn more →Nothing is stored but settings, encrypted credentials and run metadata.
Learn more →CSP-hosted on US-based cloud infrastructure, or on agency servers, including air-gapped networks.
Learn more →Each workspace keeps its own connections, flows, code tables, people and history apart.
Learn more →Search a record ID and see every flow it went through.
Learn more →Generated from SentraBridge's ready-made templates.
Nightly, upserts changed OpenGov permit records into a Socrata / Tyler Data & Insights dataset.
SFTP server → PostgreSQL / PostGISEvery morning, reads new payment CSV files from the bank's SFTP folder, cleans and checks them, loads them into a database table, and archives the…
A reusable sub-flow: other flows hand it the records that failed their checks, and it emails the data team a summary with a CSV attached.
Each links to its connector page. Not listed? Any REST API, OpenAPI file, database or SFTP server works.
Yes. Workspaces keep connections, flows, code tables, people and history separate.
No. Records pass through in memory only. History keeps counts, timings and record IDs.
Yes, including networks without internet access.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.