Toit console

The Toit console is the dashboard for the Toit cloud, which offers various tools to upgrade your devices, monitor your device fleet health, view your daily data usage and much more.


The Devices page lists all devices that are available in your project.

The page lists:

  • The device name.

  • The firmware version currently installed on the device.

  • Date and time of the last time the device was connected to the Toit cloud.

  • The device ID

  • The health status of the device.

You can sort devices by clicking on the column headers.

The Search field allows to search for devices by name, device ID, hardware ID, or firmware version.

A warning sign next to the firmware version means that the installed firmware on the device has been removed from the Toit cloud and is therefore not available anymore.

If so, update the device firmware to the latest version.

Fleet health

The fleet health page collects the device status for all devices in your project.

At the top, devices are represented by different colors based on their current health: green for a device that behaves as expected, and red otherwise. The tooltip shows the name of the device and the list of pending actions or issues for that device.

The overall status section accumulates devices based on their health issues - or lack thereof.

A device can be counted in more than one category, except for devices in the "No issues category" that is exclusive of all others.

Click on the "Go to devices" link to see the list of devices filtered according to their status or issue.


The Playground is an online text editor where you can write Toit programs. Click Run online to execute the code in the Toit cloud. The playground uses the latest firmware version available in the Toit cloud.


This pages let's you communicate with your hardware via the Web Serial API. The serial communication is only for initial hardware provisioning or debugging via the serial port. Read more here.


The Project page is for managing and viewing the various top-level information of your Toit project, such as

  • Details is used to enter the project owner information and payment methods.

  • Users lists all users in the project, starting with the current user. Click on Add user to add new users to the project by simply entering their email address. A welcome email is sent to the newly created user, with a link to set the password for the new Toit account just created.

  • Firmware lists all firmware versions available in your project. A pie chart depicts the distribution of the different firmware versions installed on the devices in your project.

  • Data Usage displays data and graphs that give full transparency on your data usage type (application or system data, such as logs and metrics), as well as usage history and forecast, so you always can predict your upcoming bill with Toit.

  • Invoices lists previously paid invoices, if any.

  • API keys lists the keys that can be used to connect a server application with the Toit API to your devices.


If your devices generate more data than the limit on 100MB of free data per month, submit your payment information here to get access to the full version of the Toit platform.

Toit accepts payment information in a PCI compliant manner. All sensitive data, like your card data, is collected and handled by Stripe, which is the payment infrastructure that the Toit platform integrates with.

All sensitive payment data is securely transmitted to Stripe without being stored in the Toit cloud.

We serve our payment pages in the Toit console securely using Transport Layer Security (TLS) so that they make use of HTTPS.


The System page displays various graphs showing information about Logs and PubSub ingestion in the system.


The Data page allows to create PubSub, Logs, and Metrics subscriptions. Existing subscription are listed on the page and can be deleted with the bin icon. Select a subscription from the list to visualize the unacknowledged message count and the oldest unacknowledged message age for the chosen time interval. Check the API documentation to learn how to acknowledge messages using the CLI.