Architecture
How govtender actually works
An engineering-level tour of the pipeline: where data comes from, how it becomes a trustworthy canonical record, how the API and dashboards read it, and how it gets deployed and refreshed. Every diagram below is drawn from the real code, not the marketing summary.
[ ] a table, store, or persisted artifact
{ } a decision point
→ data flows this way
- - → deferred, optional, or scheduled separately