Backed by 8,700+ GitHub stars and designed as a modern alternative to Apache Airflow, Mage delivers the open-source data pipeline platform that combines the interactive flexibility of notebooks with production-grade orchestration in a single self-hosted environment accessible at port 6789. The modular block architecture lets data engineers compose pipelines from Python, SQL, and R code blocks with instant data previews, live execution logs, and visual debugging at each step. Over 100 prebuilt integrations connect sources and destinations including PostgreSQL, MySQL, Snowflake, BigQuery, Redshift, S3, Kafka, MongoDB, Amplitude, Salesforce, and Stripe with parallel stream synchronization for high-throughput data movement. Batch pipelines run on cron schedules or event triggers while streaming pipelines process real-time data from Kafka, Kinesis, and RabbitMQ with stream mode reducing memory usage by approximately 90 percent compared to batch processing. Native dbt integration builds, tests, and runs dbt models directly inside the pipeline editor alongside custom transformation blocks. Spark, Snowpark, and Databricks runtimes handle large-scale distributed processing. AI-assisted development generates code, fixes errors, and optimizes queries within the notebook interface. Monitoring dashboards track pipeline health with integrations to Datadog, Prometheus, New Relic, and OpenTelemetry. Terraform templates deploy production environments to AWS, GCP, or Azure with two commands, while Helm charts support Kubernetes clusters. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

Originally built at Netflix to orchestrate microservices powering 230 million subscribers and now trusted in production at Tesla, LinkedIn, and J.P. Morgan, Conductor is the most battle-tested open-source workflow engine available — with 32,000 GitHub stars and horizontal scalability to billions of executions. The architecture cleanly separates orchestration from business logic: workflows are defined in declarative JSON while workers execute tasks in any of seven supported languages (Java, Python, Go, JavaScript, C#, Ruby, Rust) with zero framework constraints. Durable execution persists every state transition, enabling automatic retries, configurable timeouts, crash recovery, and instant replay from any failure point without re-executing completed tasks. Native AI agent orchestration supports 14+ LLM providers (Anthropic, OpenAI, Google Gemini, AWS Bedrock, Mistral, Cohere, HuggingFace, Ollama), MCP tool calling, function calling, human-in-the-loop approval gates, and vector database integration (Pinecone, pgvector, MongoDB Atlas) for RAG pipelines. Deploy with your choice of five persistence backends (PostgreSQL, Redis, MySQL, Cassandra, SQLite), six message brokers, and Elasticsearch or OpenSearch for workflow indexing — all configurable via Docker Compose files included in the repository. The built-in web UI provides workflow visualization, execution monitoring, task queue inspection, and manual intervention controls. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

MateClaw delivers a multi-agent AI platform where digital employees run as persistent team members with roles, goals, and accumulated skills rather than stateless chat completions. The Spring Boot backend on Spring AI Alibaba provides ReAct iterative reasoning and Plan-and-Execute decomposition on a StateGraph runtime, with parallel delegation between employees and dynamic context pruning for multi-step tasks. Five career templates ship ready (Product Researcher, Customer Support, Knowledge Curator, Data Analyst, Executive Assistant) while custom employees inherit configurable backstories, pixel-art avatars, and dedicated tool bindings. The MCP integration supports stdio, SSE, and Streamable HTTP transports with per-employee tool isolation preventing capability bleed between agents. ACP bridges bring Claude Code, Codex, and other coding agents in as first-class employees. Workflow orchestration composes multiple employees and system actions into publishable linear DSL processes with seven step modes: sequential, fan_out, collect, conditional, await_approval, dispatch_channel, and write_memory. The trigger system wires cron schedules, webhooks, channel messages, employee lifecycle events, content matches, and workflow completions to automated flows. The Admin Runtime Console provides real-time visibility into running employees with token usage tracking and one-click force-recycle. Spring Boot Actuator monitoring, full audit trail, and per-channel error isolation deliver production-grade reliability. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

AWX transforms Ansible from a command-line tool into a centralized automation hub with a web UI, REST API, and distributed task engine for managing playbooks, inventories, and credentials at enterprise scale. The React-based dashboard provides real-time visibility into job status, inventory health, and execution history while Django REST Framework powers programmatic control over every automation resource. Job templates combine Ansible playbooks, inventories, and credentials into reusable units that chain together in workflow templates using directed acyclic graph orchestration with conditional branching on success, failure, or always-run logic and configurable convergence gates. The RBAC system built on django-ansible-base provides granular permission control over organizations, teams, projects, inventories, and credentials at object-level granularity. Dynamic inventory sources pull host data from AWS EC2, Google Cloud, Microsoft Azure, VMware vCenter, and Red Hat Satellite, while credential management securely stores SSH keys, cloud tokens, and vault passwords with HashiCorp Vault and CyberArk integration for external secret retrieval. Notifications deliver alerts via Slack, email, PagerDuty, Mattermost, IRC, and webhooks, while activity streams log every action for compliance auditing. The Receptor mesh network distributes job execution across isolated container-based execution environments with capacity-aware scheduling and hop-node routing for network-segmented infrastructures. Upstream of Red Hat Ansible Automation Platform. Deploys via Docker Compose with PostgreSQL and Redis or via the AWX Operator on Kubernetes. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

T3 Code puts every coding agent you already pay for behind one control surface, so Claude Code, Codex, Cursor, Grok Build, OpenCode, and Antigravity all run on your server while you direct them from your phone, browser, or desktop. Start a thread, choose the provider and model that fit the job, and watch the agent work in a shared conversation instead of a terminal you have to babysit. Permission modes decide when an agent must stop and ask, and its approvals, questions, and plan reviews arrive in the same thread wherever you happen to be connected from. When the work lands, review it file by file in the built-in diff view, then commit, push, and open pull requests through the Git and GitHub integrations without leaving the app. A real terminal sits beside the chat, and projects, settings, and scheduled tasks stay attached to the machine where the code actually runs. Install it as a background service and reach it from anywhere through T3 Connect, a Tailscale or LAN pairing, or the hosted web client, with a pairing code guarding local access. Outside agents can also drive threads over MCP, launching, messaging, and waiting on work across machines you have linked together. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

With 23,600 GitHub stars, 13 million monthly PyPI downloads, and 425+ contributors automating over 200 million data tasks monthly for Fortune 50 companies like Progressive Insurance and disruptors like Cash App, Prefect is the most widely deployed open-source workflow orchestration framework for Python — turning any script into a resilient production pipeline with a single @flow decorator while eliminating rigid DAG structures entirely. The durable execution engine persists task results and automatically resumes from failures without replaying expensive upstream work, guaranteeing exactly-once execution for any Python function. Event-driven automation triggers workflows from webhooks, cloud events, or state changes through a real-time event bus that detects what happens or fails to happen across your entire data platform. Work pools decouple workflow code from infrastructure, enabling seamless switching between Docker, Kubernetes, AWS ECS, Azure Container Instances, GCP Cloud Run, and serverless environments without modifying pipeline logic. Native Ray and Dask task runners extend execution across clusters for compute-intensive workloads. The self-hosted server provides a monitoring dashboard with flow run timelines, task state visualization, scheduling, and automation configuration. The third-generation engine reduces overhead by over 90 percent compared to Prefect 2, supporting batch, event-driven, interactive, and background task workflows. Deploy via Docker Compose with PostgreSQL, Redis, server, background services, and worker containers, or use official Helm charts for production Kubernetes. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Flowctl turns repetitive ops work, such as granting SSH access, restarting a service, or provisioning a server, into self-service forms that anyone on the team can run without holding credentials. Each workflow is a YAML or HUML file with typed inputs, validation rules, and a list of actions. Actions run in order or as a dependency graph, so independent branches execute in parallel. Every action runs in a Docker container, as a shell script, or as another flow, and scripts can target remote servers over SSH, several at once. Sensitive steps pause until a reviewer approves or rejects them. Output from one action feeds the next, files pass along as artifacts, and failed actions can be retried. Cron schedules with time zones and labels run flows unattended, while logs stream live in the browser. Email, Slack, Mattermost, and webhook notifications announce success, failure, waiting, or cancellation. Teams get isolated namespaces with user, operator, reviewer, and admin roles, OIDC single sign-on, and encrypted storage for SSH keys and secrets. A built-in flow editor means nobody has to hand-write files, and custom executors can be added as Go plugins. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

GoCD treats delivery as a pipeline you can see: every commit enters a sequence of stages, passes or fails in the open, and travels from first build to production deployment along one visible, traceable path. Stages split work into jobs that run in parallel on a fleet of agents, so unit tests, integration suites, packaging, and security scans finish together instead of queueing behind each other. Pipelines connect with fan-in and fan-out dependencies, meaning a release pipeline waits for every upstream component to pass before it assembles them, and one library build can feed a dozen services. The value stream map draws that whole web on one screen, from the triggering commit through every stage to deployment, and any run can be compared with another to spot exactly what changed. Materials watch Git, Subversion, or Mercurial repositories and start pipelines on new commits, while artifacts produced by one stage are fetched, versioned, and promoted by the stages after it. Environments group pipelines and agents so test and production stay isolated, resources tag agents by capability, and elastic agents appear on Docker, Kubernetes, or cloud hosts only while work exists. Pipeline definitions can live in YAML or JSON inside a repository, changing through code review like the software they deliver, and templates keep repeated release patterns consistent across teams. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Recognized by the CNCF Landscape in the AI Agent – Workflow Orchestration category alongside Dify and Temporal, Astron Agent is iFLYTEK's fully open-source platform for building, deploying, and managing enterprise multi-agent systems — backed by 8,900+ GitHub stars and the production infrastructure behind one of China's largest AI companies. Unlike pip-install frameworks such as LangGraph, CrewAI, or AutoGen, Astron Agent ships as a complete microservices platform spanning 10+ services across Java, Python, Go, and TypeScript: a ReactFlow-based visual workflow builder for low-code agent orchestration, native integration with the Model Context Protocol (MCP) for tool calling, a built-in model management layer supporting iFLYTEK Spark, OpenAI, Anthropic, and on-premises MaaS deployments, and a multi-tenant Go authentication service powered by Casdoor. The standout differentiator is native RPA integration via the companion astron-rpa project (7,200+ stars), providing 300+ pre-built automation capabilities spanning browser, Office document, and enterprise system interaction — enabling agents to execute physical UI actions rather than only API calls. Infrastructure includes PostgreSQL for multi-tenant data isolation, MySQL for application metadata, Kafka for event streaming, Redis for caching, and MinIO for object storage, all orchestrated through Docker Compose with explicit health checks and dependency chains or production Kubernetes Helm charts. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

Powering mission-critical infrastructure at OpenAI, Cursor, Replit, Lovable, Retool, and Snap with over 22,000 GitHub stars, Temporal is the durable execution platform that originated from Uber's Cadence project — built by the creators of AWS SQS, AWS SWF, and Azure Durable Functions with nine years of production-proven reliability. The workflow-as-code model lets developers write business logic in Go, Java, Python, TypeScript, .NET, PHP, or Ruby using native SDKs, while the Temporal Server automatically persists state at every step, replays from failures, retries activities with configurable backoff policies, and manages task queues without developers writing reconciliation logic. Workflows support signals for external event injection, timers for scheduled delays, child workflows for decomposition, and queries for real-time state inspection — all backed by deterministic replay over an event-sourced history that guarantees exactly-once semantics. The Web UI provides visual workflow execution inspection with event timelines, pending activity monitoring, namespace management, and worker health dashboards. Persistence supports PostgreSQL, MySQL, or Apache Cassandra for horizontal scalability, with Elasticsearch or OpenSearch for advanced workflow visibility queries. Multi-cluster replication enables global failover across data centers. The self-hosted stack deploys via Docker Compose with the auto-setup image, PostgreSQL, Web UI, and admin tools — operational within 30 minutes. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

One server, treated properly: Nanocl runs your containers and full virtual machines from a single declarative Statefile, reconciling what is running against what the file says, so a lone host gets cluster discipline without cluster ceremony. Containers group into Cargoes with replica counts, ordered init containers, and health-aware restarts; finite jobs run to completion and stop. When a workload needs a real kernel or a custom disk image, it boots as a QEMU virtual machine beside the containers instead of forcing a second platform. Publishing is built in: the proxy controller terminates TLS and routes HTTP and TCP traffic, and the DNS controller keeps service names resolving while workloads come and go. Secrets for registries, certificates, and environment variables attach where they are used, never inside the file itself. The daily loop is a CLI and an API: list processes, follow logs, exec into a container, watch events, and back up the entire deployment state before you change it. Namespaces keep projects apart on the same host, and Statefile arguments, templates, and sub-states carry one definition from staging to production. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT or Apache-2.0 licensed.

Fleet-wide container discovery, live log streaming, and Traefik reverse-proxy routing converge into Dockpeek, a lightweight Docker dashboard built for multi-host server environments. System administrators can launch web applications with one click through automatic port binding detection and integrated Traefik label parsing that extracts public routing hostnames directly from container configurations. The platform monitors multi-host environments through encrypted Docker socket proxies, letting operators inspect running containers, query published network ports, and trigger image updates from a unified control panel. Native Docker Swarm integration auto-detects active cluster managers, mapping swarm services and replicated tasks alongside standalone workloads while flagging degraded service replicas. Built-in log inspectors stream stdout and stderr outputs in real time with line-filtering controls to diagnose crashed services without opening remote SSH terminals. Operators can track image registries for newer digest tags, review pending updates across container fleets, and trigger graceful rolling container recreations directly from the dashboard. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

While you sleep, a crew of Claude Code agents in a single Docker container keeps building: you plant a mission, the farm splits it into sub-agents on their own branches, and only work that passes your tests ever lands in the repo. Open the farm in your browser and every agent is a pixel Claude walking its plot, tending a task at a terminal or napping when the budget says stop, with the quest log, mission board, and a hatchery for new agents a click away. Each account is paced against its real five hour and weekly usage, measured live, always leaving you twenty percent and never paying overage, and teammates' agents message each other and hand jobs to whichever account still has room. Talk to any agent from the Claude app on your phone, post quests, set schedules like weekday issue triage at nine, and watch live dashboards the agents maintain themselves. Whiteboards let you sketch while an agent draws back full Mermaid architectures for the whole farm to see, the farm's logged-in browser does website work as you, and Slack mentions, Blender scenes, and other models from GPT to a local Ollama all plug into the same queue. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

With over 600 GitHub stars and a featured Show HN launch, Mission Control is the agent-first command center that replaces the chaos of manually shepherding AI agents with structured delegation, approval workflows, and autonomous execution. The Next.js 15 web UI delivers an Eisenhower priority matrix with drag-and-drop quadrants, a Kanban board tracking tasks through Not Started, In Progress, and Done columns, and a goal hierarchy with milestone progress bars — powered by shadcn/ui, Radix UI, and @dnd-kit. Six built-in agent roles — Researcher, Developer, Marketer, Business Analyst, Tester, and You — receive tasks through a token-optimized API compressing context by 92 percent to approximately 50 tokens versus 5,400 unfiltered. The autonomous daemon polls task queues on cron schedules, spawns Claude Code sessions via the official CLI, enforces concurrency limits, and auto-retries with loop detection that escalates to human decisions after three failures. Field Ops extends execution to 64 external services across 16 categories with working X, Ethereum with MetaMask signing, and Reddit adapters, protected by AES-256-GCM encrypted vault with scrypt key derivation, per-service and global spend limits, a circuit breaker, and three autonomy levels. All data lives in local JSON files with Zod validation and async-mutex locking ensuring safe concurrent writes, backed by 193 automated Vitest tests. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Usulnet packs container management, Trivy security scanning, Nginx reverse proxy, scheduled backups, WireGuard VPN, firewall rules, and multi-node orchestration into a single 70MB Go binary with zero external runtime dependencies. Every module ships in one download with no paid tiers, no telemetry, and no edition gating. Container lifecycle management covers creation, start, stop, restart, pause, kill, and removal with bulk operations, real-time resource statistics, filesystem browsing, and settings editing. Trivy integration scans images and running containers for CVEs with severity scoring, generates SBOMs, and validates CIS benchmarks. The multi-node architecture supports standalone, master, or agent modes where agents connect over NATS JetStream with mTLS encryption, enabling remote Docker host management from a central dashboard. Reverse proxy configuration handles Nginx with automatic Let's Encrypt certificates, TCP/UDP stream proxying, access lists, and dead host detection. Backup operations capture container volumes and Compose stacks on configurable schedules with retention policies and full restore capabilities. A built-in application catalog provides 60+ one-click templates for common services. JWT license validation uses an RSA-4096 public key embedded in the binary, requiring no call-home and working entirely offline. For teams tired of maintaining separate tools for each infrastructure concern, Usulnet collapses the entire stack into a single point of management with Docker Compose deployment alongside PostgreSQL, Redis, and NATS.

Managing multi-server container fleets often deteriorates into fragmented SSH sessions, mismatched compose files, and conflicting port allocations. Composr consolidates multiple Docker host daemons into a unified web dashboard that controls running containers, stack definitions, and system metrics from a single interface. Operators can connect remote Docker daemons through encrypted TCP sockets, inspect container health, and stream live execution logs with sub-second responsiveness. A built-in project creation wizard guides administrators through drafting new Compose topologies across local directories or remote server nodes. In-browser CodeMirror editors deliver live syntax highlighting for YAML files, configuration dotfiles, and reverse proxy definitions without detaching containers from disk. The platform tracks service properties directly, letting you toggle Compose profiles, relocate services between YAML manifests with pre-flight risk checks, and detect target port collisions before redeployment. Integrated backup managers bundle container metadata, compose files, and environment definitions into downloadable archive packages for automated disaster recovery. System operators can open interactive browser terminals into any active container, execute batch maintenance tasks, and configure scheduled image update checks. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.