SignalBus is a lightweight, local-first developer framework for structured signals and events. Connect processes, scripts, and applications on the same machine instantly without the overhead of HTTP APIs or message brokers.
Lightning-fast event routing for local processes with minimal latency and maximum efficiency.
Intuitive command-line tools for emitting, listening, and reacting to signals with minimal setup.
Subscribe using wildcards to handle dynamic or hierarchical topics like build.*, system.cpu.*, and more.
Fine-grained permissions with token management for secure multi-user environments and controlled access.
Query recent signals with timestamps, sender info, and payload metadata for debugging and monitoring.
Prevent signal spam with configurable per-topic or per-sender emission limits for system stability.
build.started → build.completed → deploy.triggered
user.created → email.welcome → analytics.track
system.cpu.high → alert.notify → scale.up
test.failed → slack.notify → retry.build
Connect TUI or CLI tools with real-time event triggers for rapid automation.
Secure service-to-service messaging with controlled permissions and isolation.
Get started with SignalBus via Cargo (P.S: Read the documentation for more details on all the SignalBus commands)
cargo install signalbus
Note: SignalBus currently keeps all signal data in memory and clears it when the daemon stops. Optional persistence across restarts will be added later, allowing data and configurations to be retained between daemon sessions if desired.