Skip to content

VeeaONE Developer Platform

Build and run software across the Veea edge.

VeeaONE Runtime brings native VeeaHubs and qualified Linux / Ubuntu, NVIDIA Jetson, and specialized hardware targets into one managed edge runtime environment. Use VHT to build, validate, and deploy containerized workloads, from local services and web interfaces to persistent data apps, background jobs, cloud-connected workflows, and AI-enabled edge workloads.

Start with native VeeaHubs, add Linux / Ubuntu nodes where more compute or storage is needed, extend to Jetson for accelerator-backed AI workloads, and bring specialized hardware online as deployment requirements grow.

For AI workloads, deploy to accelerator-backed targets such as Jetson when local inference, video analytics, or real-time decisioning need to run close to the data.

VeeaHubs Linux / Ubuntu NVIDIA Jetson x86, ARM / other hardware

Why Veea

Use the edge as a managed application platform.
Run software at the edge

Deploy containerized workloads on VeeaHubs and qualified edge nodes, then extend into additional validated placements as those topologies mature.

Stay useful locally

Build applications that keep state, process data, expose local services, and continue operating when cloud connectivity is limited.

Choose the right deployment path

Use VHT 1.x for legacy signed packages and Control Center upload flows, or VHT 2.0 for Docker-native registry, Compose, and Stack workflows.

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, and site-adjacent capacity. NVIDIA JetsonAccelerator-backed edge compute for qualified local inference and AI-enabled 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?
Existing signed app, .tgz package, or Control Center uploadUse VHT 1.x
Current VHC25 apps or legacy D-Bus integrationUse VHT 1.x
Docker-native app development with registries and ComposeUse VHT 2.0
Docker Context, Compose, or Stack deployment workflowsUse VHT 2.0
Existing app compatibility alongside new Docker-native appsUse both
Production rollout decisionConfirm the target workflow with Veea

Public docs, official access

Read the docs today. Sign up when you are ready to build on Veea.
Explore publicly

Use the documentation to understand the platform, compare VHT 1.x and 2.0, and plan your edge application.

Become a developer

Register for the account access, developer services, environments, and permissions needed to work with Veea systems.

Deploy with confidence

Use the right workflow for your target: VHT 1.x for legacy signed apps, or VHT 2.0 for Docker-native development.

Start here

Get from account to deployed app
5 steps
  1. Create your developer accountSet up access so you can work with Veea developer tooling. Account
  2. Prepare and enroll a runtime targetChoose the target, install the runtime, register, enroll, and confirm its capability profile. Runtime
  3. Install the toolkitInstall VHT for your target workflow. Tools
  4. Run the first appBuild and run a containerized workload on VeeaONE edge infrastructure. Build
  5. Choose a deployment pathUse Docker-native VHT 2.0 or legacy VHT 1.x packaging as needed. Deploy

Choose your path

VHT documentation
VHT 2.0Current Docker-native workflow with vhc2. VHT 1.xLegacy vhc apps, signing, Control Center UI links, and hub runtime integration.

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. Build for VHC25 VHT 1.xUse vhc, arm32v7, signed apps, and sideload workflows. 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.
VHT 1.x and 2.0 can coexist.

Use VHT 1.x for existing signed app and D-Bus workflows. Use VHT 2.0 for the Docker-native future. These docs keep both paths clear so teams can run today’s apps while preparing the next release path.