Ready to use Kubernetes namespaces
Easy to use, secure and cost-effective. Deploy your app in seconds
Create a namespace and deploy your application in seconds
Through the console, or through our API, it only takes a few seconds to create a fully functional namespace in which you can deploy your application. PodFactory can be used in your CI/CD pipeline to provision namespaces for deploying and testing your builds. PodFactory can also be used to provision long term namespaces to host your production environments
Run workloads without the need for extensive Kubernetes knowledge
Deploying Kubernetes on premise is hard and not recommended by most books on the subject. The alternative is to deploy Kubernetes in the cloud. But in the cloud, only the control plane is managed by the hosting provider. You still need to have extensive knowledge of Kubernetes in order to:
- consume storage
- interconnect with your hosting provider’s network
- secure your cluster
- deploy observability and monitoring stacks (ElasticSearch, Kibana, Prometheus, Grafana, AlertManager, etc.)
- deploy multi-tenancy
- optimize your workloads in terms of CPU, memory and storage requirements
- set up backups (for the configuration and for the data)
- control costs
- setup best practices for your users
With PodFactory, you create namespaces in clusters that are already secure, and that have all of the above elements taken care of.
Our namespaces are for all budgets, ranging from very cheap to very expensive:
- cheap namespaces run on dedicated entry-level hardware with no redundancy options. They’re ideal for deploying an application to a testing or quality assurance environment, manually or from a CI/CD pipeline
- standard namespaces are ideal for running production environments, they can be hosted on any of our partner hosters
- premium namespaces run on Google, Amazon or Azure and include premium options (like premium storage) from the hoster. On top we add our support and SLA
It is also possible to use dedicated clusters to your tenant. This ensures that your teams are the only ones creating namespaces on these clusters. This option is more expensive because all cluster resources are billed, whether they’re being used or not.
Our namespaces are secure and adhere to all configuration best practices:
- at the hoster level, where the hoster provides a control plane that is managed according to best practices
- at the cluster level, where PodFactory ensures security and robust multi-tenancy
- at the namespace level where you, the customer, are forced to deploy according to best practices.
This means that you will have to work with security constraints that might force you to adapt the way you deploy your application. For example, you cannot deploy a Pod that runs as root. This means that you will potentially have to rewrite your Dockerfiles to make sure your processes run as a standard user.
The flipside is that you do not have to worry about security, you do not have to worry about compliance and you do not have to worry about upgrades and following security announcements.
Our team is available to discuss your specific needs and help you with these aspects and constraints.