CreateDeveloper Preview

Aevornix Control

The desktop control plane for your whole project.

Join Developer Preview Read the documentation

Overview

What Aevornix Control is

Control is where a project is actually worked on. It holds the project dashboard, the workflow surfaces for every part of the pipeline, and the agent conversation. It also starts the local backend the rest of the tools talk to. Everything it does is a command on the same surface the command line and the agents use, so the interface cannot do something that is unreachable any other way.

Where it fits

One production path.

Aevornix Control is one system in a pipeline. Each stage takes a defined input and hands a defined output to the next.

Control
Developer Preview
Orchestrates the project, the workflows and the agents.
In
Your intent, and the current project state
Out
A planned unit of work handed to the pipeline
Control decides what needs to happen and calls AevCode to work out how.
AevCode
Developer Preview
Plans changes, validates them, and rolls them back cleanly when they fail.
In
A unit of work plus the project it applies to
Out
A reviewed, reversible change set
Validated changes are applied to the project Core builds and runs.
Design
Developer Preview
Produces the images, textures, materials, meshes and animation a change needs.
In
An asset requirement from the planned work
Out
Project-ready assets in engine formats
Assets land in the project alongside the change that asked for them.
Core
Developer Preview
Renders, simulates, edits and runs the project.
In
The project with its applied changes and assets
Out
A running scene, a test result, or an exported build

What Control runs

Project dashboard: Open, create, validate and migrate projects; see recent work and jump back into it.
Workflow surfaces: The production areas (world, gameplay, interface, audio, animation, effects) each driving the same pipeline.
Agent conversation: Describe intent, review the proposed change, apply or reject it.
Patch review: Every applied change is a reviewable, reversible set rather than an in-place edit.
Test and release: Run the test layers, then the release gate before an export.
Design suite: Art and Studio open from inside Control rather than as separate applications.

Technical foundation

Desktop application: A native desktop shell around the same interface the in-editor workspace uses, so both stay in step.
Local backend: Control starts the project backend itself; the interface retries a cold start rather than failing on it.
Provider keys: Model access uses keys held in a local vault. The project uses your keys, not a shared account.

Evidence