StarBonding CLI for OEMs, developers and integrators

Build your own.
Bond every connection.

StarBonding CLI brings native Windows RTMP ingest, authentication, Zentun framing and multi-network bonding to your own application. Launch one executable, send it a standard RTMP stream, and keep ownership of your product experience.

Open integration spirit: anyone may use starbonding-cli.exe to develop their own bonding application or include it with their Windows application.

StarBonding CLI
your-app.exe
    │ local RTMP
    ▼
starbonding-cli.exe
    │ bonded Zentun transport
    ├──── Ethernet
    ├──── Wi-Fi
    ├──── 4G / 5G modem
    └──── Phone tethering
    │
    ▼
Your live destinations

EVENT READY url=rtmp://127.0.0.1:1935/live/your-stream

Native WindowsOne standalone CLI
Standard RTMPWorks with your pipeline
No SDK dependencyNo FFmpeg or GStreamer
Your applicationYour branding and workflow
Partner APIProvision and renew accounts

Your product. Your workflow.

Bonding capability without turning your product into someone else’s product.

Use StarBonding CLI as the reliable transport layer beneath your own Windows application. Your application can decide how streams are created, which inputs are accepted, what the user sees, how workflows are automated and how your product is branded.

The CLI remains deliberately simple: it listens for a local RTMP publisher, performs authenticated bonding across available network adapters and reports stable process events for your host application.

Use it freely in the application you want to build.

Develop a new live-streaming product. Add bonding to an existing encoder, sports graphics system, camera workflow, playout application or managed streaming service. Bundle starbonding-cli.exe with your Windows application. Build the interface and experience that make sense for your users.

A small integration surface

Your application controls the experience. The CLI handles the bonded path.

01

Start the CLI

Launch starbonding-cli.exe as a standard Windows child process. Pass credentials through stdin or use Credential Manager.

02

Wait for readiness

Read complete stdout lines. Start your publisher only after the stable EVENT READY record.

03

Publish local RTMP

Send H.264/AAC FLV to rtmp://127.0.0.1:1935/live/<stream-key>.

04

Own the workflow

Monitor events, show your own UI, control your publisher and stop gracefully with --stop-event.

Works beside your existing stack

Standard RTMP in. Bonded live delivery out.

There is no need to link against a DLL, ship FFmpeg, configure GStreamer or operate a separate RTMP server. Your application only needs to publish a normal RTMP stream locally.

  • Native RTMP ingest on Windows
  • Ethernet, Wi-Fi, 4G/5G modems and tethered phones
  • Stable stdout events and predictable exit codes
  • Automatic publisher reconnect handling
  • Server-side restream management through the CLI
Your Windows application
RTMP
starbonding-cli.exe
LANWi-Fi5GPhone
Bonded transport
Your configured destinations

For partners who manage customers

Provision accounts from your own systems.

Use the Partner API to list services, create managed accounts, renew them, view customer accounts and reconcile wallet transactions. Combine account provisioning with the CLI and you have an end-to-end product integration path.

Read Partner API documentation →

Partner API

Account provisioning
Wallet visibility
Renewal workflow
https://starbonding.com/api/v1/

Get started

Start with the official StarBonding package.

Download and install the official Windows package. The CLI is normally installed at:

C:\Program Files\StarBonding\starbonding-cli.exe

Your application may launch and include the CLI. Keep its filename as starbonding-cli.exe; the executable validates that filename at startup.

Installer SHA-256: 5F4A14457B6A429930EA235E0D22BEA8E3C34BBD7DBB8173D162C37FDA2D0233

Questions, answered

Built for builders.

Can I build my own bonding application using StarBonding CLI?

Yes. The CLI is intended to let OEMs, partners, developers and enthusiasts build their own Windows application around StarBonding’s bonded transport.

Can I include starbonding-cli.exe with my application?

Yes. You may include the CLI with your application. Retain the executable filename starbonding-cli.exe.

Do I need to use the StarBonding GUI?

No. The GUI and its image asset are not runtime dependencies of the CLI. Your product can launch the CLI directly and provide its own interface.

Do I need an SDK or external media runtime?

No. The CLI is a standalone native Windows executable with native RTMP ingest. It does not require SRS, FFmpeg or GStreamer.

Can I provision accounts for my own customers?

Partners can use the Partner API to create and renew managed accounts, inspect balances and reconcile transactions.