It’s more of an orchestrator. Destinations are controlled through runtime “adapters” which essentially tell Pando where and how to put apps. Instead of partitioning a container, it creates an isolated network and deploys the different workloads of your app as containers (database, web, api, etc.)
Since it’s modular, the goal is to be able to use AWS, GCP, kubernetes, etc. as the destination for apps, if you are already using that.(not all of them are built yet). By default it uses Docker.
Since it’s modular, the goal is to be able to use AWS, GCP, kubernetes, etc. as the destination for apps, if you are already using that.(not all of them are built yet). By default it uses Docker.