Skip to main content
New: SensoCAN for iOS and Android. Alerts on your phone, on every plan.

For hardware startups

Build the device. We run the platform behind it.

SensoCAN's startup program takes early-stage hardware teams from a working prototype to a product with monitoring behind it: firmware for the connection, guidance on producing at volume, full platform access during the engagement and one engineer who knows your device, all under written terms.

Apply to the programRead the documentation

How it goes today

A small team has a device that works on the bench. Between it and a product sit the connection firmware, the cloud, the dashboards, the alerts and the app, and every month spent on those is a month not spent on the device.

What an accepted team gets.

Four things the program provides, each written into the engagement before work begins.

  • Firmware for the connection

    We write the firmware that connects your device to SensoCAN, and the terms say who owns it, what is reusable and how long the licence runs.

  • Production guidance

    Step-by-step guidance on taking your hardware from a prototype to production runs, from the first batch onward.

  • The platform during the engagement

    Full access to SensoCAN while the engagement runs: dashboards, rule chains, alarms, the AI assistant and the mobile apps, on a workspace we set up with you.

  • One engineer, in writing

    Our team reviews your hardware's compatibility and the firmware it needs, then sets the scope, the responsibilities and the timeline down in writing before anything starts.

From application to a product with monitoring behind it.

Four steps; the second is where the terms are written.

  • 01

    Apply

    Tell us about your company and the device: what it does, what it senses and how it connects. The program team reviews the application and comes back to you.

  • 02

    Scoping review

    We check the hardware's compatibility, list the firmware work, and write down what is included, what is not, who does what, the timeline and how the work is accepted.

  • 03

    Engineering and platform access

    The firmware is written and tested against your device while your team builds on the platform: a workspace, limits, alarms and the assistant, set up with you.

  • 04

    Handover

    You receive the firmware and the terms that cover it: ownership, source or binary access, licence duration, maintenance, portability and how either side exits.

1

The device's page

Every device your product ships as has a page like this: its status, its topic, the buttons that hold its credentials, and the sensors it reports.

Illustration of a device's page
Node 01Update device information
Device Information
UUID
9f2c7d1e-4b0a-4c58-9e31-6d2f8a41c0e7
Device Status
Online
Location
Bench
MQTT Topic
tenant/1/device/9f2c7d1e-4b0a-4c58-9e31-6d2f8a41c0e7
MQTT Payload ExamplesShow TokenMQTT Credentials
Last Connected
Sep 22, 2026, 2:32 PM
Offline Cutoff
15 minutes
Power Source
Direct Power
Sensors
NameTypeCurrent ValueLast Updated
Temperature SensorTemperature21.40 celsiusSep 22, 2026, 2:32 PM
Humidity SensorHumidity44.10 percentSep 22, 2026, 2:32 PM
  1. The device's page: its status, location and MQTT topic, and when it last connected.
  2. The payload examples, the token and the MQTT credentials are one click away, on the device itself.
  3. The sensors it reports, with the current value of each.
2

Its credentials

Behind two of those buttons: the MQTT credentials and the authentication token the firmware we write connects with.

Illustration of the credentials dialogs
Node 01Update device information
MQTT Credentials

Use these credentials to connect your device to the MQTT broker.

Usernamedev_7f3a91c2
Password••••••••••••
MQTT Client IDnode-01

Keep these credentials secure. They are used to authenticate your device with the MQTT broker.

Device Authentication Token
Tokensc_••••••••••••••••4f2a

Save this token securely. You can regenerate it at any time.

RegenerateCopy
MQTT Payload Examples

Example payloads for sending sensor data via MQTT. Copy and adapt these for your device integration.

SingleBulkBatchBattery
Topic
tenant/1/device/9f2c7d1e-4b0a-4c58-9e31-6d2f8a41c0e7/sensor/temperature-sensor
{
  "data": {
    "value": 23.5,
    "timestamp": "2026-09-22T14:32:00.000Z"
  },
  "battery_voltage": 3.85
}
  1. The MQTT credentials the device connects with, generated when it was created.
  2. The authentication token, which can be regenerated at any time.
  3. The payload examples, in the exact shape the platform accepts, on the device's own topic.
3

A sensor, live

Each reading arrives on the sensor's own page, against the limits you set, with the headroom to each one.

Illustration of a sensor's page
Temperature SensorSensor Details
Profile
Unit
celsius
Minimum Threshold
5 celsius
Maximum Threshold
30 celsius
Email Notifications
Enabled
Current ReadingIn range
21.4celsius
Last UpdatedSep 22, 2026, 2:32 PMLive · updates automatically
Min Threshold · 5 celsius+16.4 celsiusHeadroom above min
Max Threshold · 30 celsius+8.6 celsiusHeadroom below max
Sensor Readings
  1. A sensor's page: the reading as it arrives, live.
  2. The profile: unit, the limits you set, and whether alerts go out.
  3. The current reading against both limits, with the headroom to each.
4

Diagnostics

What the platform heard from the device but could not store, with the reason and the message as it was received.

Illustration of the diagnostics page
Node 01 · DiagnosticsMessages the platform heard but could not store, and why.
Rejected messages3 in the last 7 days
ReasonTopicReceived
Rejected message
The message as it was received, and why it was not stored.
Reason
Malformed JSON
Received
20 minutes ago
Payload
{"data": [{"sensor_slug": "temperature-sensor", "value": 21.4}, {"sensor_slug": "humidity-sensor", "value": 44.1

Preview only — the first 500 characters of the stored payload.

  1. Every rejected message, with the reason it was not stored.
  2. Select one to see it as it arrived.
  3. The payload itself, so the firmware can be fixed without guessing.

Terms confirmed before engineering begins

Every accepted engagement gets written terms that cover four things.

  • Firmware and reusable-library ownership
  • Source or binary access and licence duration
  • Maintenance, portability and exit rights
  • Included work, exclusions, timeline and acceptance criteria

Questions from hardware startups

Who can apply?

Early-stage hardware companies with a device that senses something and can be connected. The form asks about the device and your funding stage, and the program team reviews compatibility first.

Do you build the whole product?

No. We write the firmware that connects your device to SensoCAN and the reusable parts around it. Your product stays yours, and the terms say so.

What happens when the engagement ends?

The terms written at the start cover it: maintenance, portability, exit rights and the licence duration of anything we wrote. Your workspace can continue on any published plan.

Apply to the startup program

Tell us about your company and the device. The program team reviews compatibility and contacts you at the email you give.

SensoCAN Inc. uses this information only to review and respond to your request. Read the Privacy Policy.

Secured by Cloudflare