Platform overview
The integration platform you run, not rent.
One service hosts the REST API, partner gateways, background processing, the scheduler and the admin UI. Every message becomes an exchange that runs through the same stages, with the same evidence and the same controls.
Capabilities
Everything an integration needs between arrival and result.
The exchange pipeline
From arrival to result, step by step.
Click through the stages, or let the walkthrough play. The panel shows what Bitween records at each step.
Step 1 · Arrive
Many ways in, one pipeline.
A partner calls an API gateway, a message lands on a bus gateway, or a scheduled job pulls from S3, SFTP, a mailbox or a database. Every entry point leads into the same pipeline.
Read how it works{"id": "7f3a91c2e4b04d8f9a0c51d2b7e6f310","informationType": "Purchase order","partner": "Northwind Retail",············ ················· ········· ···························· ······························· ···································· ············· ···························· · ·········· ··········· ·········· ···· ················ ·························· · ········· ·········· ·········· · ·}
Concepts
Six words that explain Bitween.
The admin UI and the code sometimes name the same thing differently. Here are both.
Information type
DocumentOne kind of business document, such as a purchase order or a shipment update, with its format and promoted properties.
Partner
PartnerAn external party with API keys and properties that adapters reference as {{partner.KEY}}.
Subscription
SubscriptionA configured pipeline: what starts it, which adapters run, and where the response goes.
Exchange
XchangeOne message through one pipeline, with its input, output, response, references and result.
Work group
WorkGroupA processing lane with its own queues, prefetch and priority, so busy flows never block others.
Data source
DataSourceA long-lived connection to a customer’s broker or database, held open by a resident adapter.
Adapter runtimes
Every stage runs through one invoker.
Receivers, validators, mappers, handlers and notifiers can use any of three runtimes. Bitween picks the first that claims an adapter.
01
Native
Adapters compiled into Bitween and run in process: HTTP, SMTP, S3, Azure Blob, SFTP, POP3 and the mappers.
02
Resident
Long-lived adapter processes that keep a broker connection or database pool open between messages.
03
Classic
Custom adapters downloaded from storage and started as a new process for each call.
Put every integration on one governed pipeline.
Talk to the architects who build Bitween about your partners, systems and message volumes, or start from the docs and run it yourself today.