Own data centers / TIER III
Engineering infrastructure designed for stable operation of critical services and project growth.
GIT.ru
General iT colocation
Colocation
Your servers.
Our infrastructure.
Colocate servers and network equipment in a professional data center. We arrange power, connectivity, cooling, physical access and service.
Start with a single server or a full rack. We agree on the facility, capacity and terms for your project.
Key advantages
Key advantages
Equipment insurance up to 500 million RUB
Additional protection for businesses that need financial predictability and risk control.
Connectivity up to 100 Gbit
High bandwidth for services with intensive network traffic and redundant designs.
COLOCATION PRICING
Placement pricing
Krasnodar
ColocationHosting a 1U serverfrom 9,900 RUB
Hosting a 2U serverfrom 18,900 RUB
1U Network Equipmentfrom 3,500 RUB
42U server rack, 10KWfrom 249,000 RUB
Server placement price conditions:
- No more than 2 CPUs up to 130W each;
- No additional GPU devices;
- In all other cases, terms are calculated individually upon request.
Moscow
ColocationHosting a 1U serverfrom 8,900 RUB
Hosting a 2U serverfrom 12,900 RUB
1U Network Equipmentfrom 2,500 RUB
42U server rack, 5KWfrom 190,000 RUB
Server placement price conditions:
- No more than 2 CPUs up to 130W each;
- No additional GPU devices;
- In all other cases, terms are calculated individually upon request.
Novosibirsk
The facility is being prepared for launch. Send a request and we will notify you when colocation starts and prepare preliminary terms for your project.
Discuss placementSaint-Petersburg
The facility is being prepared for launch. Send a request and we will notify you when colocation starts and prepare preliminary terms for your project.
Discuss placementINSIDE THE DATA CENTER
A carefully planned home for every server.
From rack installation to remote access. We plan power, connectivity and service around your hardware.
Schematic model. Hardware and connection details are agreed for your project.
BEYOND THE SERVER CHASSIS
Everything your hardware needs to operate.
One facility for power, connectivity and service. We agree on the details before installation so deployment follows a clear plan.
01
Power for your workload
We calculate consumption and agree on power capacity and connections, including the number of power supplies and redundancy requirements.
- Agreed power capacity
- Organised rack cabling
- Cooling for the installed equipment
02
Connectivity with room to grow
We size connectivity for your service traffic and plan connections for servers, switches and routers, including network redundancy.
03
Service without extra trips
We arrange iLO or IPMI access when supported by the equipment. Physical tasks are handled through agreed engineer assistance and facility access procedures.
FROM REQUEST TO CONNECTION
A clear plan for moving to a data center.
Tell us what you need to colocate. We then agree on the terms, equipment handover and launch.
Plan colocation- 01
Review the equipment
Type, size, power, network ports and access requirements.
- 02
Agree on the terms
Facility, connection plan, pricing and service procedures.
- 03
Receive and install
Plan delivery, rack installation and cabling.
- 04
Check the connections
Check power and networking, then arrange access and ongoing service.
About data centers
About data centers
The facility is selected according to power, network design, hardware access and additional service requirements. For projects with special requirements, we agree on procedures, allowed load and support scenarios in advance.
- unit placement and full racks
- remote hands and scheduled works
- individual network design
FAQ
Colocation is the placement of a company’s own server or network equipment in a professional data center. The customer keeps control over the hardware, while the provider supplies the infrastructure: rack space, power, cooling, network connectivity, physical security, and additional services.
This model is useful when the hardware is already owned or a specific configuration is required, but maintaining an in-house server room is too costly, risky, or difficult to manage.
A colocation service should be ordered from a provider that can not only host the server in a data center, but also help calculate power, network bandwidth, IP addresses, remote access, and additional services. Before ordering, it is important to define the placement format: 1U, several rack units, part of a rack, or a full rack.
You should also clarify power requirements, equipment depth, ports, uplink speed, DDoS protection, and remote hands work in advance.
Colocation in a data center means that a customer’s server or network equipment is placed at a data center facility instead of an office server room. The data center provides the conditions required for stable operation: controlled power, cooling, network infrastructure, restricted physical access, and monitoring.
At the same time, operating system configuration, applications, databases, and backups usually remain the customer’s responsibility or are provided as separate managed services.
Server colocation is suitable for companies that already own hardware or have specific hardware requirements. Typical scenarios include corporate systems, databases, 1C, CRM, network nodes, storage systems, disaster recovery sites, or projects where control over the exact hardware configuration is important.
Colocation is especially useful when a company wants to keep ownership of the server but move it from an office to a more reliable environment with power, cooling, and network connectivity.
The difference is that with colocation the hardware belongs to the customer, while the provider hosts it in the data center infrastructure. With dedicated server rental, the physical server usually belongs to the provider, and the customer rents a ready-made configuration for a selected period.
If standard server capacity is needed without purchasing hardware, a dedicated server may be easier. If you already own hardware, licenses, special disks, controllers, or network requirements, colocation may be more suitable.
Colocation differs from VPS/VDS and cloud servers because the customer uses their own physical hardware. VPS/VDS and cloud services provide virtual resources on the provider’s infrastructure, while with colocation the server, drives, controllers, and network cards belong to the customer.
This gives more control over the hardware, but also requires responsibility for its condition, compatibility, component replacement, operating system, applications, and data unless another model is agreed in the contract.
Colocation differs from an in-house server room because the equipment remains yours but is hosted in a professional data center. You do not need to build your own room, cooling, redundant power, fire safety, access control, and carrier connectivity.
At the same time, the company keeps control over the server and can use its own hardware configuration. This approach is often chosen when an office server room no longer meets reliability, security, or scalability requirements.
A colocation service usually includes rack space for equipment, power, cooling, network connectivity, physical security at the facility, and access to additional services. The exact package depends on the selected format: a single server, several rack units, part of a rack, or a custom configuration.
Additional options may include IP addresses, higher bandwidth, DDoS protection, remote hands, monitoring, backup, and server environment administration.
Colocation pricing depends on rack space, power consumption, the number of network ports, bandwidth, IP addresses, redundancy level, and additional services. The final cost may also be affected by remote hands, monitoring, DDoS protection, backup, and administration requirements.
That is why pricing should be calculated not only by the number of rack units, but also by actual power usage, network load, access requirements, and future infrastructure growth plans.
Rack space is selected based on the equipment size, depth, weight, mounting type, power consumption, and cabling requirements. A single server often requires 1U or 2U, while storage systems, network devices, or several servers may need more space.
Before placement, it is important to check whether the chassis fits the rack, whether proper rails are available, how many ports and cables are required, and whether the equipment stays within power and heat limits.
A rack unit is a standard unit of height in a server rack that helps calculate how much equipment can be placed in a data center. One rack unit is marked as 1U and corresponds to the height of standard rack-mounted equipment. The taller the server chassis, the more rack units it occupies.
This parameter affects cost, rack planning, power, cooling, and future expansion. A wrong size estimate may complicate installation or require a different placement format.
Power for a server in a data center is calculated based on actual or declared equipment consumption, including power supplies, workload, redundancy, and possible growth. It is important to consider not only the rated power, but also the real operating mode: databases, disk arrays, and high-load services may consume more energy.
Before placement, you should prepare details about the server model, power supplies, peak consumption, and requirements for one or two power feeds.
Redundant power and cooling reduce the risk of equipment downtime caused by infrastructure issues. Servers in a data center operate continuously, so power, UPS systems, generators, air conditioning, and airflow must be designed for round-the-clock load.
This does not remove the need for monitoring, backups, and proper system architecture, but it helps provide more stable operating conditions than a typical office server room.
The internet uplink for server colocation is selected according to the workload: websites, corporate systems, APIs, disaster recovery sites, and network services may require different bandwidth. It is important to consider not only peak speed, but also stability, latency, traffic volume, redundancy, and IP address requirements.
If the project serves users from different regions, user geography, traffic type, and the need for protection against network attacks should be assessed in advance.
IP addresses are usually needed when the server must be accessible from the internet, accept connections, host websites, email, VPN, APIs, or corporate services. The number of addresses depends on the project architecture, network requirements, separate services, and security rules.
Before ordering colocation, it is important to understand how many public IP addresses are required now and whether extra capacity will be needed for future services, load balancing, administration, or environment separation.
Remote hands are on-site data center assistance with physical actions on equipment. For example, a technician can reboot a server, check indicators, connect a cable, install components, replace a drive, or perform a visual inspection based on an agreed request.
This service is useful when the equipment is hosted in a data center and the customer’s engineer cannot quickly visit the facility. The list of available tasks and response times should be clarified in advance.
KVM access is useful when the server needs to be managed at a low level: viewing the boot screen, changing BIOS/UEFI settings, installing an operating system, diagnosing errors, or restoring access when normal network connectivity is unavailable. For critical systems, this can significantly speed up maintenance.
However, the format of KVM or out-of-band access depends on the hardware and facility conditions. It should be clarified before placement.
Physical security in a data center is provided through a set of measures: access control, visitor procedures, video surveillance, restricted rack access, and equipment handling regulations. This reduces the risk of unauthorized access to servers and network devices.
However, project security is not limited to physical protection. The operating system, firewall, access rights, passwords, updates, backups, and monitoring must also be configured properly to reduce technical and operational risks.
DDoS protection, monitoring, and backups are often needed for projects where service availability and data integrity are important. DDoS protection helps reduce the impact of network attacks, monitoring helps detect issues faster, and backups provide a recovery option after an error, failure, or data corruption.
These tools do not eliminate all risks, but they improve infrastructure resilience. For critical systems, they should be planned in advance rather than after the first incident.
In colocation, responsibilities are usually divided: the data center is responsible for the agreed facility infrastructure and services, while the customer is responsible for their hardware, operating system, applications, and data. If administration, component replacement, diagnostics, or on-site maintenance are needed, these should be agreed separately with the provider.
This division should be clarified before placement so everyone understands who reacts to hardware failures, controls backups, updates the system, and makes decisions during incidents.
Before placing a server in a data center, you should check its dimensions, rails, power, drive condition, network interfaces, access credentials, labeling, completeness, and rack compatibility. It is also important to prepare backups, a migration plan, DNS settings, IP addresses, a connection scheme, and a list of responsible contacts.
This preparation reduces installation delays and helps launch the equipment faster after it is mounted in the data center.
A specialist can help choose colocation, network connectivity, and additional services by assessing the equipment, power consumption, network load, availability requirements, security, and maintenance needs. This approach helps avoid focusing only on the price per rack unit and instead calculate a practical configuration for real business tasks.
Through GIT.ru, customers can select a placement format, agree on power, IP addresses, uplink, DDoS protection, monitoring, remote hands, and infrastructure support.
Colocation request
Обсудить размещение оборудования
Fill in the form — a General iT engineer will contact you and clarify the placement requirements.