Robotiq.ai on-premise solution – Appendix to “Platform Overview”
Robotiq.ai on-premise solution
Robotiq.ai on-premise solution is exactly the same as Cloud hosted solution (regarding functionality) but has different deployment. Features and functionality of on-premise solution is the same as cloud based which is described in the document Robotiq.ai – Platform overview.
Talking about cloud vs on-premise solution, we are actually talking about on prem or cloud hosting Headquarters application (HQ app). Hosting robots has already been explained in the document Robotiq.ai – Platform overview.
Main differences between cloud and on-premise solution:
- No BYOK functionality – since deployment is on the client infrastructure, BYOK functionality is needed to secure data at rest in cloud, but on on-premise solution Robotiq.ai relies on client provided PostgreSQL database which can be encrypted based on client setup
- HQ has several services shipped as Docker images – instead of Kubernetes cluster which is on cloud infrastructure, here is Docker compose needed to run the HQ - simplified installation
- Cloud solution is managed by Robotiq.ai team along with patches and new releases, on-premise solution is managed by client infrastructure team (installation of new releases and patches) along with the help of one of our colleagues (if needed).
- Robot – HQ communication – is AMQPS, without certificate sign-in and mTLS for robots – since it is on client's infrastructure (local network), there is no need for generating robot certificates. But if client insists on it, there is a way to import certificate for each robot installed and to enable mTLS and AMQPS communication.
- In on-premise solution client provides service certificates and manages those certificates for HTTPS and AMQPS communication between services – we provide environment variables so that client's infrastructure team can place the needed certificates somewhere where services can reach them for communication
- In on-premise solution client infrastructure team needs to give hostnames (DNS records) for Frontend, gateway, and authentication service so that client end users can reach HQ application
- Provisioning of new releases for on-premise solution, client infrastructure team has granted access to Robotiq.ai repository where signed Docker images for HQ are stored. Then they can download new images and install them following instructions given by the release management team from Robotiq.ai.
These are main differences between on-premise solution and cloud hosted solution of Robotiq.ai.
Below is the detailed picture with HQ and Robots topology, along with protocols, ports used in communication and brief description of each service that HQ consists of.
