Djinious
Djinious FactoryThe integrated edition of DjiniousComing soon

The whole platform.One cockpit.

In developmentDjinious Factory is not available yet. The nine Djinious applications are — each on its own, or together as one platform.

Djinious Factory brings the nine applications together into one system: one cockpit, one API, one agent. Describe what you want to build in one prompt — Factory carries the project from requirements to release in a single conversation, and an engineer validates every step that matters.

Djinious Factory
Djinious Factory: “What are we building?” — one prompt to start an engineering project, in engineer-validation or autonomous mode, above the projects under way
cockpit, API and agent
1cockpit, API and agent
engineering domains
8engineering domains
functions in one catalogue
220functions in one catalogue
lifecycle stages
11lifecycle stages

What it is

Nine applications become one system.

In Factory there are no separate applications any more, only functions grouped by engineering domain over one data model: one organisation, one project, one file store, one job queue. What DjiniousEngineering orchestrates across the suite today, Factory does in one place.

01

One stream

A project is one conversation. Messages, operations, results, approvals, questions and decisions land in order — whether they come from the agent, a person or a script. It is the project’s record.

02

The reference document

Beside the stream, the reference: the results that must stay in sight, pinned and grouped by lifecycle stage. A pin can stay live, refreshed while someone is looking.

03

Two modes, switchable at any time

Autonomous: the agent chains its turns until the plan is done. Engineer validation: every write or calculation waits for an engineer, who approves it, refuses it or edits its input.

04

The agent proposes, a person disposes

Only someone with the right to validate validates an item. Every result carries its provenance, and its evidence is capped at what actually produced it.

Inside the cockpit

One conversation carries the project.

A real project in a development build: Sterna S2, an electric survey fixed wing, taken from its mission to a flown survey.

01 · The stream

State the mission. Steer the work.

The project opens on the brief, in plain words. Each chapter — mission, requirements, concept, architecture… — folds away once done, keeping its results, operations and answers one click away.

  • Chapters follow the engineering lifecycle
  • The agent keeps its own working brief — you can see it and correct it
  • Every operation is timed and kept
Djinious Factory
The Djinious Factory stream for Sterna S2: the mission brief in plain words, then the first chapters of the project

02 · Stream and reference

Results to validate, side by side.

Open the reference beside the stream: the mission, the requirements, the concept and every later stage, each item with its revision, its kind of evidence and its status. Validate or reject it where you read it.

  • Reference grouped by lifecycle stage
  • Proposed, validated or rejected — by a person with the right
  • The ledger underneath: revisions, provenance, raw data
Djinious Factory
Djinious Factory with the reference open: a flight simulation in the stream, and the mission brief and system requirements waiting for validation

03 · Simulation in the stream

The survey, flown before the first part is printed.

Simulations land in the conversation as live widgets. Here Sterna flies its survey block in Isaac Sim, on the physics of its digital twin, and every check is shown with its verdict: stall margin, speed range, landing, energy reserve, control saturation.

  • Replay, scrub and change the viewpoint
  • Every check shown, passed or failed
  • Every number computed in the project, not quoted
Djinious Factory
A Djinious Factory flight simulation in Isaac Sim: Sterna S2 climbing over its survey block, with airspeed, height, battery and cross-track telemetry, and eight passed checks

Captures from a development build, in the Fumée palette.

End to end

From one prompt to a release.

Factory runs the whole engineering project from a single conversation.

  1. 01Requirements
  2. 02Architecture
  3. 03Sizing
  4. 04CAD
  5. 05Simulation
  6. 06Safety
  7. 07Supply
  8. 08Verification
  9. 09Release

One platform underneath

One API, one rights model, any model provider.

Everything the cockpit does goes through the same public API that scripts and external agents use.

API first

The cockpit uses only the public API. A script or an external agent reaches the same functions, through REST or MCP.

REST · MCP

Any AI provider

The agent speaks a neutral model: dozens of providers built in, or your own OpenAI- or Anthropic-compatible model server.

Cloud · on-premises

Tokens only at the edge

Inside the stack there are no tokens: every call to an engine is signed for the real caller and lives one minute.

Signed assertions

Distributed by default

No state that only one process knows. The API and the runners scale freely; the engines answer signed calls only.

Docker Swarm
Factory and the applications

Factory is built from the engines of the nine applications: the most complete implementation of each capability was kept, the duplicates removed. The applications remain the way to adopt Djinious today — one at a time, or as a platform. Explore the platform today

Coming soon

Be among the first to run a project in Factory.

Tell us about the system you want to build. We will open early access to Djinious Factory with a small number of engineering teams.