Hey folks,
I built flynnt, a provider-independent Kubernetes-as-a-Service product.
Flynnt hosts your k8s control plane and makes it easy to add compute nodes from anywhere. The compute nodes can be hosted in a public cloud or on-premises, and are owned by you.
Currently, when planning to use kubernetes for your infrastructure, the choices you have are either self-hosting and operating your clusters or using one of the many managed public cloud offerings.
Both options come with trade-offs. Be it vendor lock-in, high operational overhead or data privacy concerns.
Flynnt tries to be another option with different trade-offs.
How does flynnt compare to EKS, AKS, GKE, etc?
In general, most hosted k8s service providers force you to use their compute service offering and don't allow adding arbitrary nodes from outside.
So, flynnt is best compared to "EKS Anywhere", "GKE Anthos" or similar.
Privacy: We are a european company and will be 100% GDPR-compliant on launch. Our service is currently hosted in germany. Your data does not need to be moved into a cloud just for using higher-tier abstractions like kubernetes.
Pricing: Pricing will be fixed per cluster. As you can use whatever hosting provider you want, just choose the provider that fits your pocket. You can also mix different providers for your compute nodes. Just be aware of latency for inter-node communication.
My name is Phil and I am looking for users for the Closed Beta. If you are interested to give this a shot, just fill out the form on the website or shoot me an email (in profile).
Thanks for reading, your feedback is welcome, happy to answer questions.
SAP was the first to adopt this pattern with it's SAP Gardener.
There's currently an open source project working towards making this pattern possible for vanilla K8s named "Kamaji".
Redhat started lately this approach with hypershift.
Looks promicing, wish u lot of success with the product.
Currently, when planning to use kubernetes for your infrastructure, the choices you have are either self-hosting and operating your clusters or using one of the many managed public cloud offerings. Both options come with trade-offs. Be it vendor lock-in, high operational overhead or data privacy concerns.
Flynnt tries to be another option with different trade-offs.
How does flynnt compare to EKS, AKS, GKE, etc? In general, most hosted k8s service providers force you to use their compute service offering and don't allow adding arbitrary nodes from outside. So, flynnt is best compared to "EKS Anywhere", "GKE Anthos" or similar.
Privacy: We are a european company and will be 100% GDPR-compliant on launch. Our service is currently hosted in germany. Your data does not need to be moved into a cloud just for using higher-tier abstractions like kubernetes.
Pricing: Pricing will be fixed per cluster. As you can use whatever hosting provider you want, just choose the provider that fits your pocket. You can also mix different providers for your compute nodes. Just be aware of latency for inter-node communication.
My name is Phil and I am looking for users for the Closed Beta. If you are interested to give this a shot, just fill out the form on the website or shoot me an email (in profile).
Thanks for reading, your feedback is welcome, happy to answer questions.