pixlcore/xyops

The next generation of Cronicle: open-source job scheduling, visual workflows, server monitoring, alerting, and incident response.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 24 minutes ago
Added to GitGenius on September 10th, 2026
Created on December 29th, 2025
Open Issues & Pull Requests: 37 (+0)
GitHub issues: Enabled
Number of forks: 583
Total Stargazers: 6,185 (+0)
Total Subscribers: 37 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.2 hours
Mean response time: 28.8 hours
90th percentile: 12.6 hours
Tracked items: 325

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 11% of issues opened in the past year have been closed. Three people close 85% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

xyops is an open-source job scheduling and workflow orchestration platform that combines scheduled task execution with visual workflow design, server monitoring, alerting, and incident response capabilities.

The tool addresses the need for a unified system to manage recurring jobs, coordinate complex workflows, and respond to infrastructure events. It provides a visual interface for designing workflows alongside traditional cron-like job scheduling, allowing teams to define, monitor, and react to both planned tasks and unexpected system conditions in a single platform. The approach integrates job execution with observability and alerting, enabling users to see the full lifecycle of their automation from scheduling through completion and incident handling.

Teams should consider xyops if they need to move beyond basic cron jobs and want a centralized dashboard for workflow management and server health. It suits organizations that run multiple interdependent tasks and need visibility into their execution, as well as those seeking to automate incident response alongside routine operations. The tool is positioned as a successor to an earlier project, indicating it builds on established patterns while adding modern workflow visualization and monitoring capabilities.

The project shows active development with regular commits across multiple areas of the codebase. Work spans core scheduling logic, the visual workflow interface, monitoring and alerting systems, and infrastructure components. The maintainers respond to issues and pull requests, indicating ongoing engagement with user feedback. Development activity covers both feature additions and maintenance of existing systems, suggesting the project is being actively shaped rather than in maintenance mode.