Windows VPS for 1C
A rented server for 1C saves you from the office PC under a desk that nobody updates or backs up. But 1C on a VPS has its own quirks: the software licence is tied to the parameters of the virtual machine, users need both 1C and Windows licences, and core speed matters more than core count. Here is how to put together a 1C server for a small company.
This article is for a company where 1–10 people work in 1C:Accounting, Trade Management or Salary and HR Management and want to move the database from an office computer to a server in a data centre. How the Windows Server licence itself works and how to lock down RDP sign-in is covered in detail in Windows VPS: licensing, RDP and secure sign-in. Here we cover what 1C adds on top.
Three ways to run it
File database and remote desktop. The database sits on the server, the 1C platform is installed there too, and users connect to the server over RDP and work in their own sessions. This is the simplest option: you need nothing besides Windows and 1C. It suits 1–5 users. As the number of people and the size of the database grow, file mode starts to slow down under simultaneous writes, and if the database file is damaged in a crash, everyone is affected at once.
Client-server option. The VPS runs the 1C:Enterprise server and a database server — Microsoft SQL Server or PostgreSQL. Users connect with the thin client or over RDP. This setup handles more users and larger databases, but it needs a 1C server licence, more memory and an administrator who knows how to configure it. Companies usually switch to it when there are more than five people or the database has grown past a few gigabytes.
Publishing on a web server. The database is published through IIS or Apache, and users work in a browser or the thin client over HTTPS, without remote desktop. Then you need no licences for RDP sessions, but not every external data processor or piece of hardware works through the web client. This setup is often combined with RDP for the accountant who needs full access.
1C licences on a virtual server
- Client licences are always required: one per simultaneous connection. In file mode over RDP all users work on one server, and the licences are activated on it.
- A 1C server licence is needed only for the client-server option. For small companies there is the "Server MINI" edition for 5 connections; it still requires client licences.
- A software licence is tied to the machine's parameters: network name, amount of memory, processor and motherboard model, network card. For a virtual server these are the parameters the virtual machine reports. If the host moves the server to a node with a different processor or you reduce memory when changing plans, the licence may stop working.
- Reactivation is done with a spare PIN code: a licence comes with one main and two spare PIN codes. When the spare ones run out, the 1C company issues new PIN codes on request. Adding memory or disk usually does not reset the licence; reducing them does.
A hardware USB key cannot be attached to a virtual server directly, so software licences are used on a VPS. Before renting, ask the host whether the virtual machine's parameters change when it is moved between nodes and when you change plans. If the host promises to keep the processor model and MAC address, licences last for years.
Windows licences for 1C users
Without additional licences, Windows Server allows two people to connect over RDP at the same time, and those connections are intended for administration. If three or more accountants work in 1C through remote desktop, you need the Remote Desktop Session Host role and a licence for each user. From a host this is a monthly RDS SAL, and for a small team it can cost about as much as the server itself. Check its price before ordering.
Another route is a 1C server on Linux. The platform supports the 1C:Enterprise server on Linux with PostgreSQL; then no Windows Server licence is needed, and users work through the thin client. This saves money but requires an administrator familiar with Linux and PostgreSQL.
How much memory and how many cores
According to Microsoft's requirements, Windows Server 2022 itself starts with 2 GB of memory, and for Windows Server 2025 with the desktop experience Microsoft recommends 4 GB. On top of that, each 1C session over RDP takes 300–500 MB on average, and in the client-server option the 1C server and the database server use memory to cache the database. Guidelines for typical configurations:
| Users | Setup | Cores | Memory | Disk |
|---|---|---|---|---|
| 1–2 | File database, RDP | 2 | 4 GB | 60 GB NVMe or more |
| 3–5 | File database, RDP | 4 | 8 GB | 80 GB NVMe or more |
| 5–10 | 1C server and database server, RDP or thin client | 4–8 | 16 GB | 120 GB NVMe or more |
These are starting points, not a rule: heavy configurations such as Integrated Automation and data exchange with a website need more. After a month of use, check the load in Task Manager and, if resources are short, move to a bigger plan, keeping the software licence in mind.
For 1C, core frequency matters more than the number of cores: posting documents and month-end closing run mostly in a single thread. Look for plans with processors from 3 GHz; the selection is VPS with high CPU frequency. Take NVMe disks only: a file database constantly reads and writes in small chunks; more in NVMe or SSD.
What a 1C server costs
According to the accsly catalog as of 1 November 2026, plans in Russian data centres that can run Windows cost the following (the catalog stores prices in roubles; dollar figures are rounded):
- 4 GB of memory: about $16 a month at the middle of the market, a quarter of the plans cheaper than about $12;
- 8 GB: median about $30, a quarter cheaper than about $21;
- 16 GB: median about $66.
Note that some plans include the Windows licence in the price and others add it as an option, which raises the total. RDS licences for users and 1C licences are paid separately. Windows plans in Russia from hosts that invoice legal entities are collected in VPS for 1C; all Windows plans are in VPS with Windows and RDP server.
For 1C the server location is almost always Russia: under Russian law, personal data of employees and counterparties must be stored in databases inside the country, exchanges with banks and electronic document flow work faster, and the company receives the accounting documents it needs from the host. More in How to choose a country for your server.
Database backups
Copies the host makes as disk snapshots protect against a server failure, but not against an accountant who deleted documents a week ago. 1C needs its own backups:
- file database — an export to a .dt file from the Designer or a copy of the 1Cv8.1CD file while nobody is working in the database, for example on a nightly schedule;
- client-server database — a regular dump with the database server's own tools: SQL Server backup or
pg_dumpfor PostgreSQL.
Store the copies off the server and at least once a quarter check that the database can be restored from them. How to set up such copying is described in VPS backups.
Checklist before ordering
- The setup is chosen: file database over RDP, client-server option or publishing on a web server.
- 1C client licences are counted and, if needed, a server licence.
- The price of Windows in the plan is known, and of RDS SALs if there are more than two users.
- The host has confirmed that the virtual machine's parameters do not change when it is moved between nodes.
- Processor from 3 GHz, NVMe disk, memory with headroom according to the table above.
- The server is in Russia, and the host issues invoices and accounting documents to the company.
- RDP sign-in is open only to office and staff addresses, and database backups off the server are set up.