xyOps

I built xyOps for people who still run real infrastructure and want their automation stack under their own control.

It started from a frustration: most workflow tools can run tasks, but they don’t give you much operational context when something goes wrong. Your scheduler knows the job failed. Your monitoring system knows the server was under load. Your ticketing system knows someone is upset. But the story is split across five tools.

xyOps brings those pieces together.

It’s an open-source, self-hosted platform for job scheduling, workflow automation, server monitoring, alerting, and incident response. You can schedule jobs across a fleet, build visual workflows, stream logs, collect metrics, fire alerts, capture server snapshots, and create tickets with useful context attached.

The core idea is that automation and monitoring should be part of the same feedback loop. When an alert fires, you should be able to see what was happening on the box. When a job fails, you should get logs, metrics, history, and next steps in one place.

xyOps is also deliberately open. The full app is available in the open-source version, with no hidden enterprise-only core features. The commercial model is paid support, not paywalled functionality.

I’m sharing it here because I’d love feedback from indie hackers, self-hosters, ops folks, and developers who automate real systems. If you’ve ever outgrown cron but didn’t want to hand your automation stack to a black box, xyOps might be for you.