Who it is for Manufacturers
Your product ships with remote access. No backend, no app-store app.
You publish the interface to the product, and ThingFace delivers it on all of its boards with your customers' logins, from anywhere; the firmware does not need to carry it. You do not maintain servers, publish apps, or pay a cloud team.
- available in the beta
- in preparation
- planned
Signed interface
With the product locked, the interface changes only through a publication signed with the product key, with no rollback to older versions. No board can change the fleet's interface.
New interface without reflashing
The new version is uploaded from the command line, with one key per product, and reaches every board of the product. Unpublishing is from the command line or the product's page.
Device API
Named actions over HTTP, events and signed webhooks, and boards calling one another.
Customers, fleet, and support
Organizations holding your customers' accounts, a fleet view, time-limited support access, and an exportable audit log.
A fleet that cannot be redirected
A board's cloud address changes only with a signed order, which the board verifies.
Factory identity
The unit's key is born on the chip and survives a factory reset.
Publishing from CI
The interface is uploaded from your CI without storing any secret there.
Your brand on the portal
The portal with your product's name and colors.
Your system talks to the fleet
Named actions in the interface manifest, called over HTTP with one key per device. The cloud delivers the bytes and returns the board's response, without reading either.
In production, one board calling another took 0.4 to 0.6 s.
POST https://api.thingface.com/v1/devices/{id}/actions/open
Authorization: Bearer [device key]
← 200 [the board's response, exactly as it sent it]
Shall we talk about your product?
Join the list as a manufacturer and tell us how many units you plan to connect. The first invitations go to those with products in series production.
Join the list as a manufacturer