I’m so excited about the rapid progress we’ve made at Orchex already in 2025 that I’m going to start blogging about it even though we don’t have a product. We’ve only been in development for about a month and we already have the underpinnings of an Enterprise Orchestration Engine, which is foundational technology for composable software solutions.
Update 15.Dec.2025: After years of frustration with WordPress, I am finally abandoning this blog. The content will likely stay here for some time, but new content will appear here:
There’s quite a bit left to build. This is a high-level summary of what we have so far:
- Generic “native” storage with provider model and webservice APIs
- Orchestration processes including automatic processor dependency resolution
- Custom routes (map inbound webhooks to orchestration processes)
- Scheduled processes
Here is a list of the Orchex introductory blog posts that I intend to write:
- Enterprise Orchestration Engines Overview
- EOE Usage Scenarios
- Orchex Overview
- Why Is Orchex Open-Source?
- EOE Use Cases
- EOE Objectives
- Orchex Stores, Providers, and Webservice APIs
- Orchex Orchestration Processes
- Invoking Orchestration Processes
- Orchestration Processors
- Orchestration Processor Stages
- Orchex LogicBlocks
- Orchex Orchestration Engine
- Orchestration Context
- Orchex Scheduled Jobs
- Orchex Development Environment Setup
- Orchex Simple Processor Examples
- Orchex Custom Routes
- Orchex JavaScript Constructs
deliverystack.net 
16 thoughts on “-Introducing the Orchex Enterprise Orchestration Engine!”