Feature Requests

Several database providers rely on IP whitelisting in addition to password to prevent unauthorized connections. Even though we recommend using mTLS or VPNs whenever possible, in several cases it's still the only possible option and we need to provide static IPs that can be whitelisted.

Um bot no discorde que cria Beyblade apenas com oque a pessoa fala com as peças do jogo do Roblox Beyblade Physics e que tmb pode dar rank pro Beyblade de f a s+ como um rpg

I run a monorepo setup, and as I understand it, if I set my working directory to the root of each service, it should only deploy when that service changes. However, I've observed that every push redeploys each service in my monorepo despite no code changes to most of them. Is this a known issue, and are there any steps I can take to resolve the problem I'm experiencing? It's particularly annoying to either have to go through and cancel all other deployments or have to wait for them to complete 1 by 1 due to throttling.

I am writing because I recently requested the deactivation of my organization subscription, but I have not yet received a confirmation email. I have already checked my spam folder and account settings, but the status remains unclear. Could you please confirm that my subscription has been successfully cancelled and that no further charges will be applied?

Today, you can connect a GitHub organization to only one Koyeb organization. We want to enable you to connect a GitHub organization to multiple Koyeb organizations so you can deploy the same repository to multiple Koyeb organizations.

There is already a post about a monthly spending limit ( https://koyeb.canny.io/feature-requests/p/budget-spending-limits ). I'd like to suggest a one-time upload of cash, and when that amount is reached all resources will be suspended until they are manually downgraded or more funds are uploaded.

I try to deploy the new nemotron 3 with vLLM on a A100. I have a Pro account. I hit the RAM limit ...

We need to ease the way to execute certain tasks before a new deployment of a service. That would be useful to invalidate cache, perform migrations, or any other tasks that need to be performed before the app is deployed and running.

Sometimes, you do not want your secret or environment variable to be exposed at run time. We want to let you set the scope of secret and environment variables to build time, runtime, or both so you can manage what data is exposed.

It's possible to use the Docker Hardened Image Registry with the custom registry configuration but this is only for final image pull. Please support auth for dhi.io during the build phase so we can use FROM on the free dhi.io templates that still require auth.