• Thread Author
Mac users no longer need to buy a Windows laptop or accept crippled workarounds to run the Czech accounting system POHODA — hosting the app in the cloud and accessing it via a Windows desktop session delivers the full, native POHODA experience on macOS, iPadOS, and virtually any internet‑connected device.

Background / Overview​

POHODA is distributed in multiple variants — POHODA, POHODA SQL, and POHODA E1 — and the vendor explicitly documents hosting options so the application can be run remotely from a server instead of being installed on each workstation. This hosted approach preserves every feature of the desktop application while removing the need to manage on‑premise servers.
Cloud hosting vendors in the Czech Republic and broader Europe offer managed POHODA installations where the software is already preinstalled on Windows servers in professional data centers; users then connect from their Mac using a Remote Desktop client (or the newer Windows App), which streams the full Windows desktop — including POHODA — to the Mac. Several specialized providers (CZCLOUD, ARDin, iPodnik and others) advertise this exact workflow and highlight benefits like backups, SLA guarantees, and VPN access. (czcloud.cz, ardin.cz)

How the cloud-hosted POHODA model works​

The architecture in plain terms​

  • A Windows server (virtual machine) in a secure data center hosts the installed POHODA application and stores the accounting database centrally.
  • Your Mac runs a remote client (Microsoft’s Windows App or Remote Desktop client) that connects to that server and displays the Windows desktop in a window or fullscreen mode. From your point of view, POHODA behaves exactly as if it were running locally. (theverge.com, learn.microsoft.com)
  • The hosting provider manages the Windows OS, hardware redundancy, backups, patching, and optionally the POHODA license and updates — you pay a monthly fee for access and computing resources.

Editions and compatibility​

All common POHODA editions are supported in cloud deployments, including the single‑user MDB edition through to the multi‑user POHODA SQL and the larger POHODA E1 information system. Hosting providers explicitly state compatibility across these product lines and with common POHODA add‑ons. (stormware.cz, pohodaplus.cz)

Why this is usually the best option for Mac users​

  • No local Windows installation required — eliminates Boot Camp, local VMs, or dual‑boot complexity.
  • Full feature parity — hosted POHODA runs the exact same Windows binaries as an on‑PC installation, so no functionality is lost.
  • Scalability — CPU, RAM, storage, and concurrent users can be increased or decreased by the host as your company grows.
  • Centralized backups and disaster recovery — data is stored in managed datacenters with backup procedures and geographic redundancy options.
  • Works on iPad and other mobile devices — remote desktop clients and the Windows App let you open POHODA from tablets where a local Windows install would be impossible.

The step‑by‑step: how to start POHODA on a Mac (practical guide)​

  • Pick a hosting vendor that supports POHODA (examples: CZCLOUD, iPodnik, ARDin, others). Ask whether they will host your POHODA edition and whether migration of existing data is included. Many providers offer trial periods or setup assistance. (czcloud.cz, pohodaplus.cz)
  • Decide licensing: will you bring your existing POHODA license or ask the host to include licensing in the package? Clarify if the vendor will manage POHODA updates.
  • Confirm server sizing and concurrency: set the number of simultaneous users, storage quota, and CPU/RAM profile. This affects costs and responsiveness during peak accounting periods.
  • Ask about security features: VPN, RD Gateway or equivalent, multi‑factor authentication (MFA), and backup cadence. Insist on data center certifications and an SLA. (ardin.cz, adminbyrequest.com)
  • Receive connection details from the host: server address, username, password, and any VPN credentials or workspace feed URL. Hosts typically provide Windows user accounts and an initial password.
  • On your Mac, install the client:
  • Prefer the new Windows App or the Microsoft Remote Desktop client available via the Mac App Store. The Windows App consolidates connections to Windows 365, Azure Virtual Desktop and RDP resources and is now recommended for macOS. (theverge.com, learn.microsoft.com)
  • (Optional but recommended) Connect to your provider’s VPN first for an additional encrypted tunnel. Then use the Remote Desktop client or Windows App to create a saved connection and log in.
  • Once connected you’ll see the Windows desktop with POHODA open (or you can launch POHODA from the hosted Start menu). Adjust display scaling, map printers, and enable clipboard/file redirection according to the host’s instructions.

Security and compliance: what to insist on​

Using Remote Desktop to access a server across the internet is common — but it must be done securely. Do not accept an exposed RDP port and minimal controls.
  • Use VPN or an RD Gateway: avoid exposing RDP (TCP 3389) directly to the Internet. VPN or RD Gateway acts as a protected broker and reduces brute‑force exposure. (monovm.com, adminbyrequest.com)
  • Require Network Level Authentication (NLA) and strong passwords: NLA prevents unauthenticated session initiation and reduces attack surface.
  • Enforce Multi‑Factor Authentication (MFA): MFA dramatically reduces successful account takeover risk; ask your host if they support MFA for remote sessions.
  • IP whitelisting and firewall rules: restrict access to known office IPs or your VPN endpoint where feasible.
  • Logging, monitoring and backup verification: insists on 24/7 monitoring, retained access logs, and periodic restore tests so you know backups actually work.
Be aware that RDP exploits and brute‑force attacks are real; best practice is layered defense (VPN + NLA + MFA + logs). Security guides and vendor documentation make these same recommendations. (cloudzy.com, adminbyrequest.com)

Licensing and legal checklist — don’t overlook RDS CALs and Office licensing​

Remote Desktop Services (RDS) licensing is a frequent surprise. If the host uses a Windows Server session host to provide a GUI desktop for you, Windows Server requires Remote Desktop Services Client Access Licenses (RDS CALs) in addition to normal Windows Server licensing. Hosts often include RDS CALs in their pricing, but you need written confirmation. Microsoft’s licensing guidance explains per‑user and per‑device RDS CAL models and the grace periods, and clarifies that desktop virtualization and app streaming have distinct licensing rules. (learn.microsoft.com, microsoft.com)
If you plan to run Microsoft Office inside the hosted Windows session, check Office licensing: the licensing model for Office in a shared RDS environment differs from local installs and often requires separate rights or per‑device licensing. Ask the host for a licensing statement.

Performance tips for a smooth experience​

  • Choose a host with low latency to your location — responsiveness matters more than raw CPU. Ping times under 50 ms noticeably improve interactive feel.
  • Ask whether the provider offers SSD storage and adequate IOPS for your database; database latency affects POHODA responsiveness during reports and exports.
  • Use a wired Ethernet connection or a high‑quality Wi‑Fi link for the Mac; remote desktops are sensitive to unstable wireless.
  • For heavy multiuser environments (many accountants working concurrently) size the SQL edition server with more RAM and CPU cores; hosts can usually resize on demand.

Integration, automation and add‑ons​

Cloud‑hosted POHODA typically supports the same integrations as an on‑premise install: e‑shops, transport/carrier interfaces, electronic invoicing, and scheduled exports. Many hosts also offer additional automation (email workflows, scheduled exports) or permit you to install 3rd‑party add‑ons that run in the hosted environment. Ask for compatibility confirmation before buying.

Alternatives to cloud hosting: local Windows on Mac​

If cloud hosting isn’t suitable, there are two main local options, each with tradeoffs:
  • Parallels Desktop (virtual machine): runs Windows inside macOS and is the easiest local approach on both Intel and Apple silicon Macs. Parallels now officially supports Windows on Apple silicon (Windows for ARM) and offers emulation for legacy x86 VMs, but emulation can be slow and has limitations. Parallels is a strong option for single‑user setups if you want local Windows performance and offline access.
  • Boot Camp (Intel Macs only): historically allowed native Windows installs on Intel Macs, but Boot Camp is not available on Apple silicon and is therefore a poor long‑term choice for new Mac hardware.
For many businesses, cloud hosting beats local VMs on manageability, backups, and multiuser scenarios — but if you need offline access or very low latency for heavy local reporting, Parallels is a legitimate alternative. (lifewire.com, wired.com)

Costs: what to expect​

Monthly hosting costs vary with:
  • Number of simultaneous users
  • Edition of POHODA (MDB vs SQL vs E1)
  • Server size (CPU, RAM, SSD storage)
  • Additional services (managed backups, VPN, SLA level, support, licensing included)
Public listings from specialized vendors show per‑user offerings starting at a modest monthly fee and rising with concurrency and advanced features; ask for a full quote that includes RDS CALs and any POHODA licensing the host may supply. Expect a small business with a handful of users to pay a few hundred to a few thousand CZK / EUR per month depending on included services. Always confirm what is included (migration, backups, SLA, security features). (uzivatel.cz, czcloud.cz)

Practical gotchas and limitations​

  • Some peripheral redirection (e.g., certain USB dongles or specialized fiscal printers) may require extra configuration or not be supported in a hosted session. Confirm with the provider.
  • Performance during end‑of‑period reports depends on server sizing and database tuning; hosts can typically scale resources temporarily for busy windows.
  • If you rely on integrations that expect local IPs or specific network topology, those integrations may need reconfiguration for the hosted environment.
  • Licensing confusion is common: insist on written clarification of RDS CALs and Office licensing for your use case.
If a host promises “no additional licensing costs” be skeptical and ask for exactly which licenses are included and for how long.

Quick checklist before you sign a hosting contract​

  • Does the provider support your specific POHODA edition and add‑ons?
  • Are RDS CALs and Windows Server licensing included? Get it in writing.
  • What is the SLA (uptime guarantee) and backup/restore policy?
  • Which security controls do they provide (VPN, RD Gateway, MFA, NLA, firewalls, logs)? (adminbyrequest.com, monovm.com)
  • Will your local printers and fiscal devices work? Ask for a test session.
  • How quickly can they scale resources during peak workloads?

Final analysis — strengths and risks​

  • Strengths: Cloud‑hosted POHODA restores full functionality to Mac users, centralizes backups and maintenance, scales with business needs, and enables work from anywhere on Mac, iPad, and other devices. Providers and the POHODA vendor explicitly support hosting as an official deployment method. (stormware.cz, czcloud.cz)
  • Risks: Misconfigured RDP exposure, unclear licensing, peripheral compatibility, and performance mis-sizing. These are manageable but must be confirmed before committing to a provider: require written license inclusions, test printing and fiscal devices, and insist on layered security (VPN/RD Gateway + NLA + MFA + logging). (monovm.com, learn.microsoft.com)
If the host follows standard guidance — place servers in certified data centers, provide VPN/RD Gateway access, include RDS CALs, and offer backups with test restores — hosted POHODA is a secure, flexible, and practical solution for Mac‑based accountants and business owners.

Short recommended roadmap for Mac users who want to start today​

  • Choose two hosting vendors and ask for a POHODA hosting trial.
  • Confirm edition compatibility, RDS CAL inclusion, and the host’s security controls in writing. (ardin.cz, learn.microsoft.com)
  • Test a session from your Mac (or iPad) with the Windows App / Remote Desktop client and verify printer and device behavior. (theverge.com, learn.microsoft.com)
  • If satisfied, migrate data during a low‑traffic window and set up MFA + VPN for all users.

Running POHODA on a Mac via the cloud removes the long‑standing friction between macOS preferences and Windows‑only accounting software. With careful vendor selection, proper security controls, and attention to licensing details, this approach delivers the comfort, convenience, and full functionality Mac users have been waiting for — without surrendering control over data or compliance.

Source: Jablíčkář.cz How to start COMFORT on Macu? CloudThis solution will surprise you.