Product
Devory Platform, Desktop, Cloud, Runtime and Autonomous User Interface are not five independently completed products. They are five connected surfaces of one governed engineering system, each shown below with its own honest status.
Devory is not a workflow tool, a package manager or another AI assistant. It is the infrastructure layer for software composition: a governed system where trusted capabilities are built once, qualified and reused, by engineers and by autonomous AI agents, instead of being reintegrated from scratch on every project.
The graph-native engineering platform: software modelled as components, interfaces, capabilities, providers, graphs and revisions.
The native engineering environment for local projects, graph editing, persistence and controlled runtime execution.
The browser-based collaborative application for identity, organisations, shared projects and Cloud-connected workflows.
The execution and qualification foundation that turns authorised graphs into deterministic, controlled, auditable operations.
The governed interface through which external AI agents act on behalf of authenticated users, scoped, confirmed and audited, never unrestricted.
Public Release 0.1 is live: self-serve sign-up, real billing and a scoped set of cloud-execution and marketplace capabilities are open to everyone today. The rest of the platform is shown below with its own honest status, not rounded up.
| Product | Current stage | Available to | What works now | What remains |
|---|---|---|---|---|
| Devory Platform | Foundations substantially implemented | Internal pilot | Graph composition, component and capability modelling, typed interfaces | Full end-to-end integration and pilot qualification |
| Devory Desktop | Active integration | Internal pilot | Local projects, native graph workspace, local persistence | Every Cloud-connected workflow completed end to end |
| Devory Cloud | Public Release 0.1 — live | Everyone — public self-serve sign-up | Self-serve sign-up/sign-in, real organisations and workspaces, Stripe billing, scoped cloud-workflow execution, Marketplace browsing | Broader workflow/component coverage; execution beyond the current safe component set |
| Devory Runtime | Local foundations implemented | Internal pilot | Planning, scheduling, real subprocess execution, journalling | Full Cloud submission and production operational qualification |
| Devory Autonomous User Interface | Protocol foundation implemented | Not externally connectable yet | Capability discovery, resource scopes, confirmation, audit envelopes | An externally reachable network transport; external pilot integration |
| Devory Marketplace | Live pipeline, catalogue still empty | Everyone — browsing is public; publishing requires a Devory account | Real publisher accounts, listings and moderation, entitlement-gated orders and commission accounting | A populated public catalogue — no listings are published yet; broader install experience |
The same platform, viewed by what each capability does rather than which product surface it belongs to.
Build
A canvas of rounded-square tiles for composing software visually. Each tile is a real engineering capability with inputs, outputs and state, inspectable at a glance and backed by an authoritative model, not a picture that only looks like software.
Projects group the tiles, connections and configuration an engineer is actively working on. Workspace organization is being extended from individual projects toward shared team workspaces.
Software is composed from versioned, typed component tiles rather than ad hoc scripts. A foundation library of common component types is defined; a shippable catalogue of ready-to-use components is still being built out.
Source-control-aware workflows are part of Devory's engineering direction, wiring source history directly into the canvas as a tile. This is planned rather than shipped today.
Direct terminal access alongside the visual canvas is planned so engineers can drop into familiar command-line workflows without leaving Devory.
Execute
A deterministic local execution engine plans, schedules, runs and journals tile executions as real processes, with recovery from ordinary failures. Execution is currently limited to trusted, known components.
Devory tracks deployment and runtime state as part of its cloud services. Binding that state to live, customer-controlled cloud environments is in progress rather than generally available.
Devory Desktop is the local engineering canvas; Devory Cloud is the shared canvas for identity, collaboration and marketplace services. Connecting the two into one consistent experience is active, ongoing work.
Govern
Identity and organisation services support personal and team-scoped access with role-aware permissions. These services are real but not yet generally wired into a customer-facing product surface.
Extend
The Devory Marketplace is being introduced as a public catalogue of verified components, capabilities, providers, templates and integrations. Browsing is public today; installation, publishing and commercial transactions remain limited to qualified or future workflows.
An extensible plugin architecture, including support for MCP-style tool integrations, is planned so third-party tiles can join the canvas under a governed trust model.
An AI agent doesn't need to reinvent common infrastructure to work inside Devory. Through the Autonomous User Interface (AUI), it operates as a typed, permissioned participant that can discover qualified components and compose them into a working system, under explicit delegation, confirmation and audit boundaries. That is distinct from unsupervised automation, and it is one capability inside the system, not the system itself.
