Public sector
Government bodies share data across agencies, vendors and citizen portals under strict sovereignty and procurement rules. Bitween is open source, self-hosted and transparent about how it works.
The challenge
01
Data must stay in national or agency-controlled infrastructure, with no dependency on a vendor's cloud.
02
Proprietary integration platforms tie critical services to one vendor's licensing and roadmap.
03
Each agency needs its own access, credentials and pipelines, governed consistently.
Flows you can run today
Each flow below uses capabilities that exist in Bitween now, with links into the documentation that describes them.
Flow 1
Each agency is a partner with its own API keys and properties. Agencies call shared API gateways, and each agency's key selects its own pipeline, so one endpoint serves many agencies with different rules.
Flow 2
Applications submitted through a portal are validated synchronously, stored with their full input, mapped and written to the case management system, with the exchange id returned to the portal for tracking.
Flow 3
Replace unmaintained scripts one flow at a time: Bitween reads the same files and tables, while the Flow map documents what connects to what.
Controls that matter here
Good to know about formats and scope
National e-government standards and e-invoicing formats are not shipped as ready-made packs. They can be implemented with HTTP adapters, the XML mapper and custom adapters.
Related use cases
One HTTPS endpoint per business process: sync when partners need an answer, async when they need speed.
Onboard partners with their own keys, properties and pipelines: configuration, not code.
Poll named SQL statements into exchanges and write deliveries back to tables and procedures.
Share your partners, systems and volumes. We'll show you how the flows would run on Bitween in your own environment.