Forum01
Choose the readings and controls to expose.
Define product streams, settings and actions around your existing application.
Give customers an application built around your equipment.
Your equipment, readings and controls. Your customer’s application.
Customer portal · level-monitor reference
From your product definition to their daily view.
02
Give each customer their own equipment.
Allocate devices and sites, then configure roles and the branded customer view.
03
Show the result of a real request.
Present fresh readings and permitted controls. Distinguish requested, pending and applied state.
Reference product view · integration required
Product integration and plan limits apply. Customer access does not include your engineering tools or local safety controls.
Setup and technical guides ↓Setup and technical guides
Choose the setup question or guide you need.
What you do not have to reconstruct between tools
Device identity, product definition and customer/site allocation connect the two experiences. Share only the data and controls you deliberately expose. Customer permissions do not grant terminal, account administration or unrestricted engineering access.
Keep the responsibility clear
Build the branded web view around your product integration. Native apps and business-system connections are separate engineering work. Check your plan’s domain and branding options. Your team owns product calculations and equipment behaviour.
What would we need to change?
Configuration, product engineering and subscription eligibility are different requirements.
Enable and configure
Integrate the selected product contract, configure the customer view, branding, allocation and roles, then exercise data and control outcomes. Product Applications can add bounded records and processes when needed; they are not a substitute for specifying product behaviour.
What you keep
Keep your hardware, Linux, application, firmware and local safeguards. An adapter can add customer data and controls without rewriting the product. RAUC and managed containers are independent options.
Plan and readiness
Standard supports one Customer Portal and one downstream customer organisation; Business+ supports a multi-customer product within current published limits. Device/runtime readiness and integration remain separate from subscription eligibility.
Read the guide → →
The tools underneath the job
Use the exact implementation guides to check the supported contract and limits.
Use the Customer Portal for your product
Configuration and implementation requirements.
Read the guide → →Device data and control contract
Configuration and implementation requirements.
Read the guide → →Product Applications
Configuration and implementation requirements.
Read the guide → →
Bring a specialist into the work
Ask for help where evidence or an integration decision is unclear. Use the context and permissions available to that conversation.
Hardware, product and operations help
Equidna helps connect supplied hardware evidence to the software path; Nutria helps plan the customer job; Pingüino helps investigate authorised operational evidence. Shared-room help remains read-only. 24/7 AI assistance has plan and usage conditions.
Read the guide → →
Choose one useful result to prove.
Use the reference to build your own test. Validate the hardware, integration and operating process on your product.
Build a level-monitor product
Review the procedure and qualify the parts your product requires.
Read the guide → →Check adoption requirements
Start with the product you have, then choose independent optional paths.
Read the guide → →
Start with this job.
Integrate the selected product contract, configure the customer view, branding, allocation and roles, then exercise data and control outcomes. Product Applications can add bounded records and processes when needed; they are not a substitute for specifying product behaviour.