Miget is built with a focus on security, reliability, and flexibility, providing a robust platform for deploying a wide range of applications and services. A key feature of Miget’s infrastructure is the concept of Private Networking, which ensures that your services remain secure and isolated from the public internet by default. This means that any service deployed on Miget, whether it’s a managed service like PostgreSQL or a custom application like Elasticsearch, is accessible only within the private network of your Kubernetes cluster.

​
What is Private Networking?

Private Networking at Miget ensures that all services within your application stack are configured to listen on an internal, isolated network. This network architecture is designed to enhance security by restricting access to these services, so they are only available within the boundaries of your specific Kubernetes instance.

​
Key Features of Private Networking at Miget

  • Internal Service Accessibility: By default, every service you deploy on Miget-whether it’s a managed service like PostgreSQL or a custom-deployed application like Elasticsearch-listens on the private network only. This means these services are accessible only to other services within the same Miget instance, ensuring a secure and isolated environment.
  • Instance Isolation: A critical aspect of Miget’s Private Networking is that services within one Miget instance are isolated by default from services in any other Miget instance. Even if you have multiple Miget instances under the same account, they do not communicate with each other through this private network. To connect workloads that live on different resources, put them on the same private network (VPC) — that is what a VPC is for.
  • No External Exposure by Default: Miget is configured to ensure that your services are not exposed to the public internet by default. This significantly reduces the risk of unauthorized access and protects your applications from potential vulnerabilities associated with public exposure.

​
Exposing Private Services using Ngrok

While Miget’s Private Networking provides a secure and isolated environment, there may be situations where you need to expose a service to the external world temporarily. Whether for development, testing, or remote access, Miget integrates seamlessly with Ngrok, a tool that allows you to securely expose private services to the internet. For a step-by-step guide on setting up Ngrok with your Miget services, please refer to our How-to Guide on Ngrok.

​
Going further: private networks (VPC)

The isolation described above is per-resource and comes for free. When you need more than that — workloads on different resources reaching each other, a database reachable only by the applications you name, or access from your own laptop or office — create a private network (VPC). A VPC spans every resource in a region, and can be reached from outside over WireGuard, Tailscale, Cloudflare WARP or a site-to-site tunnel.