Start the CLI
Launch starbonding-cli.exe as a standard Windows child process. Pass credentials through stdin or use Credential Manager.
StarBonding CLI for OEMs, developers and integrators
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.
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
Your product. Your workflow.
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.
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
Launch starbonding-cli.exe as a standard Windows child process. Pass credentials through stdin or use Credential Manager.
Read complete stdout lines. Start your publisher only after the stable EVENT READY record.
Send H.264/AAC FLV to rtmp://127.0.0.1:1935/live/<stream-key>.
Monitor events, show your own UI, control your publisher and stop gracefully with --stop-event.
Works beside your existing stack
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.
For partners who manage customers
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 provisioninghttps://starbonding.com/api/v1/Get started
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
Yes. The CLI is intended to let OEMs, partners, developers and enthusiasts build their own Windows application around StarBonding’s bonded transport.
Yes. You may include the CLI with your application. Retain the executable filename starbonding-cli.exe.
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.
No. The CLI is a standalone native Windows executable with native RTMP ingest. It does not require SRS, FFmpeg or GStreamer.
Partners can use the Partner API to create and renew managed accounts, inspect balances and reconcile transactions.