Other Hardware¶
Specialized hardware lets VeeaONE extend into deployments where a generic node is not enough.
Use this target family when a deployment needs a specific physical capability: expanded storage, industrial connectivity, serial or USB access, camera-adjacent processing, ruggedized operation, custom accelerators, gateway hardware, or specialized network placement.
What Specialized Hardware Adds¶
| Capability | Example |
|---|---|
| Device access | Serial, USB, CAN, GPIO, cameras, sensors, radios, or industrial buses. |
| Storage capacity | Local media retention, site data archives, image storage, logs, and batch processing. |
| Industrial fit | Ruggedized systems, environmental tolerance, DIN-rail devices, or field-ready gateway hardware. |
| Specialized acceleration | GPU, NPU, TPU, FPGA, or workload-specific hardware. |
| Network placement | Gateways near OT networks, private networks, restricted zones, or site equipment. |
Good Candidates¶
Specialized hardware can make sense for:
- manufacturing and industrial sites
- camera-heavy locations
- energy, utilities, or field operations
- transportation and logistics environments
- retail or venue deployments with local analytics
- storage-heavy edge applications
- AI or sensor workloads that require a specific hardware interface
Enrollment Model¶
The target joins VeeaONE infrastructure through the same high-level runtime path:
- Choose the hardware role.
- Install or activate the VeeaONE Runtime profile.
- Register the target with Veea services.
- Enroll it into the intended site, mesh, or operational environment.
- Describe the capabilities the hardware contributes.
- Deploy applications with VHT 2.0.
Capability Profile¶
Specialized targets should be documented by what they add to the environment:
| Area | What to Capture |
|---|---|
| Hardware identity | Vendor, model, architecture, serial, and intended placement. |
| Compute | CPU, memory, accelerator hardware, and container constraints. |
| Storage | Capacity, persistence path, write endurance, backup model, and app data policy. |
| Network | Interfaces, routing, DNS, firewall posture, and site reachability. |
| Device I/O | Attached devices, buses, permissions, drivers, and container access model. |
| Operations | Logs, health, restart behavior, updates, and VeeaONE visibility. |