Skip to main content

​
Quick Overview

Qovery organizes your infrastructure in a simple hierarchy: Let’s break down each level.

​
Organization

Your Organization is your company’s workspace—the top-level container for everything in Qovery. Key features:
  • Team collaboration across multiple projects
  • Role-based access control (RBAC)
  • Shared cloud credentials and integrations
  • Billing and cost management
Most companies have one Organization. Users can belong to multiple Organizations with different roles.

​
Cluster

A Cluster is a Kubernetes cluster where your services run—a collection of machines (nodes) that execute containerized applications. Two types of clusters:
Qovery provisions and manages the entire cluster lifecycle:
  • Automatic setup and configuration
  • Upgrades and security patches
  • Monitoring and maintenance
  • Auto-scaling with Karpenter (AWS)
Supported providers: AWS (EKS), GCP (GKE), Azure (AKS), Scaleway (Kapsule)Create a managed cluster →
Learn more about Clusters →

​
Project

A Project groups related services that work together for a common purpose. Examples:
  • Main Application (frontend + backend + database)
  • Internal Tools
  • Marketing Website
Structure: 
Project: "E-commerce Platform"
├── Production Environment
├── Staging Environment
└── Development Environment
Learn more about Projects →

​
Environment

An Environment is a deployment stage containing services at a specific version (usually tied to a Git branch). Common types:
  • Production - Live applications (main branch)
  • Staging - Pre-production testing (staging branch)
  • Development - Feature development (develop branch)
  • Preview - Temporary per-pull-request environments
Preview Environments are automatically created for each pull request and deleted when merged. Perfect for testing changes in isolation before production. Learn more →
Learn more about Environments →

​
Services

Services are the building blocks of your environment—applications, databases, jobs, and more.

Application

Your containerized apps built from Git or container registries.Features:
  • Auto-scaling
  • Custom domains + HTTPS
  • Health checks
  • Rolling deployments
Configuration →

Database

Managed databases or containerized instances.Supported:
  • PostgreSQL, MySQL
  • MongoDB, Redis
Modes:
  • Container (dev/test)
  • Managed (production)
Configuration →

Cron Job

Scheduled tasks on a cron schedule.Use cases:
  • Data processing
  • Backups
  • Report generation
Configuration →

Lifecycle Job

One-time jobs triggered by events (deploy/stop/delete).Use cases:
  • Database seeding
  • Pre-deployment checks
  • Environment cleanup
Configuration →
https://mintcdn.com/qovery/Nvnl0g5BHzA0XQmy/images/logos/helm-icon.svg?fit=max&auto=format&n=Nvnl0g5BHzA0XQmy&q=85&s=f6c259d3ee3123f80e74bcb99c9f6f1d

Helm Chart

Deploy packaged Helm applications.Examples:
  • Prometheus
  • Grafana
  • Message queues
Configuration →
https://mintcdn.com/qovery/Nvnl0g5BHzA0XQmy/images/logos/terraform-icon.svg?fit=max&auto=format&n=Nvnl0g5BHzA0XQmy&q=85&s=a0e5acfcbe26b4b86d136930f5b22a57

Terraform

Deploy any infrastructure via Terraform.Use cases:
  • AWS RDS, S3
  • Serverless functions
  • Custom cloud resources
Configuration →

​
Deployment

Deployment is the operational process that takes your code from Git and makes it run on Kubernetes. What happens during deployment:
1

Code Retrieval

Qovery fetches your code from Git (GitHub, GitLab, Bitbucket) based on the branch configured for your environment
2

Build

Your code is built into a container image using Docker. Qovery auto-detects your framework or uses your Dockerfile
3

Push to Registry

The container image is pushed to a registry (AWS ECR, Docker Hub, GCP Artifact Registry, etc.)
4

Deploy to Kubernetes

Qovery provisions all necessary Kubernetes resources (pods, services, ingress, secrets) and deploys your application
5

Health Checks

Qovery monitors your application health and reports deployment status
Deployment features:
  • GitOps automation - Auto-deploy on every Git push
  • Preview environments - Auto-deploy pull requests
  • Zero downtime - Rolling updates with health checks
  • Rollback - One-click rollback to any previous version
  • Pipeline stages - Databases → Jobs → Containers → Applications
Monitor deployments:
  • Real-time deployment logs
  • Service logs (stdout/stderr)
  • Deployment history with status tracking
Learn more about Deployments →

​
Key Features

​
Environment Variables

Configure apps with variables at three levels:
  • Project level - Shared across all environments
  • Environment level - Shared across services in one environment
  • Service level - Specific to one service
Qovery auto-generates connection variables: 
QOVERY_DATABASE_MY_DB_HOST
QOVERY_DATABASE_MY_DB_PORT
QOVERY_DATABASE_MY_DB_CONNECTION_URI
Learn more →

​
Networking

  • Internal: Services communicate privately within an environment
  • Public: Expose apps with auto-generated domains (*.qovery.io) or custom domains
  • HTTPS: Automatic SSL/TLS certificates

​
Next Steps

Quick Start

Deploy your first app in 15 minutes

How Qovery Works

Understand the architecture

Configuration Guide

Explore all configuration options

Deployment Guide

Learn about deployment workflows