VPS for a 1C:Enterprise cluster — from €5.49/mo
Build a 1C cluster with replication and load balancing — fast NVMe servers in a private network, 5-hour trial before payment, test the load risk-free
Build a 1C cluster
A VPS setup for a 1C cluster is several virtual servers on which you deploy a 1C:Enterprise server cluster with session distribution and database replication. The minimal working scheme is two nodes — an application server and a database server, 16 GB RAM each, i.e. two Power 1 plans at €17.99/mo joined into a private network. A separate replica node starts at €5.49/mo. A cluster pays off once you pass 30 users or the database grows into tens of gigabytes. A 5-hour trial before payment lets you build a test loop and measure response times. All configurations are in the VPS catalog.
Plans
VPS for a 1C cluster
A cluster node with a small database fits on Standard 1 — 4 vCPU, 4 GB RAM, 50 GB NVMe for €5.49/mo. The main 1C server under active load needs Power 1 (10 vCPU, 16 GB, 160 GB NVMe) at €17.99/mo. Resources scale as your user count grows, and the 5-hour trial runs before payment.
Compare all plansStandard 1
| 4 vCPU · AMD EPYC |
| 4 GB RAM |
| 50 GB NVMe |
| Unlimited traffic |
| 1× IPv4 · KVM |
| 24/7 support |
Standard 2
| 4 vCPU · AMD EPYC |
| 6 GB RAM |
| 60 GB NVMe |
| Unlimited traffic |
| 1× IPv4 · KVM |
| 24/7 support |
Load balancing
Distribute 1C worker processes across cluster nodes — user sessions spread evenly between the servers.
Database replication
Keep a standby replica of the 1C database on a separate node to switch over quickly if the primary server fails.
Resources sized for 1C
Dedicated vCPU, NVMe storage and RAM headroom for the database server and 1C:Enterprise worker processes.
How to deploy a 1C cluster
Choose plans and an image
Order the number of servers you need for the cluster nodes and select a Windows Server or Linux image in the control panel.
Install the OS yourself
Via the panel and the KVM console you install the OS on each node yourself and prepare the network between the servers.
Configure the 1C cluster
Connect via the KVM console, RDP or SSH, install the 1C:Enterprise server and the database engine, bring up the cluster and replication.
We will help design the cluster
We will suggest how to split the roles between nodes — the database server, 1C worker processes and the database replica — for your number of concurrent users.
We will help with the network setup between the servers and a backup scheme for the 1C databases — node snapshots you take yourself in the panel. If a cluster is overkill, start with the VPS for 1C:Accounting; ongoing node maintenance is handled by our engineers under 1C cluster administration.
Discuss the projectFrequently asked questions
Didn't find your answer?
Write to us via the contact page.
At least two VPS: a 1C:Enterprise application server and a database server, joined into a private network. With 16 GB RAM each that is two Power 1 plans at €17.99/mo. The database replica goes on a third node.
Yes, if the nodes are spread across sites. We build a distributed fault-tolerant cluster across several data centers: if one site fails, the other picks up the sessions. A single server cannot offer that.
You choose a Windows Server or Linux image and install the OS on each node yourself via the control panel and the KVM console.
Yes, every server comes with a KVM console — hardware-level access for installing or reinstalling the OS and for emergency management, in addition to RDP and SSH.
For the database node take Power 1 — 10 vCPU, 16 GB RAM, 160 GB NVMe at €17.99/mo — or higher: the database is bound by memory and disk. A replica node is usually fine on Standard 3 at €8.99/mo.
We will advise on splitting the roles between nodes and on the network setup between servers. The 1C installation and licenses remain on your side or with your specialist.
When you have more than 30 users, the database has grown into tens of gigabytes, or you need fault tolerance: if one worker process dies, sessions move to another.
PostgreSQL in the 1C-ready build has no license fees and covers most scenarios. MS SQL is chosen when your contractor requires it or the licenses are already paid for. Both run on our servers.