Managing scheduled jobs across internal servers doesn’t have to mean deploying heavy automation platforms. Many OpsBay users simply want Cronicle (or OpsBay Jobs) to trigger commands inside their own environment—securely and without exposing machines.

To solve this, we built opsbay-cron-broker, a tiny distributed job broker that lets OpsBay users run commands on their internal nodes using a lightweight server + worker model.

GitHub: https://github.com/itefixnet/opsbay-cron-broker

What it is

opsbay-cron-broker consists of:

• a central broker server

• workers running on your internal machines

• opsbay-job-broker.sh, a simple client for submitting jobs

Workers poll the server, execute assigned jobs, and push results back.
No inbound ports or complex setup needed.

Why use it?

• Secure — HMAC SHA-256 authentication + node whitelisting

• Lightweight — server and workers in Bash

• No agents or frameworks — perfect for small/solo setups

• OpsBay-ready — built to integrate with Cronicle and OpsBay’s job UI

• Fully internal — OpsBay triggers jobs, but execution stays inside your network

Quick workflow

1. Start the broker server

Configure .env:

Run the server.

2. Start workers on your internal nodes

3. Submit a job using opsbay-job-broker.sh

Results are returned directly in your terminal or in OpsBay.

Perfect for

• running backups, cleanup tasks, or checks on internal nodes

• triggering internal CI/CD steps

• lightweight ETL or scripts spread across multiple servers

• giving OpsBay the ability to run jobs inside restricted networks

Conclusion

opsbay-cron-broker gives OpsBay users exactly what they need:
a simple, secure way to run jobs on internal servers without heavy tooling.

Check out the project here:
https://github.com/itefixnet/opsbay-cron-broker