Skip to content
Bitween AI is on the way

Marketplace

Connectors and kits, installed from inside Bitween.

Packages reviewed and signed by Simplify9, listed on the Marketplace tab of every Bitween's Adapters page. Installing one checks both signatures; then it runs from your own Bitween, like any adapter you published.

Browse the catalogueHow installing works

15 packages, read from the registry every 60 minutes. What is here is what your Bitween's Marketplace tab offers.

Trust

Why what you install can be trusted.

A marketplace is a supply chain. Every version passes the same gates before it reaches your Bitween, and your Bitween checks it again.

Checked before it is listedEvery version carries its source. Each connector passes the Bitween adapter contract test before it is published, and its files are scanned for secrets and its dependencies for known vulnerabilities and denied licences.
Reviewed by Simplify9A person reads each version, with what changed since the one before marked, and only then is it signed and listed.
Signed twice, verified by your BitweenThe publisher signs the package and the registry countersigns it. Your Bitween checks both, and that the download is what was signed, before it installs anything. Every check fails closed.
Kept current, never changed for youOnce a day your Bitween asks about what it installed: newer versions with their release notes, and revoked ones, flagged on the Adapters page and on every subscription that runs them. Nothing is updated by itself.

Kits

A whole integration, not just a connector.

A kit installs its connectors at the versions it was written for, then the information types, partner, subscriptions, gateway and connection that make them do one job, named so it can be installed twice.

  1. 1Fill in the formThe kit asks for what only you know, such as your instance address and client id, with secrets as password fields and defaults filled in.
  2. 2See the plan firstShow plan says what it would make, changing nothing. Install makes it.
  3. 3Installed as youIt runs Bitween’s own planner with your session, so it can make only what you could, and every change is in the audit trail under your name.
  4. 4Approve access onceKits sign in to SaaS systems with a connection: someone approves access once, and Bitween keeps the token fresh.

More in Kits and Connections.

Under your control

Your Bitween stays yours.

Runs from your own storage

An installed connector is published into your Bitween like an uploaded package, and never needs the marketplace again.

Versions you choose

Install a version without making it current, pin subscriptions to one, and move them when you are ready.

Off when it must be

An administrator turns the marketplace off under Settings for a Bitween that must not reach the internet, or points it at another registry.

For developers

Build it, test it, publish it from CI.

Connectors are ordinary Bitween adapters, in .NET, Python, JavaScript or TypeScript. The bitween CLI builds one, runs the contract test, and signs and sends it for review. Today the marketplace carries packages Simplify9 publishes.

Build, test and publishbash
bitween adapter build connectors/acme.orders
bitween adapter test connectors/acme.orders/bin/serverless/acme.orders-1.0.0.zip
echo "$REGISTRY_TOKEN" | bitween registry login https://registry.bitween.io --key-file publisher.pem
bitween registry publish connectors/acme.orders/bin/serverless/acme.orders-1.0.0.zip

Need a connector that isn't here?

Simplify9 builds connectors and kits as part of its support packages, and publishes them to the marketplace for every Bitween. Tell us which systems you need to connect.

Talk to an integration architectBuilt-in adapters