Skip to content

VeeaONE Developer Platform

Build and run applications and AI workloads across the Veea edge.

VeeaONE is a managed distributed edge application platform for deploying and operating containerized workloads across VeeaHubs and qualified runtime targets.

Developers use VHT to build, validate, and deploy containerized software to the target that fits the workload, while VeeaONE provides a common operating environment across distributed physical locations.

How VeeaONE works

From application to managed edge operations.

VHT is the developer toolchain. VeeaONE Runtime provides the common execution layer across native and qualified edge targets.

Developer Containerized application The software and services being deployed
Toolchain VHT 2.0 Build · validate · deploy
Common execution layer VeeaONE Runtime
Native targetVeeaHubs
Qualified runtime targetsLinux · NVIDIA Jetson · specialized hardware
Fleet visibility and operations Operated through VeeaONE

Runtime capabilities and management features vary by qualified target and deployment configuration.

Start with the platform

Welcome to the VeeaONE developer platform.

Get a concise introduction to VeeaONE Runtime, VeeaHubs, qualified runtime targets, and the VHT workflow for building and operating applications and AI workloads across the Veea edge.

Explore VeeaONE Runtime Run the quickstart

Why VeeaONE exists

Distributed edge systems should not become distributed operational problems.

Modern edge applications increasingly span distributed compute, local models, devices, network services, accelerators, and cloud-connected control. VeeaONE provides a common platform foundation for placing and operating software across that real-world edge. Depending on target capabilities and approved platform services, applications can work with local networking, device, storage, and operational interfaces.

Heterogeneous compute

Place workloads across native VeeaHubs and qualified systems with the compute, storage, connectivity, or acceleration profile each part of the system requires.

Local applications and intelligence

Process operational data near its source and support local applications, inference, automation, and agent-assisted workflows where latency, bandwidth, resilience, or data locality matter.

Distributed operations

Apply a common runtime and developer model across fleets of physical locations, with target enrollment, application deployment, capability validation, and operational visibility supported through VeeaONE.

What developers can build

Typical workloads
Containerized applications

Deploy standard services across qualified runtime targets.

Video analytics

Process camera streams and computer vision workloads locally.

AI inference

Run local AI inference and video analytics on qualified accelerator-backed targets, including NVIDIA Jetson-based systems validated for the deployment.

Operational automation

Combine local applications, events, and external AI services to automate business processes.

Choose your starting point

Evaluate the platform or start with an approved development environment.

Public documentation is available through this portal. Production access, third-party runtime enablement, VeeaCloud services, and support depend on an approved account, supported target configuration, and applicable Veea agreement.

Evaluating VeeaONE?

Understand the platform before requesting access

Explore the public documentation, understand the runtime model, and compare target options. Request developer access when you are ready to work with an approved Veea environment.

Explore VeeaONE RuntimeSee how targets participate in the managed VeeaONE environment. Compare runtime targetsUnderstand the roles of VeeaHubs, Linux / Ubuntu, NVIDIA Jetson, and specialized hardware. Become a Veea developerLearn how approved account access, services, environments, and permissions are provided.

Already have access?

Go from prerequisites to a running application

Use this path when you have an approved Veea developer account, a supported and enrolled runtime target, development access, and the required local network connectivity.

Confirm the prerequisitesCheck the development host, target software, enrollment, access, and network requirements. Run the VHT 2.0 quickstartFollow the current Docker-native path from development host to deployed workload. Choose a deployment workflowCompare Docker Compose and Docker Stack for the application you are deploying.

VeeaONE Runtime targets

VeeaHubs are the native edge target. Qualified nodes extend the runtime.
VeeaHubsNative Veea edge hardware with the full managed runtime profile. Linux / UbuntuGeneral-purpose edge compute for local services, storage-heavy workloads, application hosting, and site-adjacent processing. NVIDIA JetsonAccelerator-backed edge compute for qualified local inference, video analytics, and AI-enabled containerized workloads. Other hardwareAdd specialized edge systems for storage, device access, industrial connectivity, acceleration, or location-specific compute. Capability profilesDescribe what each target contributes: compute, storage, networking, acceleration, and device access.

Runtime capabilities vary by target. VeeaHubs provide the full native runtime profile. Qualified nodes should be validated for OS, networking, storage, accelerators, and hardware-specific services before deployment.

Choose the right path

Which VHT workflow should I use?

Use the VHT 2.0 workflow unless you are maintaining an existing application that was built with the VHT 1.x workflow and are unable to migrate it to VHT 2.0 at this time.

New application developmentUse VHT 2.0
Docker-native app development with registries and ComposeUse VHT 2.0
Docker Context, Compose, or Stack deployment workflowsUse VHT 2.0
Existing signed app, .tgz package, or Control Center uploadMaintain with VHT 1.x until you can migrate
Current VHC25 apps or legacy D-Bus integrationMaintain with VHT 1.x until you can migrate
Existing VHT 1.x apps alongside new developmentNew work on VHT 2.0; existing apps stay on VHT 1.x
Production rollout decisionConfirm the target workflow with Veea

Build with VeeaONE

Common developer jobs
Run a VHT 2.0 quickstartCreate a Docker-native app path from a clean Ubuntu host. Manage development hubsAdd, inspect, ping, and remove VeeaHub or VeeaHub Mesh targets. Bring targets onlineChoose placement, register, enroll, and describe the capabilities each target adds. Choose a runtime targetCompare VeeaHubs, Linux / Ubuntu, NVIDIA Jetson, and other qualified edge nodes. Publish imagesUse registries to move application images into the VeeaONE edge environment. Run upgrade checksCompare existing VHT 1.x apps with VHT 2.0 and hub upgrade behavior. Maintain a VHT 1.x appUse vhc, signed apps, and sideload workflows for existing applications. Add app UI linksExpose local app UIs through Control Center and ReverseProxy. Inspect hub runtime detailsRead identity, model, mesh, network, and runtime information through VHT 1.x integration points.