# Placement Groups

Placement Groups let you control how your servers (virtual machines) are physically placed on the underlying hardware in Neevcloud's infrastructure. This gives you the ability to optimize for either **performance** or **high availability**, depending on your workload.

### Overview

By default, when you create servers on Neevcloud, the platform decides which physical host to place them on. With Placement Groups, you define the rules — whether servers should be packed together on the same host, or spread across different hosts.

This is especially useful for:

* Database clusters that need low-latency communication between nodes
* Web application replicas that must survive a hardware failure
* Distributed systems like Kafka, Cassandra, or HDFS that need partition-awareness
* Production workloads where you need predictable infrastructure behaviour

### Locations

Neevcloud Placement Groups are **region-specific**. When creating a group, choose the region where your servers are (or will be) deployed:

* **Mumbai**
* **Central India**

{% hint style="warning" %}
A placement group created in Mumbai cannot include servers in Central India, and vice versa.
{% endhint %}

### Rules and Limitations

* A server can belong to only **one Placement Group** at a time
* Placement Groups are **region-scoped** and cannot span Mumbai and Central India
* You **cannot move** a running server into or out of a Placement Group — you must create a new server and assign it at launch
* Placement Groups are **free** — you are only charged for the servers inside them
* Deleting a Placement Group **does not delete** its member servers