Redwood RunMyJobs is a proprietary platform, offered as managed SaaS or self-hosted, that automates enterprise workloads, especially SAP environments. Kestra gives any engineer the power to build, deploy, and monitor workflows in YAML through Git. No vendor lock-in, no per-job metering.
Declarative YAML workflows versioned in Git, executed in isolated containers, deployed through CI/CD. Any engineer can build and ship workflows without waiting on a vendor or central team. Open source at the core, with 2,600+ plugins and event-driven triggers built in from day one.
Proprietary platform, available as managed SaaS or self-hosted, focused on enterprise job scheduling and SAP workload automation. Jobs are defined through a GUI, executed by the RunMyJobs engine, and monitored from a centralized console. SAP-certified with deep integration into SAP ECC, S/4HANA, and BW environments.
Redwood RunMyJobs is a licensed platform that requires procurement, onboarding, and agent setup before you can define your first job. Kestra's single Docker Compose command stands up everything in a format that's already production-shaped.
curl -o docker-compose.yml \https://raw.githubusercontent.com/kestra-io/kestra/develop/docker-compose.ymldocker compose up
# Open localhost:8080# Pick a Blueprint, run it. Done.Download the Docker Compose file, spin it up, and you're ready (database and config included). Open the UI, pick a Blueprint, run it.
# 1. Negotiate contract and license terms# 2. Provision a RunMyJobs Cloud tenant or install self-hosted# 3. Install agents and Secure Gateway for on-premise systems# 4. Configure SAP RFC connections (if applicable)# 5. Set up user roles and security policies# 6. Define jobs through the RunMyJobs GUI# 7. Schedule and test job chainsOnboarding typically involves procurement, a license agreement, tenant provisioning (RunMyJobs Cloud) or a self-hosted installation, SAP system connectivity setup, and user training. Connecting on-premise systems requires installing Redwood's agents and Secure Gateway.
YAML is readable on day 1. Our docs are embedded in the UI for easy reference, the AI Copilot writes workflows for you, or start with our library of Blueprints. Engineers deploy through Git, same as application code.
Jobs are built mainly in the RunMyJobs web console. Definitions can be exported and promoted between environments, but as proprietary XML archives (CAR files) through Redwood's own promotion tooling, not as plain declarative files in your Git workflow. Job chains establish dependencies between steps. Process definitions include parameters, scheduling rules, and alerting configurations. Modifying job logic requires access to the RunMyJobs GUI and appropriate permissions.
Orchestrate data pipelines, infrastructure operations, business processes, and AI workflows from a single open-source platform. Event-driven at its core, with native triggers for S3, webhooks, Kafka, database changes, and API events. 2,600+ plugins.
Proprietary enterprise workload automation, offered as managed SaaS or self-hosted, with SAP-certified integration, finance close automation, and job scheduling. Subscription-based licensing and a GUI-driven approach to job definition and monitoring.
| Workflow definition | Declarative YAML | GUI-built process definitions (exported as proprietary XML) |
| Architecture | Event-driven at core | Schedule-driven |
| Deployment model | Single Docker Compose (self-hosted or Kestra Cloud) | Managed SaaS or self-hosted (proprietary license) |
| Licensing | Open source (Enterprise tier available) | Proprietary subscription (usage-based pricing) |
| Languages supported | Any (Python, SQL, R, Bash, Go, Node.js) | Scripts via job types (Python, shell, SQL) |
| SAP integration | SAP HANA via JDBC, SAP APIs via HTTP and scripts; existing RunMyJobs SAP jobs can be orchestrated from Kestra with the RunMyJobs plugin (Enterprise Edition) | SAP-certified native integration |
| Self-service for developers | Engineers build and deploy via Git | GUI access with role-based permissions |
| Self-service for non-engineers | Kestra Apps | Monitoring dashboards, not self-service triggers |
| Open-source option | Open source (Apache 2.0), Enterprise tier available | No open-source option |
| Finance close automation | Buildable with workflow orchestration | Purpose-built finance close module |
| Time to production | Minutes (Docker Compose) | Procurement, license agreement and agent setup |
Replacing our legacy scheduler with Kestra meant our engineers could finally own their workflows. We went from weeks of back-and-forth with a central team to self-service deployment through Git. The open-source model gave us full visibility into what we were running.
Redwood RunMyJobs is a proprietary platform. Your job definitions, execution history, and automation logic live inside their system. Kestra is open source. Workflows are YAML files in your Git repository. You own the code, the data, and the deployment. Run it on Docker, Kubernetes, or Kestra Cloud.
Kestra's open-source core is free with most of Kestra's 2,600+ plugins. Enterprise features (RBAC, SSO, audit logs) are available without per-job metering. Redwood's proprietary licensing uses subscription-based pricing with usage tiers that can scale costs unpredictably as job volumes grow.
Kestra was built event-driven from the start: webhooks, S3 uploads, Kafka messages, database changes, and API events are first-class YAML triggers. Unlimited event-driven workflows in open source. Redwood RunMyJobs is primarily a job scheduler. While it supports event-based triggers, the platform's core architecture is built around scheduled job execution.
Find answers to your questions right here, and don't hesitate to Contact Us if you couldn't find what you're looking for.
See how Kestra can simplify your workflows—and scale beyond legacy workload automation.