What Is TickerQ Hub and Why You Need It
The problem with distributed schedulers
When you run background jobs across multiple servers, you lose visibility fast. Each node runs its own scheduler, executes its own functions, and logs to its own files. There's no single place to see what's running, what failed, or what's scheduled next.
Teams end up SSH-ing into servers, grepping logs, and hoping nothing critical was missed. As the number of nodes grows, this becomes unsustainable.
What TickerQ Hub does
TickerQ Hub is a control plane — not an executor. It doesn't run your jobs. Your schedulers continue running in your network, on your servers, with zero vendor lock-in. Hub provides the missing layer:
- Central visibility: See all schedulers, nodes, and functions in one dashboard
- Configuration management: Define function configurations once, deploy them everywhere
- Team collaboration: Role-based access so your whole team can monitor and manage schedulers
- Execution history: Full audit trail of what ran, when, and what happened
How it works
Your existing TickerQ schedulers connect to Hub via the TickerQ SDK. The SDK reports node status, function registrations, and execution results back to Hub. Hub aggregates this data and presents it through a clean web interface.
The key design principle: if Hub goes down, your jobs still run. The SDK is designed to be resilient — it caches configurations locally and operates independently when Hub is unreachable.
Getting started
1. Create a free account at hub.tickerq.net
2. Install the TickerQ SDK in your .NET application
3. Connect your schedulers by providing your Hub API key
4. Open the dashboard and see all your schedulers in one place
The free tier includes everything you need to get started — no credit card required.