Reach every robot in your organization from one place.
Sign in with the account your admin gave you.
Sign in
Create your account
Use the email your admin invited. Access starts after you confirm it.
Confirm your email
We sent a link to . Open it, then come back here.
No access yet
You're signed in as , but this account isn't attached to an organization. Ask your admin, or Sensori, to add you.
Available robots
Open a robot to work through Telepath on it.
A robot shows as reachable when it answered in the last two minutes.
People
Invite someone by email. They create their own account, confirm it, and get the role you picked.
Removing a person ends their access to every robot in your organization within a few minutes.
Shell access
SSH keys people in your organization added. Approve a key and it works on every robot of your organization within a minute; revoke it and it is removed as fast. Keys marked support are Sensori's and are on every robot.
Provisioning
Organizations and robots across every customer. Creating an organization makes its first admin; registering a robot makes its identity and gives you a one-time claim code to type into the robot's installer. Nothing here is visible to customers. How all of this is run: Docs (Sensori only).
Organizations
People: open an organization to add, remove or change the role of anyone in it, and to resend a set-password email. Support does not need the customer's admin.
Releases
Loading…
Robots download a published release in the background and install it when their admin or operator presses Update now (or when Sensori forces it), only while idle. The previous version stays as the backup and comes back by itself if the new one fails its checks. Phased rollout: publish to beta first, put one or two robots on the beta channel (fleet table below), then publish the same tag to stable. Beta robots take beta and stable releases, stable robots take stable only.
Recovery image
The factory image a robot's system disk is rewritten from: the recovery media Sensori provides, or a Linux PC for a robot that no longer boots. Upload a new version here (the browser sends it straight to a private Google Cloud bucket; keep this page open), then make it current. Admins of a robot's organization download the current image from the robot's page with a link that works for a day; the robot's activity records who asked. Old versions stay until deleted. How an image is made and tested: Docs › Operations › Recovery image.
Support requests
Problem reports from Telepath and diagnostics bundles requested from the portal, every organization. Download the bundle, mark it handled when done.
Robots
On the robot: sudo install-host.sh --claim XXXXX-XXXXX (or sudo yuri-claim.sh XXXXX-XXXXX on an installed one). A code works once and expires after 7 days; Reissue makes a new one and retires the robot's old identity.
My settings
Keys and settings you saved in Telepath on any robot. They follow you to every robot you sign in to and keep working there without internet. Change them in Telepath › Settings on a robot; here you can see what is stored and clear it.
Clearing something here removes it from your account. Robots drop their copy the next time they sync (within a minute when online); a cleared key falls back to the robot's own key.
SSH keys
Shell access to the robots of your organization. Add the public key of a computer you use; an admin of your organization approves it, and within a minute it works on every robot: ssh yuri@<robot> through the relay. Remove a key here and it is gone from every robot within a minute.
One file for your ~/.ssh/config: ssh <robot> then reaches each robot of your organization from anywhere.