Request Early AccessTalk to Aegora
Aegora Runtime

Build locally. Operate anywhere.

Run an Operating Path in your environment with policy, approvals, validation, and evidence built in.

Open Download CenterView Bundle Overview
Runtime RoleSignals → decision → governance → verified outcome.
Adoption Path

Download, build, run, prove, govern, scale.

Download. Prove. Govern. Scale.

01Download
02Build
03Run
04Prove
05Govern
06Scale
High-Level Architecture

Runtime governs the space between path design and enterprise execution.

Signals do not jump straight to actions.

Design inputs

Operating Path
Policies
Approvals
Entity context

Runtime core

Signal intake
COR state
Decision engine
Governance gates

Execution and proof

Bounded actions
Validation
Evidence
Learning loop
Runtime trust boundarySignals do not jump straight to actions. They pass through COR, decision, governance, validation, and evidence.
Design Time And Runtime

Problem to Path starts the design. Signal to Outcome runs the operation.

Define the path first. Govern live execution second.

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.

01

Receive signal

A live event enters the governed runtime with tenant, source, and operating context.

02

Assemble runtime truth

The runtime updates COR and establishes the current entity, risk, and operating state.

03

Evaluate and govern

Aegora decides what should happen and applies policy, approval, and execution boundaries.

04

Execute and validate

The selected participant acts, the outcome is checked, and the evidence is attached to the case.

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.

Model routingSelect models dynamically according to policy, task, evaluation, cost, risk, and deployment requirements.
Policy enforcementEvaluate allowlists, approvals, maintenance windows, blast radius, compliance implications, and human fallback conditions before action is authorized.
Runtime stateTrack operating cases, context assembly, decisions, governance state, execution participants, and validation state as first-class runtime records.
Evidence and validationCapture proof of what happened, who approved it, what model or participant acted, and whether the intended outcome was achieved.
Replay and recoveryThe runtime architecture is designed to support replay and recovery paths where supported by the underlying workflow and runtime services.
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.

See Aegora StudioExplore Example PathsOpen Product Experience
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.

Talk to AegoraExplore Enterprise Deployment
Help us improve Aegora

With your permission, we use Google Analytics to understand how visitors use this website. With consent we also collect pseudonymous download, sample and shared-page events. We do not load Analytics until you accept. Read our Privacy Policy.