Get started with Veea

Tell us about your sites and what you want to run on them, and a Veea team member will follow up.

Prefer the full page? Go to Contact.

VeeaONE Developer Platform

Build at the edge.
Operate as one platform.

Build and deploy containerized applications using familiar Docker workflows. Run them on VeeaHubs and qualified Linux, Ubuntu and NVIDIA Jetson systems — all managed through the VeeaONE Platform™.

Explore the public documentation before requesting developer access.

Read the docs Request developer access
  • VeeaHub
  • Linux / Ubuntu
  • NVIDIA Jetson
  • Specialized hardware
  • Accelerator access
  • Device I/O
  • Local storage
  • VeeaHub Mesh
  • Control Center
At a glance

A familiar path from container to edge

  • Familiar Docker workflow

    Build and deploy with VHT 2.0, Docker Buildx, Docker contexts and Compose from an Ubuntu development host.

  • One build, multiple architectures

    Build for x86-64 and 32- or 64-bit Arm targets using a multi-architecture container workflow.

  • VeeaHubs and qualified systems

    Deploy to native VeeaHubs or qualified Linux, Ubuntu, NVIDIA Jetson and specialized runtime targets.

  • Public developer documentation

    Review the requirements, commands and deployment workflows before requesting access.

Why the edge

Process site data where it is created

Cameras, sensors, controllers and other connected systems generate data onsite. Running selected workloads locally can reduce latency, limit unnecessary data movement and keep essential functions operating during WAN interruptions.

VeeaONE provides centralized deployment and management across VeeaHubs and qualified runtime targets while applications continue operating at the site.

A cloud application reaching in The site sends everything out A standalone edge system at each site Your own hardware and your own fleet tooling VeeaONE Runtime + VHT 2.0 A managed runtime across native and qualified targets
Runs where the data is No (weakest) Yes Yes
One build supports multiple CPU architectures No (weakest) Partial Yes (strongest)
Standard container tooling Yes Partial (weakest) Yes
Fleet-wide visibility from one console Yes No (weakest) Yes
Local applications can continue during an uplink interruption No (weakest) Yes Yes
Reaches local devices and radios No (weakest) Partial Yes (strongest)
One workflow, multiple targets

Build once. Deploy to the right edge target.

Use familiar Docker workflows to create multi-architecture container images and deploy them through VeeaONE. Choose a VeeaHub or qualified runtime target based on the compute, storage, acceleration and interfaces the application requires.

Runtime target
Click a target
Build — wherever you already build
Development host Ubuntu 24.04 LTS
  • vhc2
  • docker buildx
One image Multi-architecture build
  • linux/amd64
  • linux/arm/v7
  • linux/arm64/v8
Pushed once Published to a registry
  • Secure registry
  • Local registry for development

Once, at deploy timeDeployments and updates

The site boundary
Run — inside the site
  • VeeaHubNative edge target
  • Linux / Ubuntux86-64, physical or VM
  • NVIDIA JetsonOrin on JetPack 6.2.1
  • Native Veea edge services
  • Managed hub runtime
  • Mesh-aware operation
  • Control Center visibility
  • General-purpose compute
  • Storage-heavy workloads
  • Connectors and backend services
  • Site-adjacent capacity
  • GPU-backed local inference
  • Vision workloads and video analytics
  • Robotics
  • Real-time AI services
The local loop
Sensors, cameras, devices On the site
Your container On the target you picked
Local action At the site

The loop closes here, on this side of the line

From the running container — not on the request path

Change the runtime target and the development workflow remains familiar. The target may provide different capabilities, but the application is built, published and deployed using the same container-based approach. Once running, it can process data and interact with devices locally while remaining centrally managed through VeeaONE.

From target to running application

Six steps to an application running at the edge

  1. Choose the runtime target

    Use a VeeaHub or a qualified third-party system that meets the application's compute, storage, acceleration and interface requirements.

  2. Prepare and enroll the target

    Install VeeaONE Runtime where required, connect the system to the appropriate network and enroll it with VeeaONE.

  3. Prepare the development host

    Use a supported Ubuntu development environment with network access to the runtime target.

  4. Install Docker and VHT 2.0

    Install the standard Docker components and the VeeaHub Toolkit on the development host.

  5. Add and validate the target

    Record the target's capabilities, create its Docker context and confirm the connection.

  6. Build, publish and deploy

    Build the required architectures, publish the container image and deploy it to the selected runtime target.

See the VeeaONE Developer Docs for complete runtime-target preparation, prerequisites, commands and validation steps.

Native VeeaHub advantage

Built-in access to site connectivity and hardware

Applications can run on VeeaHubs and qualified third-party runtime targets. When an application runs on a VeeaHub, it can also use documented platform interfaces to work with the hub’s integrated connectivity, networking and device capabilities.

Depending on the VeeaHub model and configuration, that can include Wi-Fi, Bluetooth, cellular connectivity, serial interfaces, local storage, network services and application-lifecycle controls.

VeeaHub → Native VeeaHub capabilities
Your container Built with VHT 2.0
Authorized access The calling container is identified before access is granted.

Wireless and radios

  • io.veea.VeeaHub.NetworkControl.WiFi
  • .WiFi.DataElements
  • .Wireless.Stats
  • .BluetoothConfig
  • .BluetoothMonitor
  • .Cellular.Status

Network services

  • .Networking
  • .ReverseProxy
  • .MqttControl

Hardware and device I/O

  • .HardwareControl.SerialPort
  • .HardwareMonitoringDaemon.Container

Platform and lifecycle

  • .Info
  • .DateTime
  • .Licenses
  • .ContainerControl
  • .SystemConfiguration.Containers

VeeaHub identifies the calling container and applies its permissions before providing access to supported hardware and platform services.

Built-in VeeaHub capabilities
  • Wi-Fi and Bluetooth radios
  • Cellular
  • Serial ports
  • Local storage
  • Feature licenses

These documented interfaces allow applications to work with supported VeeaHub services and hardware. Available capabilities depend on the VeeaHub model, configuration and application permissions.

VHT 2.0 Recommended for new development

The Docker-native toolkit for building, testing and deploying containerized applications across VeeaONE runtime targets using familiar Docker workflows.

  • Docker contexts, Compose and Stack
  • Multi-architecture builds with Docker Buildx
  • VHT tools for development and runtime-target operations
  • Validation workflows and complete command documentation

VHT 1.x Legacy application support

VHT 1.x remains available for existing VeeaHub applications. VHT 1.x and VHT 2.0 applications can operate on the same VeeaHub Mesh, allowing teams to adopt the newer workflow without immediately rewriting existing applications.

  • Continued support for existing VHT 1.x applications
  • Signed-image, feature-license and template workflows
  • The legacy VeeaHub Client command-line utility
  • Reference documentation and worked examples
Answers

Common developer questions

Do I need an account to read the documentation?

No — the VeeaONE Developer Docs are public and searchable, and reading them takes no registration at all. Developer access is necessary for managed environments, Control Center, protected capabilities, licenses and release workflows.

Open the VeeaONE Developer Docs

What do I need on my development machine?

Requirements vary based on your runtime target. The VHT 2.0 workflow requires a supported Ubuntu development host with Docker, VHT 2.0 and network access to the target. Consult the documentation for current version specifics.

VHT 2.0 prerequisites

Do I have to learn a new command-line interface?

Most development uses familiar Docker commands, including Buildx, contexts, Compose and Stack. VHT commands handle toolkit operations, target setup and validation tasks.

VHT 2.0 overview and command reference

Can I run on hardware that is not a VeeaHub?

Yes. VeeaONE Runtime operates on qualified Linux, Ubuntu, NVIDIA Jetson and specialized systems. Capabilities and supported configurations vary, so verify your target's compatibility before you build.

Supported platforms

How do I get a VeeaHub and Control Center access?

Request developer access. Your development program determines what you receive: a VeeaHub or development environment, Control Center, protected capabilities, feature licenses and release workflows.

Request developer access

Explore more

Understand the platform behind your application

The docs are open. Start there.

Explore VHT 2.0, runtime-target requirements and deployment workflows without registering. When you are ready to build on VeeaONE, request developer access for the managed environments, Control Center capabilities, licenses and release workflows your project requires.

Explore the developer docs Request developer access