At GMhost we deploy servers for BAS, M.E.Doc, Vchasno, and IT-Enterprise clients almost every week. We size the configuration to the number of accountants and the actual workload, not to marketing tiers like «premium / business». In this guide, we'll walk through how to do this yourself — or at least understand the context before ordering.
Why your office desktop is a lottery
The typical picture: BAS lives on an old HP ProDesk in the corner of the server room. It's been running for five years, nobody remembers the admin password. During month-end close, ten accountants generate reports at the same time, the disk crawls at zero, BAS hangs for half an hour. If a power supply dies on the same day, you've got a week of failover work and the risk of losing a day's work.
A server in a data center solves several problems at once: separate hardware with ECC memory and redundant power, regular controlled backups, a Ukraine-based location with the right legal status for processing taxpayers' personal data.
What BAS actually needs
BAS is a fork of 1C Enterprise, so the workload profile is similar: many small transactions to the database, CPU-bound during recalculations (closes, consolidations, summary reports), sensitive to disk latency. Plus simultaneous work by dozens of users via RDP — you need cores and RAM to spare.
The configurations we deploy in our DCs:
Team | CPU | RAM | Storage |
|---|---|---|---|
5-10 accountants | 2 × Intel Xeon Gold 6138 (20 cores) | 64 GB DDR4 ECC | NVMe 1 TB |
15-30 accountants | 2 × Intel Xeon Gold 6230 (Cascade Lake, 20 cores) | 128 GB DDR4 ECC | NVMe 2×1 TB mirror |
50+ with heavy reports | 2 × Xeon Platinum 8163 (48 cores total) | 256 GB DDR4 ECC | NVMe RAID-10 |
BAS loves RAM more than customers expect. MS SQL (or PostgreSQL in newer releases) caches working tables — give it 128 GB and the month-end close drops from 40 minutes to 7. The RAM pays for itself in a single reporting cycle.
NVMe instead of SATA SSD is critical for random IOPS. SATA SSD works too, but the close will be 1.5-2× slower. ECC memory is mandatory: an accounting database that picked up a single-bit error in memory and wrote it to disk doesn't show the problem right away — and a two-week-old backup recovery can cost you days of work.
M.E.Doc, Vchasno, IT-Enterprise — on the same server as BAS?
Yes, a perfectly normal scenario. M.E.Doc is lighter — 2-4 GB RAM and a couple of cores will do; Vchasno and IT-Enterprise are about the same. When everything sits on one server, the key thing is to budget RAM with the assumption that BAS during peak recalculations can grab almost all of it. Keeping them separate makes sense only when you have 50+ users and a heavy M.E.Doc aggregator module that processes digital signatures for 8 hours a day.
RDP terminal server — the standard architecture
Most clients want one thing: accountants log in via remote desktop, don't drag local copies of the database around, work in a shared environment. That's a terminal server — Windows Server with CAL licenses for each user, profiles moved to a separate disk, access via a corporate VPN.
A few details that often get missed:
-Windows Server + CAL licenses — official, via Volume Licensing through a partner. No «temporary activation keys»: a tax inspection complaining about unlicensed software is no fun.
-Corporate VPN to the server — so RDP isn't sitting on the open internet. WireGuard on the same server or a separate VPS node. Protects against brute-forcing and L7 attacks.
-User profiles on a separate disk from the system disk. Makes backups easier, speeds up logins.
Ukrainian DC — required or recommended?
All servers for the accounting stack we run in Ukrainian GMhost data centers. This matters not for patriotic reasons, but for three very practical ones:
-Taxpayer data — in Ukraine. Fewer questions from regulators, easier to respond to requests from the Personal Data Protection Service.
-Latency. From Kyiv to our DC — 2-5 ms; from Lviv — 4-6 ms. In a European DC it would be 30-50 ms — and you'll feel that on every click in an RDP session.
-Support in Ukrainian during business hours. The engineer on the call understands «we're in close, BAS exceeded its memory limit» without translation.
Backup — the thing people think about when it's already too late
The standard scheme we deploy:
-Daily automatic backup of BAS folders + SQL dump.
-14-30 days of versioning — you can restore a document from last Friday if an accountant accidentally deleted it.
-Off-site copy in another of our DCs (Estonia / Germany / Portugal) — so losing a site doesn't mean losing data.
-Recovery testing once per quarter — on a real copy, not «eyeballed».
How we move from an office desktop to a server in the DC
The standard zero-downtime procedure:
- Preparation. We provision the server, set up Windows Server, licenses, profiles, shared access — 1-2 business days.
- Test migration. We copy the current BAS dump and database, spin up a parallel working copy. One or two accountants test it side-by-side with production.
- Cutover. Over the weekend — final dump, transfer, control-report verification. On the next workday, the team logs into the new server.
- Safety net. The old server stays in read-only mode for another week — if something's off, we roll back fast.
Overall, a week from «we called you» to a fully working system.
What it costs
The price depends on the number of users and headroom for future growth. Roughly:
-VPS for BAS with 5-10 accountants — starting from a baseline NVMe plan.
-Dedicated server for 15-30 accountants — starting from a starter dedicated plan.
-Dedicated for 50+ with heavy reports — starting from a heavy plan.
Every plan includes a Windows Server + CAL license, RDP setup, a corporate VPN to the server, daily backups with versioning, an off-site copy, 24/7 monitoring, and Ukrainian-language support.
FAQ
How long does migration from an office server take?
Preparing a new server — 1-2 hours.
What if we still run 1C, not BAS?
We work with that. We help you migrate to BAS if a transition is on your roadmap, or we host your existing 1C configuration while you decide. Both scenarios are technically close.
Can we skip RDP and have clients connect directly to the database?
Yes — an option for those who already have a «thick client» BAS on workstations. The server then exposes only SQL and files, and you don't need RDP CAL licenses.
Who handles administration?
Basic administration — our 24/7 support. Accounting-side BAS and M.E.Doc updates — either your visiting IT specialist or us under a separate contract.
Is there a guarantee that data won't be lost?
A three-tier scheme (RAID + local backup + off-site to another DC) and a 99.9% SLA with downtime credits. That's the maximum any serious provider actually offers.
Want a configuration for your team?
Drop us a line at [email protected] or in the bot @gmhost_support_bot — we'll ask the right questions, look at your current setup, and come back with a proposal the same day. If you're under time pressure, we migrate over a single weekend.
