Product

The Devory platform, capability by capability

Devory is a visual software engineering platform for designing, building, integrating, operating and deploying software through an extensible node-based workspace. The list below covers every major capability area with an honest status, so you can see exactly what exists today.

Available in pilotIn active developmentPlanned

“Available in pilot” means the capability is real and validated inside Devory’s internal engineering pilot — it does not mean public or customer sign-up is currently open.

Capabilities

Visual engineering canvas

Available in pilot

A node-based canvas for composing software visually. Components, connections and structure are inspectable at a glance, backed by an authoritative underlying graph model rather than a picture that only looks like software.

Workspaces and projects

In active development

Projects group the graphs, components and configuration an engineer is actively working on. Workspace organization is being extended from individual projects toward shared team workspaces.

Components and reusable libraries

In active development

Software is composed from versioned, typed Components 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.

Runtime and execution

Available in pilot

A deterministic local execution engine plans, schedules, runs and journals component executions as real processes, with recovery from ordinary failures. Execution is currently limited to trusted, known components.

Deployments and environments

In active development

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.

Git and source control

Planned

Source-control-aware workflows are part of Devory's engineering direction, connecting graph changes back to versioned history. This is planned rather than shipped today.

Terminal and developer tools

Planned

Direct terminal access alongside the visual canvas is planned so engineers can drop into familiar command-line workflows without leaving Devory.

AI-assisted engineering

In active development

Devory is building a typed, permissioned interface through which AI agents can operate the platform under explicit confirmation and audit boundaries, distinct from unsupervised automation.

Extensions, plugins and MCP

Planned

An extensible plugin architecture, including support for MCP-style tool integrations, is planned so third parties can extend Devory's capabilities under a governed trust model.

Marketplace direction

Planned

A marketplace for distributing components, templates and extensions is part of Devory's long-term direction. No public marketplace or commerce exists today.

Teams, organisations and permissions

In active development

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.

Desktop and cloud relationship

In active development

Devory Desktop is the local engineering environment; Devory Cloud provides identity, collaboration and marketplace services. Connecting the two into one seamless experience is active, ongoing work.

Want to see how this applies to your team?

Read how Devory maps to specific engineering roles, or get in touch directly.