Running on Self-hosted Deployments

Using your local Transitive deployment is much like using portal.transitiverobotics.com. You log in using the admin user and the password auto-generated by the deploy script executed from the curl command (see the output at the end of the script or check your .env file).

From your portal instance you can add devices and install capabilities. You can create your own capabilities and upload them to your self-hosted NPM registry to make them available to robots connected to your self-hosted instance.

Using Transitive Robotics Capabilities when Self-hosting

When self-hosting, you can still install and use capabilities from transitiverobotics.com, including premium capabilities. To enable this, configure TR_BILLING_USER and TR_BILLING_SECRET in your .env file to be your portal.transitiverobotics.com username and JWT secret (see Security on portal.transitiverobotics.com). When configured this way you are "picking up the tab" for all premium capabilities installed by devices connected to your self-hosted instance.

After updating your .env, redeploy using docker-compose -p cloud up -d for the changes to take effect.

Your self-hosted deployment will report usage to the billing and licensing server associated with transitiverobotics.com and will hence require access to the Internet, at least from time to time. If you are interested in running a self-hosted instance offline, or with severely limited access to the Internet, please contact us.