Skip to content

VHT 2.0

VHT 2.0 is the Docker-native developer toolkit for building, testing, and deploying applications on the VeeaONE edge platform.

Use VHT 2.0 when you want to deploy to prepared VeeaONE Runtime targets such as VeeaHubs, Linux / Ubuntu environments, NVIDIA Jetson systems, or other qualified edge nodes with familiar Docker workflows while keeping the deployment path aligned with Veea-managed edge operations.

Use this section when you are working with the vhc2 command-line tool on an Ubuntu 24.04 LTS development host.

Validate the target workflow

VHT 2.0 is the Docker-native development path. For current testing, use vhc2, Docker Context, Docker Compose, Docker Stack, and a supported runtime target. Validate registry access, deployment path, Control Center behavior, runtime capabilities, and production support for your target scenario before treating VHT 2.0 as a replacement for a proven VHT 1.x deployment flow.

What You Can Do

With VHT 2.0 you can:

  • Configure a development host for Veea edge application work.
  • Add VeeaHubs to local VHT configuration.
  • Choose and validate a runtime target, including VeeaHubs, Linux / Ubuntu environments, and accelerator-backed systems.
  • Create Docker contexts that target VeeaHub Docker daemons.
  • Build multi-architecture Docker images.
  • Push images to secure or local development registries.
  • Run applications with Docker Compose for node-level testing.
  • Test Docker Stack deployment for VeeaHub Mesh workflows.

What VHT 2.0 Changes

VHT 2.0 moves Veea edge application development toward standard Docker workflows.

Area VHT 1.x VHT 2.0
CLI vhc vhc2
Docker image Final image generated by vhc Standard Docker build image
Image location Veea Cloud Public or private registry
Image signing Final image signed by vhc Signed artifacts uploaded to image registry
Deployment Dedicated deployment config Standard Docker Compose file
Capabilities Labels in Dockerfile Labels in Compose file

VHT 1.x and VHT 2.0 applications can run simultaneously on the same VeeaHub Mesh. Existing VHT 1.x applications do not need to be rewritten just because a VeeaHub is upgraded.

Development Flow

  1. Prepare an Ubuntu 24.04 LTS development host.
  2. Register as a developer and create a Veea account if needed.
  3. Enroll a VeeaHub or VM VeeaHub.
  4. Enable development mode for the mesh.
  5. Install VHT 2.0.
  6. Choose the runtime target and record its capability profile.
  7. Add the VeeaHub or qualified runtime target to your VHT configuration.
  8. Create and validate a Docker context.
  9. Build and push a multi-architecture image.
  10. Run the application with Docker Compose or Docker Stack.

For the shortest linear path, start with the Quickstart.

Operating Rules

Keep these rules in mind while moving through the docs:

  • Use vhc2 for VHT 2.0 commands.
  • Use vhc only when working in the VHT 1.x documentation.
  • Keep the Ubuntu host and development VeeaHub on the same network.
  • Prefer DOCKER_API_VERSION=1.39 DOCKER_CONTEXT=<hub-id> docker ... when targeting a VeeaHub.
  • Build and push images before Docker Stack deployment.
  • Use insecure registries only for local development, testing, or isolated networks.

Core Concepts

Concept Meaning
VHT VeeaHub Toolkit, the overall developer toolkit and workflow.
vhc2 The VHT 2.0 command-line client.
Runtime target The VeeaHub, Linux / Ubuntu system, NVIDIA Jetson system, or other qualified edge node where the app is deployed.
VeeaHub The native Veea edge hardware target.
VeeaHub Mesh A group of VeeaHubs managed as a mesh.
Docker context Docker's target selector for local or remote Docker daemons.
Docker Compose Development and single-node testing workflow.
Docker Stack Docker Swarm and VeeaHub Mesh deployment workflow.

Warning

VHT 2.0 examples use vhc2. Use vhc only when you are explicitly working with VHT 1.x material.