discover · compare · collections · requirements · contribute · feed · watching · stats · help with your tokens
pixlcore/xyops · source
Snapshot 0 · 2026-11-04T12:47:28Z · JavaScript · BSD-3-Clause
Content fingerprint
11b00e80233c5bef83f585e792ca6f54e01ea4e2fa8104257684c4e8ee638a55GitHub description at capture
The next generation of Cronicle: open-source job scheduling, visual workflows, server monitoring, alerting, and incident response.
README at capture
# xyOps™
> Your job scheduler should know what your servers are doing.
**xyOps is the next generation of Cronicle:** a complete, self-hosted platform for job scheduling, visual workflow automation, server monitoring, alerting, and incident response.
<p align="center">
<strong><a href="https://xyops.io/">Website</a> | <a href="https://docs.xyops.io/hosting">Install</a> | <a href="https://docs.xyops.io/">Documentation</a> | <a href="https://github.com/pixlcore/xycli">CLI</a> | <a href="https://docs.xyops.io/cronicle">Cronicle Migration</a> | <a href="https://marketplace.xyops.io/">Plugin Marketplace</a> | <a href="https://docs.xyops.io/support">Support</a></strong>
</p>
[](https://xyops.io/)
<p align="center">
<a href="https://github.com/pixlcore/xyops/stargazers"><img src="https://img.shields.io/github/stars/pixlcore/xyops?style=flat&label=Stars" alt="GitHub stars"/></a>
<a href="https://github.com/pixlcore/xyops/forks"><img src="https://img.shields.io/github/forks/pixlcore/xyops?style=flat&label=Forks" alt="GitHub forks"/></a>
<a href="https://github.com/pixlcore/xyops/releases/latest"><img src="https://img.shields.io/github/v/release/pixlcore/xyops?label=Release" alt="Latest release"/></a>
<a href="LICENSE.md"><img src="https://img.shields.io/github/license/pixlcore/xyops?label=License" alt="License: BSD-3-Clause"/></a>
<a href="https://discord.gg/FTzqmbGbdd"><img src="https://img.shields.io/discord/713159081422225548?label=Discord&logo=discord&logoColor=white" alt="PixlCore Discord members online"/></a>
</p>
<p align="center">
<a href="https://trendshift.io/repositories/17651?utm_source=trendshift-badge&utm_medium=badge&utm_campaign=badge-trendshift-17651" target="_blank" rel="noopener noreferrer"><img src="https://trendshift.io/api/badge/trendshift/repositories/17651/daily?language=JavaScript" alt="xyOps: #1 JavaScript Repository of the Day on Trendshift" width="250" height="55"/></a>
</p>
## Overview
**xyOps is fully open source, self-hosted, with zero telemetry and no feature gates.**
xyOps connects the work you run with the systems it runs on. Schedule jobs across a fleet, build visual workflows, watch jobs and infrastructure together, capture the exact state of a server when an alert fires, and respond without reconstructing the incident across five different tools.
## Why xyOps
- **Schedule and run anything:** Launch scripts and plugins on one server, a server group, or your entire fleet. Use recurring schedules, cron expressions, intervals, webhooks, priorities, queues, and resource limits.
- **Orchestrate visually:** Build understandable workflows with branching, parallel execution, joins, human approval, reusable sub-workflows, replay, and data passing.
- **Observe the real system:** Monitor jobs and servers together with live dashboards, custom metrics, process inspection, network connections, and historical performance.
- **Respond with context:** Turn failures and alerts into actions. Capture server snapshots, open tickets, call webhooks, block unsafe launches, or start remediation automatically.
### From alert to root cause in two clicks
When an alert fires, xyOps can freeze the relevant server state at that moment: metrics, processes, network connections, active jobs, and alert data. Open the alert, then open its snapshot. The evidence is already waiting for you.
[See alert context in action](https://xyops.io/#alert-context)
## Cronicle evolved
xyOps is built by the creator of [Cronicle](https://github.com/jhuckaby/Cronicle) and carries its job-scheduling and plugin philosophy forward into a new architecture.
Existing Cronicle users can:
- Import Cronicle data through the xyOps interface.
- Keep compatible plugins and familiar scheduling concepts.
- Convert multiplexed events into visual workflows.
- Run jobs through lightweight xySat workers with no Node.js requirement.
- Enable Cronicle compatibility mode and optionally restore Cronicle branding.
[Read the Cronicle migration guide](https://docs.xyops.io/cronicle)
## Try xyOps in one command
If you have Docker, this starts a disposable xyOps conductor with a local worker so you can explore the complete product immediately:
```bash
docker run --detach --rm --init \
--name xyops-try \
--hostname xyops-try \
-e XYOPS_masters="xyops-try" \
-e XYOPS_xysat_local="true" \
-e XYOPS_base_app_url="http://localhost:5522" \
-e TZ="America/Los_Angeles" \
-p 5522:5522 \
ghcr.io/pixlcore/xyops:latest
```
Open [http://localhost:5522/](http://localhost:5522/) and sign in with:
- **Username:** `admin`
- **Password:** `admin`
This trial is intentionally disposable. Stop it with `docker stop xyops-try`, and Docker will remove the container and its data. Change `TZ` if you want the trial to use a different timezone.
For a persistent or production deployment, continue with the [Self-Hosting Guide](https://docs.xyops.io/hosting).
## xyOps from your terminal
Prefer working from the command line? [xyCLI](https://github.com/pixlcore/xycli) brings xyOps to your terminal with colorful dashboards, monitoring charts, and readable job reports.
Launch jobs and workflows, follow live output, investigate failures, inspect server health, and sync your automation definitions with local files you can version in Git.
[](https://github.com/pixlcore/xycli)
Install with npm:
```sh
npm install -g @pixlcore/xycli
```
[Get started with xyCLI](https://github.com/pixlcore/xycli#getting-started) | [Screenshot gallery](https://github.com/pixlcore/xycli/blob/main/docs/screenshots.md)
### Connect your AI assistant with MCP
xyCLI also includes a **Model Context Protocol (MCP) server** that lets compatible AI assistants work directly with xyOps. Inspect failed jobs, run existing workflows, search alerts, capture monitoring snapshots, and create tickets with the findings.
Connect over STDIO or HTTP, using your existing xyOps API key permissions and resource restrictions. An optional `--read-only` mode disables all mutation and execution tools. The `ghcr.io/pixlcore/xycli` Docker image includes Node.js and xyCLI, with the MCP HTTP server as its default startup command.
The [MCP Server extension](https://github.com/pixlcore/xyext-mcp) adds `/mcp` to your conductor's existing URL, with each client's xyOps API key passed through. It includes xyCLI as a dependency and works with both Docker and manual installations. See [Enabling the MCP server](docs/hosting.md#mcp-server).
[Explore the MCP tools and setup guide](https://github.com/pixlcore/xycli/blob/main/docs/mcp.md)
## Open source without feature gates
The complete xyOps application is available under the [BSD 3-Clause license](LICENSE.md). There is no separate commercial build and no vendor cloud control plane required to operate it.
Your jobs, logs, metrics, secrets, files, tickets, snapshots, and configuration remain inside your infrastructure. xyOps does not send product telemetry to PixlCore or to any other telemetry service.
Read more:
- [Trust and privacy posture](https://docs.xyops.io/trust)
- [Single Sign-On](https://docs.xyops.io/sso)
- [Security Overview](SECURITY_OVERVIEW.md)
- [Threat Model](THREAT_MODEL.md)
- [Longevity Pledge](LONGEVITY.md)
## Free software, optional paid support
The application is identical at every level. Paid plans fund development and provide a support relationship for teams relying on xyOps in production.
### Community
- Every application feature, including SSO
- BSD-licensed source code
- Community support through GitHub, Reddit, and Discord
If xyOps helps you, you can also [sponsor PixlCore on GitHub](https://github.com/sponsors/pixlcore).
### Professional
- Private support tickets
- One-business-day response target during business hours
- Deployment and upgrade guidance
- Prioritized product feedback
### Enterprise
- One-hour response target during business hours
- Direct access to Joe
- Architecture and migration guidance
- Hands-on SSO and air-gap assistance
- Invoice, wire, ACH, and purchase-order options
Again, **SSO and air-gapped operation are included in the free open-source application**. Enterprise support adds hands-on help configuring and validating those features.
[See transparent Professional and Enterprise pricing](https://xyops.io/#pricing)
## Documentation and videos
- [Official documentation](https://docs.xyops.io/)
- [Self-hosting and installation](https://docs.xyops.io/hosting)
- [Plugin Marketplace](https://marketplace.xyops.io/)
- [YouTube tutorials](https://www.youtube.com/@PixlCore-Media)
Full documentation is also included inside xyOps. Click **Documentation** in the application sidebar.
Watch a quick overview of xyOps:
[](https://www.youtube.com/watch?v=NxZKylkKfOg)
## Follow xyOps
We're sharing short videos with xyOps tips, tricks, and ideas for your own automation. Longer tutorials and walkthroughs are coming to YouTube soon!
Follow PixlCore on your favorite platforms, or join the xyOps community on Reddit. If you find a video helpful, a like, subscription, or share is a great way to support the project and help others discover xyOps.
- [Mastodon](https://mastodon.social/@pixlcore)
- [Bluesky](https://bsky.app/profile/pixlcore.bsky.social)
- [X / Twitter](https://x.com/PixlCoreCom)
- [YouTube](https://www.youtube.com/@PixlCore-Media)
- [TikTok](https://www.tiktok.com/@pixlcoremedia)
- [Instagram](https://www.instagram.com/pixlcoremedia/)
- [Reddit](https://sh.reddit.com/r/xyOps)
## Community and support
- [GitHub Discussions](https://github.com/pixlcore/xyops/discussions) for questions and community help
- [GitHub Issues](https://github.com/pixlcore/xyops/issues) for reproducible bugs and feature requests
- [Discord](https://discord.gg/FTzqmbGbdd)
- [LinkedIn](https://linkedin.com/company/pixlcore)
## Contributing
Please read the [Contributing Guide](CONTRIBUTING.md) before opening a pull request.
The short version: we do not accept feature pull requests, but there are many other useful ways to contribute. The guide explains where community help is most valuable.
## Development
See the [Development Guide](https://docs.xyops.io/dev) for complete local setup instructions. In short, install [Node.js LTS](https://nodejs.org/en/download), then run:
```bash
git clone https://github.com/pixlcore/xyops.git
cd xyops
npm install
node bin/build.js dev
echo '{ "secret_key": "test" }' > conf/overrides.json
bin/debug.sh
```
## Security
Read the [Trust Guide](https://docs.xyops.io/trust) for xyOps self-hosting, privacy, telemetry, outbound requests, and enterprise security posture.
Read the [Security Guide](https://docs.xyops.io/security) to report a security vulnerability privately. Please do not submit vulnerabilities as public GitHub issues.
## Governance and longevity
The xyOps project exists to empower users and developers through openness, reliability, and fairness.
- The [Governance Model](https://docs.xyops.io/governance) is designed to preserve these principles.
- The [Longevity Pledge](LONGEVITY.md) commits xyOps to remaining open-licensed and OSI-approved. No rug pulls.
## License
xyOps™ is licensed under the [BSD 3-Clause License](LICENSE.md).
See [TRADEMARKS.md](TRADEMARKS.md) for trademark usage guidelines.