Are there features not supported by prefect server that are supported by Prefect Cloud? We would like to deploy Prefect Cloud on Kubernetes in test, and maybe use a manage version for production
j
Joseph Desjardins
12/21/2022, 12:40 AM
Hi @Edmondo Porcu, one of the main differences between Prefect Cloud and Prefect Server is the concept of a User. Prefect Cloud has features based on that concept depending on your licensed tier such as Single Sign On, Role Based Access Controls, Audit logs, and SCIM provisioning (Enterprise). Server does not have the concept of a user which means theses features aren’t applicable.
Additionally, with Prefect Cloud, we manage the Orchestration UI and API which we’ve found to be more scaleable than hosting Server on your own infrastructure.
You may also be interested in learning about our Hybrid model which allows flow execution to take place on your Kubernetes Cluster, while we manage the Orchestration UI & API.
Happy to chat more if you’re interested in exploring further!
e
Edmondo Porcu
12/21/2022, 2:05 AM
We are happy to pay the subscription, we already discussed that for the sales team, for a production instance. But the test instance is nice to have it on Kubernetes, so after it gets too dirty you can just destroy it and start it from scratch. @Joseph Desjardins is there a chance to have the same features in a locally managed instance for testing?
j
Joseph Desjardins
12/21/2022, 3:23 AM
As far as orchestration features are concerned, those are fully available with server, which you can deploy on Kubernetes. The features associated with the concept of a user are not available with server.
There’s no authentication built into Prefect Server
There are also some orchestration features (like automations) that are only available in Prefect Cloud because they can’t be implemented efficiently in Prefect Server’s limited architecture.