Skip to content

SOLARIO / PLATFORM

You set the intent. Solario governs production.

Solario builds and transforms enterprise software through an explicit production lifecycle. Agents execute bounded work. Solario controls progression. Your organisation retains the executable software, its documentation and the full production record.

01 / PRODUCT LIFECYCLE

One pipeline.
Five governed phases.

Every Workload moves through the same production lifecycle. Greenfield work begins with Intent. Brownfield programmes may begin with Discovery, then enter Intent with a reconstructed view of the current system.

The five phases of the Solario production lifecycle and the Governance Harness that controls progression
OPTIONAL BROWNFIELD ENTRYDiscoveryRecover the current specification, architecture and code graph. Assess risk and candidate transformation paths before deciding what to change.
  1. 01

    Intent

    Compile inputs into signed business goals and requirements.

  2. 02

    Design

    Define architecture, interfaces, rules and delivery obligations.

  3. 03

    Build

    Execute bounded work against the approved design.

  4. 04

    Test

    Verify behaviour, quality and policy conformance independently.

  5. 05

    Deploy

    Release approved, observable software into its target environment.

GOVERNANCE HARNESSGovernance lifecycle, deterministic controls, human checkpoints and a full audit trail surround the complete production pipeline.

SOLARIO ZERO TRUST PRINCIPLE

Agents are never trusted by default.

The Governance Harness constrains what agents can do, verifies what they produce and keeps authority outside the generating workflow.

See the governance model
02 / ONE PRODUCTION RUN

Watch a Workload
move through Solario.

The CLI makes the production lifecycle observable. Follow three moments from the existing Listify campaign and inspect the governed artefact produced at each step.

solario intent prd-listify-full

Compile varied inputs into signed intent.

The CLI resolves the brief, user stories, test cases and design system. Solario Core turns them into canonical goals and requirements, then stops for Product Owner authority.

SOLARIO CLI / INTENTLIVE RUN
Solario CLI starting the Intent pipeline for the Listify workload, showing five stages and twelve inputs being resolved.

Canonical output

Awaiting sign-off

Intent ledger

GOAL-001
Manage lists and items in detail
GOAL-002
Collaborate with role-based access
REQ-013
Enforce viewer permissions
REQ-022
Enforce capacity and tier limits
12 entrants · 4 goals · 22 requirements
Solario CLISolario CoreArtefact Store
03 / PRODUCT COMPONENTS

One product.
Five components.

Console and CLI are the operating surfaces. Core runs and governs the lifecycle. The AI SDK controls model access. The Artefact Store retains the production record.

Solario Console and Solario CLI provide access to Solario Core. Core runs the governed lifecycle, uses the Solario AI SDK for approved model access and retains outputs in the Solario Artefact Store.
Operating surfaces
01 / Human operatorsWEB

Solario Console

Configure Projects and Workloads, inspect production runs, act at human checkpoints and retrieve the retained record.

  • Projects
  • Workloads
  • Approvals
  • Run inspection
02 / Engineers + automationCLI

Solario CLI

Initialise governed Projects, execute phases locally or remotely, inspect progression and integrate the factory into CI.

  • Local
  • Remote
  • CI
  • JSON output

03 / Execution and control engine

Solario Core

GOVERNED RUNTIME

Core composes the Workload, orchestrates execution and owns every legal lifecycle transition. Agents perform bounded work inside the system. They do not define its rules or authorise progression.

  1. 01Intent
  2. 02Design
  3. 03Build
  4. 04Test
  5. 05Deploy
OrchestratorState MachineGovernance HarnessLoop Engineering
Platform services
04 / Model accessSDK

Solario AI SDK

Routes work through approved frontier and open-weight endpoints with one controlled model-access layer.

  • OpenAI
  • Anthropic
  • Bedrock
  • vLLM
  • Ollama
05 / Production recordSTORE

Solario Artefact Store

Retains immutable, classified artefacts with their Project, Workload origin and production provenance.

  • Specs
  • Evidence
  • Outputs
  • Telemetry
  • Verdicts
04 / PRODUCTION RECORD

Every output remains
connected to its origin.

Solario retains more than the final code. Intent, specifications, decisions, evidence, repairs and releases remain linked so the next change begins from an inspectable system, not institutional memory.

ARTEFACT LINEAGE
  1. Approved intentGoals and requirements signed by the accountable product authority.
  2. Delivery BlockBounded scope aligned to the target architecture and delivery strategy.
  3. Design recordSpecifications, interfaces, ADRs, tasks and validation criteria.
  4. Executable changeApplication code, tests, infrastructure and deployment material.
  5. Verified releaseVerdicts, telemetry, documentation and the complete decision history.

SPRINT 0 / SOFTWARE DISCOVERY

Know what to change. And why.

In approximately two weeks, from EUR 20k, turn an existing system into a navigable retro-specification, architecture and code graph, and a set of prioritised transformation paths.