Skip to content
Bitween AI is on the way
v10Open source · self-hosted · Kubernetes-ready

Every partner, system and message on one governed pipeline.

Bitween is the self-hosted integration platform for teams that can't afford to lose a message. Receive from APIs, brokers, databases and files; validate, map and deliver; and keep a searchable, replayable record of every exchange, inside your own infrastructure.

  • MIT licensed, every feature included
  • Your data never leaves your network
  • Docker image and Helm chart
  • Audit trail for every change

Speaks the protocols your business already runs on

  • REST & HTTP
  • OAuth2
  • RabbitMQ
  • Amazon SQS
  • PostgreSQL
  • SQL Server
  • MySQL
  • Oracle Database
  • Amazon S3
  • Azure Blob Storage
  • SFTP & FTP
  • POP3 mailboxes
  • SMTP
  • JSON
  • XML
  • Kubernetes & Helm
  • Docker
  • Microsoft Entra ID
  • Elasticsearch

Product tour

Built for the people who keep integrations running.

Operators, integration developers and support teams share one browser-based workspace, with permissions that show each person exactly what they need.

Dashboard

Know what needs attention before anyone asks.

  • Failures still to act on
  • Retry chains that keep failing
  • Unhealthy and busiest subscriptions

Real screenshots of Bitween with a demo workspace.

bitween.yourcompany.com/dashboard
Bitween dashboard with today's exchanges, the 7-day success rate, failures to act on and the busiest subscriptions

How it works

Follow one message through Bitween.

Every exchange, whether it comes from a partner API call, a queue or a scheduled pull, runs through the same stages and leaves the same evidence behind.

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
exchange 7f3a91c2 · what Bitween records
{
"id": "7f3a91c2e4b04d8f9a0c51d2b7e6f310",
"informationType": "Purchase order",
"partner": "Northwind Retail",
············ ·········
········ ·
········ ···················
········· ····················
··········· ·····················
··
············· ············· ·················
··········· · ·········· ··········· ·········· ···· ··
·············· ·················
········· · ········· ·········· ·········· · ·
}

Visual mapping

JSON in, XML out. No document ever sent with gaps.

Build rules from real samples: paths, fixed values, partner and global values, transforms, lookups and list filters. Every rule is attempted, and if one fails the exchange fails with the reason.

  • Decimal-exact numbers: 100 × 1.16 is exactly 116
  • Ambiguous dates refused, never guessed
  • XML namespaces, attributes and repeated elements
  • Server-side preview through the pipeline’s own code
Subscriptions / Northwind → ERP / Transformation

Source · JSON sample

{
"order": {
"id": "SO-10482",
"customer": "Northwind Retail",
"status": "S",
"date": "12/09/2026",
"lines": [
{ "sku": "NW-2201", "qty": 12 },
{ "sku": "NW-3150", "qty": 0 }
]
}
}

Rules

Output · XML preview

<PurchaseOrder>
<Reference>SO-10482</Reference>
<Customer>NORTHWIND RETAIL</Customer>
<Account>NW-4471</Account>
<Status>Shipped</Status>
<OrderedOn>2026-09-12</OrderedOn>
<Item>
<Sku>NW-2201</Sku>
<Quantity>12</Quantity>
</Item>
</PurchaseOrder>

Reliability

Retry what's safe. Block what isn't. Alert once.

Retry policies decide per failure: transient network errors wait and try again within a budget, validation errors never repeat, and when a shared budget runs out one alert reaches the right team.

Fixed

delayMs

Linear

+ incrementMs

Exponential

× multiplier, capped

Retry chain

PO-10482 → ERP orders API

correlation c1d0…
  1. Attempt 1

    09:14:02

    HttpRequestException · 503 Service Unavailable

  2. Waiting 30 s

    Group "Transient network errors" · exponential

  3. Attempt 2

    09:14:32

    HttpRequestException · 503 Service Unavailable

  4. Waiting 60 s

    Budget: 2 of 5 for this message

  5. Attempt 3

    09:15:32

    200 OK · response stored · budget released

Shared budget

Transient network errors

138 / 500

per message cap 5

When a shared total runs out, retries stop for the whole group and one alert goes to the handler you chose.

400 Bad Request → blocked

Group “Validation errors” never retries bad data.

Notifier → integrations team

Email via SMTP, or an HTTP call to your incident tool.

Deployment & trust

Your infrastructure. Your compliance scope.

Bitween runs where your data already lives. No vendor cloud in the path, no per-message metering, and nothing to phone home to.

  • Scale out with replicas

    Add replicas behind a load balancer and tune prefetch per work group.

  • Choose your stack

    PostgreSQL, SQL Server or MySQL; S3, Azure Blob or Oracle Cloud storage.

  • Enterprise sign-in

    Microsoft Entra ID sign-in and Azure managed identity for databases.

YOUR CLOUD · YOUR DATA CENTREPartners · systems · operators (HTTPS)Ingress or Gateway APITLS · routes /, /api, /swaggerKUBERNETES · HELM CHART · SCALE BY REPLICASBitween replicaAdmin UI · REST API · GatewaysExchange workersSchedulerData source adaptersBitween replicaAdmin UI · REST API · GatewaysExchange workersSchedulerData source adaptersBitween replicaAdmin UI · REST API · GatewaysExchange workersSchedulerData source adaptersBitween databasePostgreSQL · SQL Server · MySQLRabbitMQWork lanes · retries · eventsObject storageS3 · Azure Blob · Oracle CloudConfiguration, exchanges and the audit trail stay in your database. Payloads stay in your storage.Customer brokersRabbitMQ · Amazon SQSCustomer databasesPostgres · MySQL · SQL Server · OraclePartner endpointsHTTP · SFTP · S3 · SMTPIdentity & logsEntra ID · Elasticsearch
In development

Bitween AI is coming, with the guardrails integration already has.

AI that drafts, explains and acts should be permissioned, previewed and audited like everything else in your integration layer. That's what we're building.

Coming

AI-assisted mapping

Draft mapping rules from a source and target sample, then review them in the live preview.

Coming

Failure explanations

Plain-language summaries of why a retry chain keeps failing, and what to change.

Coming

MCP server for agents

Let AI agents work with Bitween through tools that respect roles and land in the audit trail.

Coming

Ask your exchanges

“Failed shipment updates for Contoso this week” becomes a filter you can share.

MIT

Open-source license

Every feature, unlimited integrations and users.

13

Native adapters

HTTP, SMTP, S3, Azure Blob, SFTP, POP3 and mappers.

6

Broker & database providers

RabbitMQ, SQS, PostgreSQL, MySQL, SQL Server, Oracle.

61

Fine-grained permissions

Custom roles, Microsoft sign-in, full audit trail.

FAQ

Questions architects ask us.

Can't find your answer? The documentation is written straight from the source code, or ask an architect directly.

Is Bitween really free?

Yes. Bitween is open source under the MIT License, with every feature, unlimited integrations, partners and users. Simplify9 offers optional support packages and integration services for teams that want expert help.

Where does my data live?

In your infrastructure. Bitween runs as a container in your cloud account or data centre, stores configuration, exchanges and the audit trail in your database, and writes payloads to your object storage. No Simplify9-operated service sits in the data path.

What do I need to run it?

A container runtime or Kubernetes, a PostgreSQL, SQL Server or MySQL 8 database, RabbitMQ, and S3-compatible, Azure Blob or Oracle Cloud object storage. A Helm chart and a Docker image are provided.

Can we build our own connectors?

Yes. A custom adapter is a small program that implements a simple contract for receiving, validating, mapping or delivering. Bitween runs it out of process, either per call or as a long-lived resident process that keeps connections open.

What happens when a partner endpoint is down?

The exchange fails with its reason and your retry policy decides: which errors are retried, how long to wait, how many attempts per message and how many in total. When a shared budget is spent, retries stop and one alert is sent. Every attempt is kept in a retry chain you can follow and retry by hand.

Does Bitween handle EDI or HL7?

Bitween maps JSON and XML natively, in either direction, including XML namespaces. Flat and delimited formats such as X12, EDIFACT or HL7 v2 are handled by a custom adapter that translates them before or after mapping.

How does Bitween compare with MuleSoft or Boomi?

Those are broad, cloud-first platforms with large connector catalogues and matching price tags. Bitween is focused on reliable message exchange with partners, brokers, databases and files, runs entirely in your environment, and costs nothing to license. Our comparison page walks through the differences.

When is Bitween AI available?

Bitween AI is in development. We share progress with early-access teams first. Tell us about your use case and we will keep you in the loop.

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.