Public device profiles and their published assets are free, with no upfront platform fee.
For individual developers & businesses
Connect every device. Keep every system yours.
An online platform for IoT device identities, profiles, firmware versions, codecs and custom app interfaces. Built for individual developers and businesses worldwide.
Invitation-only. Team-assisted registration.
Tell us what you are building. For now, our team handles registration for participating projects. We will provide API access for your integrations; public self-service signup is not open yet.
Join usPUBLIC ACCESS MODEL
Designed for a simpler launch.
Public device profiles are free, with no upfront platform fee. Access is currently by invitation, with registration handled by our team. Publishing policies do not imply immediate onboarding.
The publishing model does not require Ubiversal-specific certification or an approval queue.
Manufacturers remain responsible for all applicable product and regulatory requirements, including FCC, CE or other required certifications.
CORE PLATFORM CAPABILITIES
One profile. Every layer connected.
Ubiversal keeps protocol details, device logic, customer controls and published releases together—without forcing the product into a fixed application payload.
- Profile
- Codec
- App UI
- Publish
FROM DEFINITION TO RELEASE
Product logic stays with the device profile—not the transport.MULTI-PROTOCOL
Use one workflow across connection types.
Describe the protocols each product uses while keeping the profile, codec and publishing path consistent.
DEVICE LOGIC
Keep each product’s payload its own.
A codec translates product-specific reports and controls without forcing every device into the same payload format.
APP EXPERIENCE
Ship controls made for the device.
Upload a custom App UI and an in-app widget shaped around how the product is actually used.
TEST & PUBLISH
Move from tested codec to published profile.
Test sample payloads, publish codec versions, then make the complete device profile public or private.
PUBLISHING WORKFLOW
One clear path to a published device.
An overview of the six-stage publishing workflow. During invitation-only access, our team arranges onboarding and registration for your project.
One publishing workflow.
ONE DEVICE FLOW
06 steps- 01Arrange accessRequest an invitation. Our team coordinates onboarding and handles registration for participating projects.
- 02Create a device profileAdd its name, images, guides, manual and support content.
- 03Add a firmware versionRecord the firmware release supported by the device profile.
- 04Upload the codecAdd the handlers that decode reports and encode commands.
- 05Build the App UICreate the custom control interface and in-app widget for the device.
- 06PublishSet the device profile to public or share it with authorized users.
FOLLOW THE PACKET
Your device logic, carried through every layer.
Ubiversal separates what your device means from how the data travels. Select a stage to see where each responsibility lives.
0xA4 18 2F 0101 · Describe
Your product keeps its own language.
Register the product, transport and protocol details without forcing the device into a universal application payload.
DESIGNED TO STAY OPEN
Own the product. Change the plumbing.
A connected product should outlive its first radio, gateway and cloud integration.
DEFINE & RUN
One flexible contract, both ways.
A JavaScript codec translates product-specific reports and controls without forcing every device into the same payload format.
EVOLVE
Change one layer at a time.
Transport, codec and backend stay modular. Improve one part without redesigning the whole connected product.
AI-READABLE
Structured so AI can understand the device.
Device profiles give AI clear definitions for protocols, payloads, reports, controls, firmware and UI—so it can work from explicit context instead of guessing from raw data.
SUPPORT
Improve support without changing the device.
Update the profile, codec and app experience around an existing product, giving support teams clearer context and customers better controls.
PRODUCT EXPERIENCE
Illustrative examples · Simulated data. These previews are not connected to live devices or customer accounts.
FOR DEVELOPERS & TEAMS
Define the device once.
Bring product information and support into one profile. Add a versioned codec, then publish the App UI and widget people use.
Versioned · Reusable · Ready to publish
ACCESS MODEL
Public profiles. Private options.
Public profiles are free. For private access, get a quote for your project. Both options are available by invitation, with registration handled by our team.
PUBLIC
Free
Public device profiles and their published assets are free.
- Public device profiles
- Firmware versions and codecs
- App UI packages and device widgets
- Multi-protocol definitions
PRIVATE
Get a quote
Contact us for private profiles, restricted access and non-public device assets.
- Private device profiles
- Non-public payload settings
- Private codecs, App UI and widgets
- Controlled collaborator access
Access is currently by invitation. Public self-service registration and subscription checkout are not available. For enquiries, email support@ubiversal.com.
INVITATION-ONLY ACCESS
Your project starts the conversation.
Building on your own or with a company? Individual developers and businesses worldwide can request an invitation. No company is required to enquire.
Device registration, handled by our team.
For participating projects, Ubiversal registers and stores device IDs and keys received through production integrations. Our team currently operates this workflow on behalf of customers.
This is our current onboarding arrangement. We provide API access for your integrations and discuss the services available for your project. Public self-service signup is not open yet.
QUESTIONS, ANSWERED
Start with clarity.
The short version of how Ubiversal fits around your product and where to begin.

