Become a Veea Developer¶
The VHT documentation can be public, but the Veea developer workflow is not completely anonymous. Register as a Veea developer when you want to move from reading the docs to building, testing, deploying, or using protected Veea services.
Developer registration is the path toward the access you may need for:
- Veea developer services
- Control Center access
- development VeeaHubs or VeeaHub Mesh environments
- partner credentials or partner identity
- feature licenses for protected hub capabilities
- signed artifacts and release workflows
The exact access granted can depend on your Veea relationship, account status, partner status, and the hardware or environments assigned to you.
Become an official Veea developer
Treat registration as the step that connects a public reader to Veea-managed development access. The docs can be open to everyone; Control Center access, assigned hubs or VMs, partner credentials, feature licenses, and signed-release workflows require the appropriate Veea account permissions.
What You Are Signing Up For¶
Developer registration is not just a newsletter form. It is the beginning of the access path for the systems that make VeeaHub development real.
Depending on your role, Veea may provide or enable:
- a Veea account that can sign in to developer services
- Control Center access for managed hubs and applications
- access to a development VeeaHub, VeeaHub Mesh, or VM environment
- partner credentials or a partner developer identity when required
- feature licenses for protected hub capabilities
- the ability to create, test, sign, or release deployable artifacts
You may not need every item on day one. For example, a developer reading the docs or reviewing architecture does not need hub access yet. A developer deploying to a real hub does.
Start Developer Registration¶
Register when you are ready to request the Veea-managed access needed for real development environments, Control Center permissions, assigned hubs, partner credentials, protected capabilities, or release workflows.
Public Docs Vs Developer Access¶
You can read these docs without being registered. Public documentation is useful for understanding the platform, reviewing VHT concepts, and preparing an integration plan.
To actually deploy, test against Veea-managed infrastructure, use Control Center, access a development hub, or use partner-specific capabilities, you should become an official Veea developer and complete the required account setup.
| Need | Registration required? | Notes |
|---|---|---|
| Read the documentation | No | The docs should remain public and searchable. |
| Learn VHT concepts and command flows | No | You can review the workflow before you have credentials. |
| Use Control Center | Usually yes | Requires a Veea account with the right permissions. |
| Use a Veea-provided VM, hub, or development environment | Usually yes | Access must be assigned to your account or organization. |
| Deploy to a real VeeaHub | Usually yes | You need hub access, development mode, and the correct deployment path. |
| Use protected hub features | Yes | Partner credentials or feature licenses may be required. |
| Sign or release partner artifacts | Yes | Requires partner identity and signing credentials. |
After Registration¶
After registering, you should receive further details by email. Depending on your setup, the next steps may include creating or linking a Veea account, receiving partner credentials, getting access to Control Center, or being assigned a development hub or VM.
Note
Some simple VHT 2.0 development flows may work without partner-specific credentials if you already have access to a VeeaHub and can enable development mode. Registration still matters when you need Veea-managed access, Control Center permissions, signed artifacts, or protected hub features.
When Registration Matters¶
Registration matters most when your app moves beyond a local proof of concept.
Become an official Veea developer before you expect to:
- sign in to Veea developer services
- deploy through Control Center or a managed Veea workflow
- receive a developer VM, test hub, or VeeaHub Mesh access
- import partner credentials into VHT
- use feature licenses for VeeaHub capabilities such as Zigbee, Bluetooth, or networking
- create signed artifacts for partner testing or release
If you are not sure whether you need partner credentials yet, start with the public docs and the VHT 2.0 quickstart, then register before you need real hub access, Control Center access, or licensed hardware capabilities.