Cloud server for M.E.Doc

It depends entirely on how it is deployed, and the vendor publishes the numbers, so take them rather than ours. For the local version - one person working in M.E.Doc on their own remote desktop - M.E.Doc asks for a processor from 2 GHz, from 2 GB of RAM and from 1.5 GB of free disk. For a terminal server, where several people are in the same Windows desktop at once, the vendor gives a formula: RAM = active users x 2 GB + 4 GB for the system, plus 1.5 GB for every automatic processing module you run, and CPU = 4 + active users. So four people sharing one desktop works out at 12 GB of RAM and 8 cores, not the entry size on this page. The vendor supports FireBird up to a 100 GB database file and recommends moving to Oracle above that. Checked against M.E.Doc official technical requirements in September 2026

Yes, and it is the common case: one Windows machine, one backup schedule, the ledger and the e-reporting side by side. Size the two independently and add them up - M.E.Doc publishes its own requirements, BAS has its own, and neither figure covers the other. The calculator is where that total turns into a price, because a machine carrying both is usually past the packages on this page. If the two need separating for access reasons, the accounting server page sizes the ledger on its own, and the remote office page is the one to read if a whole team needs to be inside the same desktop all day

You or your integrator. We hand over a Windows server with administrator access, the OS image and the backup; the application, its licence and the reporting setup stay on your side. We sell the infrastructure underneath M.E.Doc, not the application or support for it

They stay yours. We do not hold, escrow or install signature keys, and nobody at DCXV needs access to them to run the server. You restore them onto the machine the same way you would onto any other Windows computer

One weekly backup is in the price of every plan, snapshots roll the machine back in two clicks, and daily retention up to seven days is available. Take a snapshot before a reporting run rather than after one goes wrong - that is the cheapest insurance on this page

Yes, but that is Remote Desktop Services rather than administrative access. Windows Server includes two administrative sessions; beyond that each person needs an RDS user CAL, sold in the configurator and installed by an engineer within three days. If the whole team is meant to work inside one Windows desktop all day, the remote office page is sized for exactly that

Export the database and collect the key files from the machine it runs on now, before anything else changes. We deploy the Windows server in under ten minutes, you or your integrator install M.E.Doc with your licence and restore the data, then you file one real report from the new machine while the old one is still available. Cut over after that, not before a deadline

That is the point of moving it. The server sits in a Tier III data centre with redundant power and a 99.982% facility SLA, so the deadline depends on your internet connection and a device to connect from rather than on the office building