> ## Documentation Index
> Fetch the complete documentation index at: https://www.qovery.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Frequently Asked Questions

<AccordionGroup>
  <Accordion title="What is the difference between a Project, an Application, and an Environment?">
    A **project** is the site that you're working on. Each project can contain multiple **applications** and be deployed in multiple **environments**. An environment is a standalone copy of your site, including apps, databases, storage, data, and all other services. By default, `main` branch is the production environment, while all other branches can be set up as identical copies of the prod environment for testing purposes.
  </Accordion>

  <Accordion title="How does Qovery manage databases?">
    Qovery provides `managed` and `container` modes for your databases. Basically, `managed` mode relies on the managed database provided by the cloud provider. E.g. if you choose `Postgres` with the `managed` mode while your environment is running on AWS, then Qovery provides an [AWS RDS](https://aws.amazon.com/rds) instance. Please check out our [database section](/configuration/database) for further details.
  </Accordion>

  <Accordion title="Does Qovery replace Kubernetes?">
    Behind the scene, Qovery uses [Kubernetes](https://kubernetes.io/). Qovery extends Kubernetes to make it accessible to any developer teams.

    **Important**: Qovery does not modify Kubernetes. It only deploys his services in a `qovery` Kubernetes namespace.
  </Accordion>

  <Accordion title="Does Qovery support mono repository?">
    Yes, absolutely! Check out our monorepo guide.
  </Accordion>

  <Accordion title="Does Qovery support microservices?">
    Yes, absolutely! Check out our microservices guide.
  </Accordion>

  <Accordion title="What Git providers do you support?">
    GitHub, GitLab, BitBucket.
  </Accordion>

  <Accordion title="Do you support GitHub Enterprise or Gitlab Self-hosted?">
    Not at the moment, but you can upvote for this feature in [our roadmap](https://roadmap.qovery.com/roadmap).
  </Accordion>

  <Accordion title="Does Qovery support private Git repository?">
    Yes, absolutely!
  </Accordion>

  <Accordion title="Which IP address does my cluster use to communicate externally over the Internet?">
    There isn't just one public cluster IP adress dedicated to external communication. However, worker nodes inside your cluster each have a public IP automatically attached to them. You can view those default public IPs in the details of your worker nodes (EC2 instances for AWS users) which belong to the node group in your cluster.

    For improved security and control, the `Static IP` feature allows you to ensure that outbound traffic from your cluster uses specific IP addresses. For more information on the `Static IP` feature and how to enable it at cluster creation, see [Static IP on AWS](/configuration/clusters#static-ip) or [Static IP on GCP](/configuration/clusters#static-ip).
  </Accordion>

  <Accordion title="If I have N custom domains under the same root domain, do I need to create N CNAME records, or just creating one for the root domain is enough?">
    You have to create N CNAME, one per custom domain.
  </Accordion>

  <Accordion title="How do you support new Kubernetes version?">
    The Qovery team manages your Kubernetes cluster's upgrade, and you don't have to think about it. Upgrades from one minor Kubernetes version to another require a good amount of tests to make sure everything goes smoothly with zero interruptions for your app. This is why Qovery always provides 1 or 2 minor versions below the last one offered by the cloud provider. Our goal is to guarantee you the maximum uptime.

    More details on this dedicated section: [how does Qovery handle Kubernetes version upgrades](/configuration/clusters#how-does-qovery-handle-kubernetes-version-upgrades).
  </Accordion>

  <Accordion title="Can I upgrade my cluster myself?">
    NO and you SHOULDN'T!

    More details on this dedicated section: [how does Qovery handle Kubernetes version upgrades](/configuration/clusters#how-does-qovery-handle-kubernetes-version-upgrades).
  </Accordion>

  <Accordion title="Can I have access to my Kubernetes cluster?">
    Absolutely, you can follow this guide to connect to your cluster with kubectl.
  </Accordion>

  <Accordion title="Can I have access to my application with a shell?">
    Absolutely, you can connect directly to your application with a shell by clicking on the Qovery cloud shell button:

    <img src="https://mintcdn.com/qovery/h4GYArJsH08SmRTF/images/qovery_cloud_shell.png?fit=max&auto=format&n=h4GYArJsH08SmRTF&q=85&s=e137def9461f38c4ab8554a775b4fad7" alt="Qovery Cloud Shell" width="3164" height="2070" data-path="images/qovery_cloud_shell.png" />

    Then you just have to select the pod and the container.

    You can also check out our [CLI](/guides/qovery-101/provision#qovery-cli) and the `qovery shell` command.
  </Accordion>

  <Accordion title="How application auto-scaling works?">
    Take a look at [our application documentation](/configuration/application#auto-scaling).
  </Accordion>

  <Accordion title="Why you should use Qovery?">
    ### The power of Kubernetes

    Under the hood, Qovery uses **containers** and **Kubernetes** to run applications. With us, your applications scale accordingly to your traffic and needs. We rely on major cloud providers to provide reliable infrastructure to make your applications highly available.

    ### Reliable infrastructure

    What's more, we took on our shoulders the complexity of providing and managing other infrastructure requirements you need (like databases or message brokers), so you can focus merely on developing business features.

    ### Simple and Powerful

    With Qovery, the cloud is simple again. Get all the benefits of using cloud and Kubernetes without dealing with its complexity. You don't need to hire infrastructure experts - configuring continuous integration, deployment, databases, message brokers, storage, DNS, SSL/TLS, VPCs, and many others - we do it all for you. On Qovery, you can spin up a set of microservices, databases, and other cloud services in minutes with a single Git push!

    ### Built for all developers

    Qovery is designed by developers for developers. Our goal is to make your life easier and allow you to move faster. Developer experience is at our heart. Building cloud-native applications was never that fast and simple!

    ### Fully customizable for advanced business use cases

    Create teams, split responsibilities, manage privileges, enforce company-wide rules, deploy to multiple clouds, plug in your own CI solutions. Qovery Business allows you to bring your organization to the next level with ease.
  </Accordion>

  <Accordion title="How Qovery works under the hood?">
    [Here](/basic-concepts) is a detailed explanation on how Qovery works under the hood.
  </Accordion>

  <Accordion title="How can I contact you?">
    Contact us by email at hello (at) qovery.com or via Pylon directly in the Qovery console (existing customers).
  </Accordion>
</AccordionGroup>

## Still Have Questions?

If you can't find an answer to your question:

<CardGroup cols={2}>
  <Card title="Contact Support" icon="headset" href="/getting-started/useful-resources/help-and-support">
    Reach out to our support team
  </Card>

  <Card title="Documentation" icon="book" href="/getting-started/introduction">
    Browse our comprehensive documentation
  </Card>

  <Card title="Roadmap" icon="map" href="https://roadmap.qovery.com/en/roadmap">
    See what features are coming next
  </Card>
</CardGroup>