Deploying BAS for accounting, and the hosting provider sends an invoice that says "cloud hosting", and it's unclear whether it's a ready-made service or just a fancy name for a VDS. Sound familiar?

For a business, the difference between these two approaches is not marketing. It's a direct question: who is responsible for updating the platform, where the backups are stored, whether you can fine-tune the server for a non-standard integration, and how much all of this costs after a year or two. Making a mistake at the start means either overpaying for a ready-made environment that doesn't provide the needed flexibility, or taking a VDS and drowning in administration when you just wanted to work with documents.

Below is a breakdown without slogans: what each option really gives you for BAS, what limitations surface after six months of operation, and how to choose based on your task, not the provider's glossy presentation.

💡 Quick overview:

• We examine two approaches to hosting BAS: a cloud environment (a ready-made service managed by the provider) and VDS/VPS (a virtual server under the client's full control)
• We go through the key criteria: deployment speed, data security, customization options, scaling, monthly costs
• We provide a decision matrix: which option fits your business size and accounting specifics

What BAS is and why the hosting choice is not a minor technical detail

BAS (Business Automation Software) is a platform for automating accounting, document management, payroll, and enterprise management. It is built on the "1C:Enterprise" technology stack and is widely used by companies in Ukraine. Unlike boxed 1C, BAS was designed from the start to work in the cloud and on virtual servers.

When you choose hosting for BAS, you are essentially choosing an operating model. Cloud hosting is when the platform is already deployed by the provider, configured, and maintained by them. You get access via a browser or thin client and work. VDS/VPS is when the provider gives you a virtual machine with a clean operating system, and everything else (platform installation, DBMS, security setup, backup) is on you or your system administrator.

All scenarios diverge from this choice: budget, implementation speed, the ability to integrate with non-standard equipment, and the chief accountant's stress level during quarter-end closing.

Cloud hosting for BAS: a ready-made turnkey service

The cloud provider delivers an already deployed BAS environment: the platform is installed, the database is configured, updates come centrally. You pay a monthly fee and don't think about a server disk failing or SQL Server needing a restart. This is the main advantage: operational risks lie with the provider.

Launch speed. You can start working on the day the contract is signed. No need to wait for a system administrator to install Windows Server, configure IIS, and publish the database. The provider gives you a ready-made login URL, and the accountant starts processing source documents right away.

Backup. Automatic, with configurable frequency. In case of a failure, data is restored from a backup from the previous day or even the last hour, depending on the plan. With self-administered VDS, backup regularity often hits the human factor: the administrator forgot, the script failed, the disk ran out of space.

Scaling. If the business grows and 20 concurrent users become 50, the provider increases computing resources without migrating to another server. With classic VDS, such expansion often means moving to a more powerful plan with data transfer and downtime.

The main downside: tight customization limits. You are limited to the set of configurations the provider offers. Need integration with POS software that only works via a COM port? Or a specific application pool setup for a non-standard load? In the cloud, this may be impossible; the provider keeps the environment standardized for stability. An additional risk: data resides on external infrastructure. For companies with strict confidentiality requirements (financial sector, government agencies), this may be unacceptable.

VDS/VPS for BAS: a server tailored to your task

VDS/VPS is a virtual machine with dedicated resources: CPU cores, RAM, disk. You get root access and a clean OS. After that, it's on you: install Windows Server or Linux, deploy the DBMS (most often MS SQL Server for BAS), publish the platform, configure firewalls.

Full control. The main advantage of VDS, for which companies accept the administration costs. You choose the BAS platform version, the SQL Server edition, the IIS application pool configuration yourself. You can set up RDP access for remote employees exactly according to your security policies, not the provider's averaged regulations.

Custom integrations. This is the key scenario for choosing VDS. If the accounting system needs to exchange data with production equipment, a barcode scanner via a COM port, or a legacy system living on the office local network, you can implement this on your own server. In the cloud, such scenarios are either impossible or cost extra for customization.

Confidentiality. All data is on your virtual server. You control encryption, configure access auditing, and decide who connects from where. For businesses that handle customer personal data or trade secrets, this is often the deciding argument.

The main downside: operating cost. The price of the VDS itself is only part of it. Add to that the system administrator's work: installation, configuration, platform updates, monitoring, backups, incident response. For a small company of five people where the accountant is also the admin, this setup quickly becomes a problem.

Comparison table

What to choose: a decision matrix

Cloud is your option if:

• The company is small, up to 15-20 BAS users
• There is no system administrator on staff
• Accounting is standard, without specific modifications and non-standard integrations
• Predictability of monthly costs is important

VDS/VPS is your option if:

• More than 20 users or high transaction intensity
• You have a staff administrator or a reliable contractor
• Integrations with equipment, POS systems, legacy systems are needed
• Industry-specific data hosting requirements apply (finance, medicine)

A practical rule. If you spend more than two business days a month on VDS administration, you are already overpaying compared to the cloud. Calculate your administrator's hourly rate, multiply by the actual time spent, add it to the VDS plan cost, and compare it with the cloud plan for your scale. The numbers are often surprising.

A hybrid scenario. Some companies take the path of "main instance on VDS, test database in the cloud." This provides both control over the production environment and rapid deployment of sandboxes for training new employees or testing updates before applying them to the main server.

There is one more aspect rarely discussed at the selection stage: how the chosen architecture affects BAS performance. The short video below breaks down the difference between cloud and VPS from the perspective of real performance, not marketing slides:

⁉️🤔 Frequent questions

Can BAS be migrated from the cloud to VDS and back?

Yes, technically it's a standard database migration. You export a backup from the cloud environment, deploy it on VDS, and configure publication. The reverse process is similar. The risk is not in the technique but in downtime: migration takes from a couple of hours to a day depending on the database size. Plan the transition for a weekend and be sure to make a full backup before starting.

Who is responsible for updating the BAS platform in the cloud?

The provider. Updates to standard configurations and the technology platform are installed centrally; you receive notification of scheduled maintenance. On VDS, installing updates is your task. If you use a non-standard configuration with modifications, each update on VDS needs to be tested for compatibility; in the cloud, they won't do this for you, but only you can break things with an update.

What is cheaper over a three-year horizon?

For a small business without its own admin, the cloud. The plan includes everything: server, platform, support. VDS looks cheaper in the first month, but add the cost of an administrator's time, at least five hours a month, and the difference disappears. For a mid-sized company with a staff IT specialist, VDS can be more cost-effective, especially if the server is also used for other tasks (email, file storage).

Does the hosting choice affect BAS performance?

Directly. In the cloud, you share resources with the provider's other clients, and performance degradation is possible during peak load hours. On VDS, you get dedicated cores and guaranteed disk performance (IOPS). For BAS with a large volume of documents and concurrent users, VDS on SSD provides noticeably more stable response times.

Is an MS SQL Server license required when using VDS?

It depends on your BAS configuration. Some editions work with PostgreSQL (free), others require MS SQL Server. The cost of an SQL Server Standard Edition license starts at several hundred dollars per year; this needs to be factored into the VDS solution budget. In the cloud, the provider usually includes the license in the plan.

So cloud or VDS: where to start today

The rule of thumb here is simple: start with the cloud if there is no ironclad argument for VDS. During the first month or two of operation, you will see the real load profile, understand which integrations are truly needed, and assess whether the standard environment is sufficient for you. Migrating from the cloud to VDS is a solvable task. But taking a VDS without having an administrator and getting a crashed database in the middle of quarterly reporting is a scenario best avoided.

For companies with 30 or more users and non-standard accounting processes, the answer is almost always VDS. Just budget not only the hosting plan cost but also regular maintenance: monitoring, backups, updates, security audits. And find an administrator who has already deployed BAS, not just someone who "knows Windows." The platform's specifics are such that a generalist admin without experience with 1C-like systems will spend weeks on what a specialist does in a day.