Platform · Dashboards
Dashboards built by AI agents
Describe the view you need and an AI agent writes it as a complete web app that runs inside your console, on your live data. For something quick, drag widgets onto a grid.
Custom dashboards
Apps built around your operation
Hierarchies, navigation, several pages, a design of your own. Three apps an agent built, running in the console.
The map is the menu
Pick a vehicle and the map zooms in and opens its view.
Fleet, region, vehicle
The breadcrumb follows the hierarchy the app was asked to model.
A view made for the job
Speed, cargo temperature, stops and trip log, laid out for dispatchers.
Pages, not tabs
Map, vehicles, trips and reports are pages of one app.
Its own navigation
The app decides its pages and how you move between them.
A device hierarchy
Plant, line, machine. Pick a line and everything follows it.
A drawing, not a grid
The line as it is built, each machine colored by its state.
Your data, read live
Devices, buckets and alarms through the Thinger.io dashboard SDK.
Your brand, your design
Colors, type and layout of your own. It need not look like a console.
Plain language
"Running normally" instead of a gauge. It speaks to customers.
Their sites in one place
Each site with its state and today’s reading, compared with a usual day.
Hosted on Thinger.io
Served from your file storage and opened by a dashboard. No extra server.
How it works
From a request to an app in your console
An agent writes the app, the platform hosts it, and the console opens it already signed in.
An AI agent writes the app
Describe what you need. The agent builds a complete web project in whatever technology suits it, not a layout of widgets.
Into a file storage
The agent writes the project into a file storage, which serves it from its index file, and registers the dashboard.
Opened in the console
The dashboard view renders the app in a sandboxed iframe. It is hosted on the platform, next to the rest of your account.
Your session, no second login
The app loads the Thinger.io dashboard SDK and the console hands it the session, so it reads and acts on your account right away.
Dashboard SDK
Your whole account, already signed in
The app reaches your devices, data and alarms through one SDK, on the console's session. The agent writes this code, not you.
Devices
Read what each device reports and send it commands, like starting a pump.
Thinger.devicesData history
Hours or weeks of stored data for charts, and new values as they arrive.
Thinger.bucketsAlarms and events
Follow the active alarms and react the moment something happens.
Thinger.alarmsThinger.eventsThe rest of the console
Open a device, a project or another dashboard, or reach any other part of the platform API.
Thinger.navigateThinger.fetch
Handed over by the console
- API base
- Access token
- User
- Project
- Dashboard
- Context
No second login. The token refreshes on its own, and the refresh token never leaves the console.
LIVE DATA ON THE SHOP FLOOR
Two ways to build
Same data, two dashboards
One solar site on the same live data: as widgets on a grid, and as the app an agent wrote. Drag the divider to compare.
Same console, same devices and buckets.
Widgets
The quick way: widgets on a grid
No code and no agent. Drop widgets on a grid, point them at your devices and the data starts moving.
Point widgets at your data
A device resource, a bucket, a property or a manual value, with history aggregated on read.
Drag, drop, resize
Edit mode turns the dashboard into a grid you arrange by hand.
Organize with tabs
Each concern gets its own tab, all of them live in the background.
Build once, reuse
A source switcher repoints the dashboard to any device of the same type.
Public links
Private by default, shared through a URL governed by an access token.
HTML widgets
Your own markup with the live value bound in.
Every widget is in the dashboards documentation.
Good to know
Frequently asked questions
What people ask before building their first dashboard.
What is a custom dashboard?
A dashboard whose source is a web app instead of a grid of widgets. The app lives in a Thinger.io file storage, which serves it from its index file, and the console renders it in a sandboxed iframe inside the dashboard view. The app loads the Thinger.io dashboard SDK, and the console hands it the session, so it can read and act on the account without a second login.
How does an AI agent build one?
Through the Thinger.io MCP server. You describe the dashboard you need, and the agent writes a complete web app and publishes it with one tool call, thinger_dashboard_publish, which uploads its files to a file storage and points the dashboard at it. To change it, you ask the agent again.
Which technologies can a custom dashboard use?
Any technology that runs as a web app in the browser: plain HTML, CSS and JavaScript, or a frontend framework built to static files. To reach the account, the app loads the dashboard SDK script.
How does the app authenticate?
It does not ask the user to log in. The console passes the SDK the API base, an access token, the user, the project, the dashboard and a context over postMessage. The token refreshes on its own, and the refresh token never leaves the console.
Can one custom dashboard serve many devices?
Yes. The context tells the app which device, product or group it is opened for, so the same dashboard works as a standalone view or as a template per device or per product. The app can also ask the console to navigate to a device, a product, a project or another dashboard, which is how drill-downs are built.
When should I use widgets instead?
When you want a dashboard in minutes without writing or generating any code. Widgets cover time series, gauges, maps, tables, values, controls and custom HTML, each pointed at a device resource, a bucket or a property, and a widget dashboard can be shared through a public link governed by an access token.
Put your devices on a dashboard
Start with widgets on a free account, or talk to us about the app your team or your customers need.