PM at Retool here. Generally speaking, as scalable as any other piece of software. Specifically:
- Retool is datastore/backend-agnostic, so from a backend/data perspective it will be as scalable as whatever backend you’re using to process/store those orders. You can connect Retool to make requests to your own API, to directly query a database, etc.
- From a frontend perspective, you can choose to deploy Retool using Retool’s Cloud, or self-host Retool on your own private cloud. The former is quite scalable, but if you wanted full control over scalability you’d likely opt to self-host. If you’re self-hosting you have all of the “typical” scaling techniques available to you: you can e.g. run Retool on Kubernetes, and vertically or horizontally scale however you need.
- Retool is datastore/backend-agnostic, so from a backend/data perspective it will be as scalable as whatever backend you’re using to process/store those orders. You can connect Retool to make requests to your own API, to directly query a database, etc.
- From a frontend perspective, you can choose to deploy Retool using Retool’s Cloud, or self-host Retool on your own private cloud. The former is quite scalable, but if you wanted full control over scalability you’d likely opt to self-host. If you’re self-hosting you have all of the “typical” scaling techniques available to you: you can e.g. run Retool on Kubernetes, and vertically or horizontally scale however you need.
For more on scaling self-hosted deployments, see: https://docs.retool.com/docs/horizontally-scaling-retool