Skip to content
Sign inRequest access

Products

GPU CloudAMD MI325X and NVIDIA H200 by the hour or on reservation.
Dedicated ClustersPreviewPrivate, interconnected GPU clusters for sustained workloads.
SandboxesPreviewIsolated, short-lived environments for developers and AI agents.
Serverless GPUPreviewGPU containers that scale with requests, down to zero.
Serverless InferenceOpen models behind one OpenAI-compatible endpoint.
Dedicated EndpointsReserved serving capacity for one model, billed per GPU-hour.
PlaygroundSend a prompt to any model your workspace can reach.
Model DeploymentsPreviewImmutable deployments with instant promote and rollback.
Fine-tuningLoRA fine-tunes on the open models in our catalog.
Model TrainingPreviewFoundation-model training runs, managed end to end.
EvaluationsPreviewBenchmark suites and model comparisons you can rerun.
DatasetsManaged and synthetic training data, versioned and ready to use.
Data ManagementPreviewDatasets, connections and storage, with lineage across the platform.
PipelinesPreviewVersioned DAGs that automate data, training and deployment.
Data RoomsPreviewSecure document sharing with guests, NDAs and an audit trail.
NokuvaPreviewThe AI-native design editor.
TavocPreviewA Rust-native code platform: IDE and desktop apps.
FoltracComing soonMulti-cloud deployment with autonomous operations.
W0rkTreeComing soonVersion control for agent fleets.
Identity & AccessMembers, roles, policies, SSO and audit for every workspace.
Billing & CostUsage, invoices, credits and budgets in one place.
Logs & MonitoringRequest logs, latency and error rates across services.
Project CanvasPreviewSee and change a project's resources on one live canvas.

Pages

Home/
Platform/platform
All products/products
Pricing/pricing
GPU pricing/pricing#compute
Inference services/services/inference
Model training services/services/model-training
Protocol design/services/protocol-design
Research partnerships/services/research-partnerships
Protocols/protocols
Datasets/datasets
Documentationdocs.legionedge.ai
Changelog/changelog
News/news
Research/research
Blog/blog
Articles/articles
Events/events
Startup Program/programs/startup
Ambassador Program/programs/ambassador
Partner Program/programs/partner
Event Program/programs/events
Company/company
Careers/careers
Partners/partners
Contact/contact
Statusstatus.legionedge.ai
Terms of Service/legal/terms
Privacy Policy/legal/privacy

Rendering layer

v0.9Beta

Virtual Canvas Protocol

A structured drawing surface for AI-generated graphics and layout.

Available for
  • TypeScript
  • Rust
npm i @legionedge/vcanvas
Read the spec in the registryTalk to the team
virtual-canvas-protocol.tsTypeScript
import { Scene } from "@legionedge/vcanvas";
 
const scene = Scene.parse(modelOutput);
 
// Generated art stays editable — no flattened pixels
scene.select("logo/mark").scale(1.2);
scene.export("svg");
Version
v0.9
Status
Beta
License
Open specification
Implementations
TypeScript · Rust
Stack layer
Rendering

What the spec defines

The guarantees, not the vibes.

  1. Scene graphs instead of pixels — shapes, paths, and groups as validated data

  2. Every element stays addressable and editable after generation

  3. Constraint-based layout shared with the Virtual DOM Protocol

  4. Deterministic rasterization for verification and export

Overview

Why it's built this way.

Spec, schemas and conformance suite

The Virtual Canvas Protocol defines a structured drawing surface for AI-generated graphics: shapes, paths, and layout expressed as validated scene graphs instead of raw pixels. A generated illustration is data you can query, edit, and re-theme — not a bitmap you regenerate from scratch.

The scene graph shares its constraint-layout vocabulary with the Virtual DOM Protocol, so illustrations and interfaces compose on the same verifiable foundations. An icon generated on the canvas drops into a component tree without translation.

Inside Nokuva, the protocol is what keeps graphic work in the cheap medium: refining a mark or adjusting a composition is a scene-graph edit costing pennies, not a regeneration burning tokens.

The spec is in public beta at v0.9 — the remaining work before stable is the animation timeline section. Implementations ship for TypeScript and Rust, and beta feedback lands in the public tracker.

Proven in production

If a protocol can't survive contact with a real product, it isn't finished. This one ships inside Nokuva.

Explore Nokuva

Works with

Designed to compose.

The full stack

Implement it

Implementing the Virtual Canvas Protocol?

The conformance suite is public, and the team that wrote the spec reads its issue tracker. Independent implementations are the point.

Talk protocols with usBrowse the registry