TCP/UDP connections to containers

As a Nexaa user, you may encounter scenarios where TCP or UDP connections are necessary for communicating with your container. To address this requirement, we propose introducing a feature that enables you to expose one or multiple containers to the public internet, making it possible to run services that rely on non-HTTP protocols. With this feature, you'll be able to deploy and manage services like MQTT brokers, IoT applications, or other non-HTTP workloads on the Nexaa platform with ease. These services often require direct access to the container via TCP or UDP, which is not possible with traditional HTTP-based containers. By assigning a dedicated IP to your account, you'll be able to: Expose multiple containers to the public internet using a single IP address Run services that require persistent connections, such as WebSockets or MQTT, without worrying about connection limitations Take advantage of Nexaa's scalability and reliability features for non-HTTP workloads By supporting TCP/UDP connections, we aim to provide a more comprehensive and flexible platform for our users, allowing you to deploy a wider range of applications and services on Nexaa. This feature will enable you to leverage the benefits of our platform, including automatic scaling, load balancing, and security features, for all your containerized workloads, regardless of the protocol used.