Platform · Connectivity
Every way in and out, on one pipeline.
API gateways for partners, bus gateways for events, scheduled jobs for pulls and adapters for delivery, each one feeding the same stages, the same record and the same controls.
API gateways
Sync and async HTTPS endpoints. Each attached partner is paired with the pipeline that runs when it calls.
Bus gateways
Consume from the internal RabbitMQ bus or a customer’s RabbitMQ or Amazon SQS queue, and route by content.
Scheduled jobs
Receivers pull from HTTP, S3, Azure Blob, SFTP, POP3 and databases on UTC schedules, or on demand.
Aggregations
Roll finished exchanges of one subscription into a single exchange for batch delivery.
Data sources
Long-lived broker and database connections run by a supervisor, with leases, health and resource ceilings.
Custom adapters
Anything else becomes a custom adapter that Bitween runs per call or keeps resident.
API gateways
Partner endpoints in minutes.
Create a gateway, attach partners and pick the pipeline each one runs. Partners call one URL with their key; Bitween does the rest.
- Copy sync and async URLs
- Different pipelines per partner behind one URL
- Deactivate without deleting, and only attached partners are told
Bus gateways
Content-based routing on a canvas.
Each route has a match expression, an optional partner and a subscription. The canvas shows every route’s stages and where its response lands on the bus.
- Match with one_of, not_one_of, and, or
- Read the internal bus or a customer queue
- Edit routes, filters and partners together
Data sources
Connections that stay open and stay healthy.
A supervisor on each enabled node reconciles every 30 seconds: it takes leases, starts and restarts adapters, and writes their health back. A crashed owner’s lease is released straight away and another node takes over on its next reconcile.
| Placement | Behaviour | Default for |
|---|---|---|
| Exclusive | Exactly one node runs the adapter at a time, fenced by a lease counter | Brokers |
| PerNode | Every enabled node runs its own instance and pool | Databases |
| Auto | Exclusive for brokers, PerNode for everything else | Neither |
Scheduled jobs
Pulls on a schedule, with health built in.
Every run records what the receiver found (data with the exchanges it created, nothing new, or a failure), and items are only removed at the source after their exchange exists.
- Last run, reliability and next run at a glance
- Stuck and unscheduled jobs flagged
- Receive now without changing the schedule
Documentation
Written from the source code.
Every claim on this page links to documentation that is synced from the Bitween repository.
Explore the platform
More capabilities.
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.