Aegora Runtime
Build locally. Operate anywhere.
Download Aegora Runtime, create an Operating Path, run it in your environment, and move from experimentation to governed enterprise deployment without rebuilding the operating definition.
Runtime is one modular product inside the broader Aegora platform. Customers should be able to adopt it independently while still connecting it to Strategy, Discovery, and Studio when they expand. Runtime includes the evidence, outcome, and improvement loop needed to make governed execution better over time.
Adoption Path
Download, build, run, prove, govern, scale.
The runtime is positioned as portable and customer-controlled so the operating definition can grow with the deployment model.
01Download
02Build
03Run
04Prove
05Govern
06Scale
Design Time And Runtime
Problem to Path starts the design. Signal to Outcome runs the operation.
The runtime is most useful when teams separate the design-time motion from the runtime motion. Define the path first. Then let the runtime govern live execution against that path.
Problem to Path
Define the operating problem, the accountable outcome, the signals involved, the policy boundaries, and the Operating Path that should govern execution.
Signal to Outcome
Once the path exists, the runtime turns live signals into governed execution, evidence, validation, and operational learning.
Deployment Profiles
Choose the deployment model that matches your control requirements.
Aegora Cloud is not presented here as a mandatory dependency for core execution. The runtime is positioned around customer control and portability.
Local development
Use the runtime to author, validate, simulate, and prove one Operating Path before expanding into broader governed deployment.
Private enterprise deployment
The architecture supports customer-controlled deployment profiles where data, policies, and runtime boundaries remain under enterprise control.
Customer cloud or on-premises
Target deployment profiles include customer cloud, on-premises, Kubernetes, and provider environments where supported by the deployment assets in this repository.
Provider environments
Managed service providers and partners can use governed paths in their own delivery environments while preserving explicit decision, policy, and evidence boundaries.
Bundle Overview
Download the Runtime Bundle and continue through the guided setup.
The current customer handoff is bundle-first. The download includes a prebuilt runtime image archive, an environment file, a Compose file, and startup scripts, so customers do not need the source repository to get started. The step-by-step run instructions live in the download package and download flow rather than on this page.
Prebuilt runtime image archive
Included in the current Runtime Bundle download.
.env.example
Included in the current Runtime Bundle download.
Docker Compose file
Included in the current Runtime Bundle download.
Docker and Compose startup scripts
Included in the current Runtime Bundle download.
Stop scripts
Included in the current Runtime Bundle download.
Bundle README
Included in the current Runtime Bundle download.
What happens next: download the bundle, review the included environment file, and use the packaged setup scripts and README to launch the runtime in your environment.
Important: the current bundle includes the runtime image and startup assets. Customers still need to provide reachable service URLs, database settings, and secrets in
.env.Runtime Services
What Aegora Runtime is designed to enforce.
The Runtime Engine keeps governance, evidence, outcome validation, and runtime improvement attached to the operation rather than bolted on after execution.
Where To Go Next
Start with one governed path in your environment.
The recommended first-run product path in this repository starts from the Problem to Path motion, lets Helix draft the first path, and then moves into governed review and Signal to Outcome runtime operation.
Runtime Next Step
Move from bundle to governed proof.
Use the runtime to prove one accountable outcome, then add policy depth, enterprise integrations, approvals, and continuous improvement over time.