Sources
Bring representative data
Upload files or connect supported sources. Parse checks keep malformed inputs out, while normalized headers reveal every distinct layout.
Product
One approved contract across every company and source.
Convergent turns differently shaped operational files into a stable, versioned dataset. Source teams keep their existing exports while downstream teams integrate once.
Workflow
From representative files to a dependable output.
The source can change shape. The contract downstream teams depend on should not.
Contract
Define the dependable shape
Set the fields, types, validation rules, and grain the downstream consumer needs, then map each source into that contract.
Approval
Review every layout
Preview a representative file from each distinct shape. Nothing is approved until the full source reality has been sampled.
Delivery
Serve one stable result
Run the approved specification, inspect failures, and expose ordered records through REST, CSV, JSON, or MCP.
Files and exports→Approved contract→Reliable interfaces
Recurring data
Updates behave the way the source intends.
Every feed has an explicit write mode. That makes recurring corrections, new records, and full snapshots predictable instead of relying on filename conventions or hidden merge logic.
Correction
Incoming rows replace records with the same grain key. Use this when later files correct prior values.
Append
Existing records stay unchanged and only unseen keys are added. Use this for immutable event-like feeds.
Snapshot
Rows are upserted, then records missing from that same source are removed. Use this when each file represents current state.
Operational controls
Keep unexpected inputs away from trusted outputs.
✓
Malformed uploads remain visible in the file library but do not enter ingestion.
✓
Only approved specifications can be served to downstream consumers.
✓
Invalid records are quarantined for inspection instead of silently disappearing.
✓
Run history shows what processed, what failed, and the resulting row count.
✓
Live API keys are revocable and can be restricted to a single dataset.
Start with one contract
Bring three messy files and one useful downstream question.
A focused pilot should prove that Convergent can absorb source differences, maintain an approved dataset, and deliver it in the form your team already consumes.