Feature Ideas

Support GCP to deploy applications

Sometimes I may need to store files on S3. Eg: I have a service that received images from users, I need to save the images and expose them publicly.

Support Azure to deploy applications

Native support of Datadog as a monitoring platform in Qovery. Important Note: Datadog is already supported in Qovery but we want to provide better integration. Contact us or put a comment if you have any questions.

Support Docker Compose file to configure a Qovery environment and deploy complete apps.

Grafana, Prometheus, and Loki are already installed on the cluster for internal Qovery use. I would like to be able to set up Prometheus to fetch metrics from our applications and use Grafana to analyze them. Also it would be nice to have access to Grafana for more powerful log querying from Loki.

See and create backups for your databases

Vote fore all views in dark

Allows team members to login from a Google account. Today we can only login via GitHub, and most developers have their personal email there. Allowing to connect via Google would let us connect via our work email address.

Add the possibility to add custom tags / labels on the resource managed by Qovery that should be replicated on the cloud provider entities (clusters, pods, managed databases etc..). This will make it more simple to monitor those resources via the standard monitoring tools (datadog etc..)

It seems like any time an environment variable is updated, a re-deploy with full image re-build is required. This takes a long time. Re-deploys should be optimized as much as possible in case of urgent updates. The rebuild is probably required in case the new variables are needed during image building, but in most cases that is probably not needed. Suggest a way to identify variables that when changed, a new image build is required, vs variables that when changed, simply need the container's environment updated. Or, maybe this can be controlled via docker file layers by the customer, in which case this feature idea is unnecessary. But the goal would be to be able to update a "runtime" variable and redeploy quickly.

Support Hetzner to deploy applications.

add the port-forward functionality on the CLI to access private db remotely

Being able to inject helm charts directly on the qovery console and extend the qovery capabilities

Extend Qovery with Sentry, e.g. for release tracking