More Musings

WAL

Anthony

Here’s a structured comparison of the in-house server vs cloud-hosted approach for running Sage 50 with 5 users, so you can decide which suits you better:

⸻

  1. Cost

In-House Server

•	Upfront investment in hardware (server, backup drives, UPS, etc.).
•	Ongoing costs for power, maintenance, updates, security, and possibly IT support.
•	One-time software license cost (if perpetual licensing is used).

Cloud Hosting

•	Recurring monthly or annual subscription for hosting, based on specs and usage.
•	Typically lower upfront cost, but higher total cost over time depending on provider.
•	You may still need to pay for Sage 50 licenses separately or bundled.

Verdict: Cloud is cheaper up front, but may cost more over several years. In-house may pay off long term if managed efficiently.

⸻

  1. Performance and Access

In-House Server

•	Usually faster local network performance, particularly for large files or complex reports.
•	Limited to local or VPN access, which may be slower or more complex to set up remotely.

Cloud Hosting

•	Remote access from anywhere, great for hybrid teams or multi-location businesses.
•	Performance depends on internet speed, both for the host and users.
•	Often includes SSD storage and fast CPUs if using a high-end provider.

Verdict: Cloud wins for remote access and flexibility; in-house wins for local speed.

⸻

  1. Reliability and Uptime

In-House Server

•	Power cuts, hardware failures, or local disasters can cause downtime.
•	Requires manual backups and monitoring, unless you’ve automated it.

Cloud Hosting

•	Built-in redundancy, off-site backups, and managed failover options.
•	Usually comes with SLAs (Service Level Agreements) for uptime guarantees.

Verdict: Cloud generally offers better resilience and uptime unless your on-prem setup is very robust.

⸻

  1. Security and Compliance

In-House Server

•	You control the data and its location — useful for compliance or audit purposes.
•	You need to implement security, including firewalls, antivirus, encryption, and regular patching.

Cloud Hosting

•	Professional providers offer end-to-end encryption, multi-factor access, and GDPR-compliant data centres.
•	Trust is placed in the third-party host.

Verdict: Cloud offers enterprise-grade security, but some prefer the control of in-house if they have strong IT support.

⸻

  1. Scalability and Maintenance

In-House Server

•	Scaling up (e.g. adding more users or storage) may require hardware upgrades.
•	All updates, patches, and maintenance fall on you or your IT team.

Cloud Hosting

•	Easily scalable — just upgrade your plan.
•	Hosting provider manages updates and system health.

Verdict: Cloud offers superior flexibility with lower management overhead.

⸻

  1. Sage 50 Compatibility and Behaviour
    • Sage 50 is desktop-based, and multi-user setups require a shared data path.
    • Latency-sensitive: performance can suffer over poor VPN or remote desktop connections.
    • Cloud hosting is best done via Remote Desktop Services (RDS) or a dedicated VM with Sage installed — not just file hosting.

⸻

Recommendation Scenarios

•	Choose In-House if:
•	You have reliable on-site IT support.
•	Your users work from one location.
•	You prefer to control your data physically.
•	You’re making a long-term investment and want to avoid monthly cloud fees.
•	Choose Cloud if:
•	Your team works remotely or from multiple sites.
•	You don’t want to manage servers or backups yourself.
•	You need high uptime, disaster recovery, and scalability.

⸻

If you’d like, I can also help compare specific hosting providers or recommend a hybrid approach (e.g., host Sage on a local terminal server but with secure remote access). Let me know!

Great — let’s go one level deeper and walk through some specific hosting options and a hybrid alternative that can offer the best of both worlds for Sage 50 with 5 users.

⸻

Option 1: Fully Cloud-Hosted Sage 50

Approach

Use a hosted desktop or remote app service, where Sage 50 is installed on a cloud-based Windows server (typically via RDP). Users log in remotely and work as if on a local machine.

Recommended Hosting Providers

Here are reputable options:

  1. Sage Partner Cloud
    • Endorsed by Sage.
    • Works via Microsoft Azure or via approved partners.
    • Managed for Sage 50 specifically.
  2. Sagenext (US/UK)
    • Sage-focused cloud hosting with full support for multi-user access.
    • Monthly per-user pricing (roughly £45–£60 per user per month).
    • Daily backups and optional Office integration.

**3. Accountant Cloud / Quick Cloud / Apps4Rent

•	More general-purpose, still Sage-compatible.
•	Offer custom VM instances with admin access if needed.
•	Good if you need to install third-party tools alongside Sage.

Pros

•	Hosted Sage 50 pre-configured.
•	Accessible from anywhere.
•	Minimal IT maintenance.
•	Built-in backup and disaster recovery.

Cons

•	Subscription-based: recurring fees.
•	Internet access required for all use.
•	Some hosting companies lock you into proprietary access tools.

⸻

Option 2: In-House Server with Secure Remote Access (Hybrid)

Approach

Install Sage 50 on a local Windows Server (or a powerful Windows PC acting as a terminal server). Users connect over the LAN — and remote users access it securely via:

•	Remote Desktop (RDP) with port forwarding (ideally via VPN or reverse proxy like Cloudflare Tunnel)
•	Jump Desktop / AnyDesk / Chrome Remote Desktop to access their in-office desktop
•	Optional: ZeroTier or Tailscale to link devices with secure mesh networking

Hardware Requirements

•	Windows Server or Pro OS
•	SSD storage and 16GB+ RAM
•	Battery backup (UPS)
•	Dynamic DNS if no static IP

Pros

•	Faster performance for local users.
•	Complete data control.
•	One-time hardware cost.
•	Can use older workstations as thin clients.

Cons

•	You are responsible for:
•	Backups
•	Updates
•	Security
•	If remote access is not robustly configured, you risk data loss or downtime.
•	No guaranteed uptime unless you use a managed IT provider.

⸻

Option 3: Hybrid with Virtualisation on NAS

If you have a Synology or QNAP NAS with decent specs (Intel CPU + 16GB RAM), you can:

•	Install Windows VM on the NAS
•	Host Sage 50 and access via RDP
•	Get LAN performance + remote access through VPN or Cloudflare Tunnel

This gives near-cloud convenience with data kept physically in your office.

⸻

Comparative Table Summary

Feature Cloud Hosting In-House Server Hybrid on NAS

Setup Cost Low High Medium

Running Cost Recurring Low (after setup) Low

Performance Depends on internet Excellent on LAN Good

Remote Access Built-in Needs config (VPN/RDP) Easy with NAS tunneling

Maintenance Minimal Needs local IT skills Some IT knowledge needed

Data Control Low Full Full

Scalability Very easy Hardware-bound Upgradeable via NAS

⸻

My Recommendation Based on Your Setup

Given:

•	You’re tech-savvy and value control
•	You may want to keep costs low over time
•	You prefer not to rely on SaaS lock-in

A hybrid approach using a Windows terminal server or NAS-hosted VM + Cloudflare Tunnel for remote access is ideal.

You get:

•	Local speed for office use
•	Remote access without VPN complexity
•	Minimal monthly cost
•	Full control of data and backups

⸻

Would you like help:

•	Designing the in-house setup?
•	Getting a VPN or remote access system configured?
•	Evaluating a specific hosting quote?

Let me know your current infrastructure or preferences and I’ll tailor a solution.

Excellent. Since nothing is in place yet, let’s design a complete, secure, and cost-efficient Sage 50 system for 5 users, starting from scratch. I’ll guide you through a hybrid setup with in-house hosting and remote access using Cloudflare Tunnel — no need to expose open ports or rely on expensive VPN setups.

⸻

System Design Overview

We’ll set up:

1.	A dedicated in-house Windows server or PC
2.	Shared Sage 50 multi-user environment
3.	Remote access using RDP secured by Cloudflare Tunnel
4.	Local + cloud backup strategy
5.	Optional extras: printer sharing, Office integration, scheduled reboot/updates

⸻

Step-by-Step Build Plan

  1. Hardware Recommendations (In-House Server)

You can use a Windows 10/11 Pro PC or better yet, a Windows Server 2019/2022 machine.

Minimum Spec (for 5 concurrent users):

•	CPU: Intel i5/i7 or Xeon (quad-core+)
•	RAM: 16–32 GB
•	Disk: 500 GB+ SSD (Crucial MX500 or Samsung 870 recommended)
•	Network: Gigabit LAN
•	Monitor + UPS battery backup

Optional: Use a Synology NAS or another PC as an automated backup destination.

⸻

  1. Windows & Sage Setup

a. Base Setup

•	Install Windows Server or Windows Pro
•	Join all workstations to the same workgroup or domain
•	Enable RDP (Remote Desktop) on the server

b. Sage 50 Installation

•	Purchase Sage 50 with 5-user licence
•	Install Sage 50 on server
•	Set up Sage data in a shared folder (with permissions for all 5 users)
•	Configure Sage user access per login

c. Windows Accounts

•	Create 5 named user accounts on the server, one for each person
•	Each user will log in via RDP and run Sage 50 as if locally

⸻

  1. Remote Access with Cloudflare Tunnel (Free and Secure)

You do not need to open router ports or use a VPN.

a. Requirements

•	Cloudflare account (free)
•	A domain name (can be from any registrar)
•	Cloudflare Tunnel (called cloudflared)

b. How It Works

•	Cloudflare connects to your server from the outside
•	Your users open a browser or RDP client and connect securely
•	You control access with Cloudflare Access (can enforce logins, 2FA, IP filtering)

c. Setup Summary

1.	Install cloudflared on your Windows server
2.	Connect it to your Cloudflare domain
3.	Create a subdomain like sage50.yourcompany.com
4.	Set up a tunnel to forward to localhost:3389 (RDP port)
5.	Configure Access Policies for login security
6.	Users log in to Cloudflare and then use Remote Desktop to connect securely

Example Command:

cloudflared tunnel create sage50

cloudflared tunnel route dns sage50 sage50.yourcompany.com

cloudflared tunnel run sage50

⸻

  1. Backups (Local + Cloud)

Local

•	Use built-in Windows Backup or Macrium Reflect
•	Schedule daily image backups to a second disk or NAS

Cloud

•	Use Backblaze B2, Wasabi, or Dropbox for encrypted offsite backups of:
•	Sage data directory
•	Weekly system image (optional)

Tip: Use Duplicati or Veeam Agent Free

⸻

  1. Networking & Security
    • Use strong RDP passwords for each user
    • Set Windows Firewall to block all inbound except localhost
    • Set server to auto-lock when idle
    • Encrypt Sage folder if sensitive data is stored
    • Enable BitLocker if supported
    • Disable USB ports if no local access needed

⸻

Optional Add-Ons

•	Printer Sharing: Share a network printer from the server for report printing.
•	Microsoft 365: For email and Excel integration with Sage.
•	Scheduled Reboot: Weekly auto-reboot for stability.
•	Monitoring: Use uptimerobot.com to alert you if the RDP tunnel goes down.

⸻

Cost Estimate (Initial)

Item Cost (GBP)

Windows 11 Pro / Server 2019 ~£120–£180

PC hardware ~£600–£1000

Sage 50 licence (5 user) ~£1,000–£1,500/year

UPS battery backup ~£80–£150

External backup drive (1TB+) ~£60–£100

Domain name ~£10/year

Cloudflare (free tier) £0

⸻

Would You Like…

1.	A custom PowerShell script to automate parts of this?
2.	Help registering and linking a domain to Cloudflare?
3.	A visual architecture diagram of the whole setup?
4.	Instructions for setting this up on Linux instead of Windows to save money?

Just say the word — I’ll tailor the next step to exactly what you want.

Sage 50 does not run natively on Linux. It is a Windows-only application, designed for use on:

•	Windows 10 or 11 (Pro or Enterprise)
•	Windows Server 2016 / 2019 / 2022

This applies to both Sage 50cloud Accounts (UK) and Sage 50 US Edition (formerly Peachtree). It uses Windows-specific libraries, filesystem paths, and networking mechanisms that don’t work on Linux without emulation.

⸻

But Can You Run Sage 50 on Linux Indirectly?

Yes, with limitations. Here are your options:

  1. Wine (Not Recommended for Sage 50)
    • Wine can run some Windows apps on Linux, but Sage 50 typically does not work reliably under Wine.
    • Complex dependencies, database components, and networked multi-user setups make it fragile or non-functional.
  2. Virtual Machine (Recommended Workaround)

You can run Sage 50 inside a Windows virtual machine (VM) hosted on a Linux server or NAS:

Example:

•	Host: Linux server or Synology NAS
•	VM: Windows 10 or Windows Server with Sage 50 installed
•	Access: Users connect via Remote Desktop (RDP)

This setup works well and gives you:

•	The flexibility and security of Linux
•	Full Sage 50 compatibility inside the VM
  1. Terminal Server / RemoteApp Hybrid

Run Sage 50 on a Windows terminal server, and host the RDP gateway or tunnel on a separate Linux box (such as a Raspberry Pi or VPS). This way:

•	Linux handles remote access and security
•	Windows handles Sage

It keeps costs down while keeping Windows exposure minimal.

⸻

Conclusion

Sage 50 must run on Windows. But with a well-designed setup:

•	You can use Linux as the host for a Windows VM,
•	Or use Linux to handle remote access, security, and backup, while Sage runs on a local Windows machine or VM.

Would you like me to draw up a diagram or write a VM-based setup guide on Linux for you?

Here’s a complete setup guide + diagram for running Sage 50 in a Windows VM on a Linux host, with full multi-user remote access and modern security, using Cloudflare Tunnel for secure access.

⸻

Architecture Overview

      +-------------------------+
      |  User Devices           |
      | (Windows, Mac, etc.)    |
      |   Use RDP or Browser    |
      +------------+------------+
                   |
                   | Secure tunnel (HTTPS / RDP)
                   v
     +-------------+----------------+
     | Cloudflare Tunnel (Free)     |
     | + Cloudflare Access Policy   |
     +-------------+----------------+
                   |
                   v
 +-----------------+------------------+
 | Linux Host Server (e.g. Ubuntu)    |
 | - Proxmox / VirtualBox / QEMU      |
 | - cloudflared tunnel               |
 +-----------------+------------------+
                   |
          +--------+--------+
          | Windows 10/Server|
          | VM with Sage 50  |
          | Shared folder & RDP |
          +------------------+

⸻

Step-by-Step Setup Guide

  1. Prepare Linux Host

You can use:

•	Ubuntu Server or Desktop
•	Debian, CentOS, Rocky, etc.
•	Synology NAS with Virtual Machine Manager

Install:

sudo apt update && sudo apt install qemu-kvm libvirt-daemon-system virt-manager

Enable nested virtualization if needed for performance.

⸻

  1. Install Windows VM

Use virt-manager or proxmox to create a VM:

•	OS: Windows 10 Pro or Windows Server 2019
•	Specs: 4 cores, 16GB RAM, 100GB SSD (expand as needed)
•	Enable RDP in Windows and create 5 user accounts
•	Install Sage 50 in the VM
•	Share Sage data folder for all users (under C:\SageData for example)

⸻

  1. Configure Remote Access

a. Install cloudflared on the Linux host:

curl -L https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64.deb -o cloudflared.deb

sudo dpkg -i cloudflared.deb

b. Authenticate with Cloudflare:

•	Create a Cloudflare account
•	Add your domain (e.g. example.com)
•	Get the Tunnel credentials:

cloudflared tunnel login

cloudflared tunnel create sage50

c. Tunnel config:

/etc/cloudflared/config.yml

tunnel: sage50

credentials-file: /etc/cloudflared/your-sage50-credentials.json

ingress:

  • hostname: sage50.example.com
    service: rdp://localhost:3389
  • service: http_status:404

d. Run the tunnel as a service:

cloudflared service install

sudo systemctl start cloudflared

⸻

  1. Secure Access with Cloudflare Access
    • Go to Cloudflare dashboard → Zero Trust → Access → Applications
    • Add an app:
    • Name: Sage50 RDP
    • URL: rdp://sage50.example.com
    • Add policies:
    • Email domain allowlist (e.g. @yourcompany.com)
    • Enforce login (Google, GitHub, Microsoft, etc.)

⸻

  1. Remote User Workflow

Each user:

1.	Opens browser → logs into Cloudflare Access
2.	Clicks RDP link or uses Remote Desktop to connect to sage50.example.com
3.	Logs into their Windows user account inside the VM
4.	Runs Sage 50 normally

⸻

Benefits of This Setup

Feature Outcome

Cross-platform access Any device with RDP or browser can connect

No ports open Cloudflare Tunnel handles all access

Fully local control Data stays on-premises or on your own hardware

No Windows license bloat Only one Windows VM licence needed

Easily scalable Add RAM/CPU or migrate VM as needed

Backups Use Linux tools (e.g. rsync, Borg, Duplicati) to back up VM or Sage data

⸻

Next Steps

Would you like me to:

•	Provide a cloudflared config file template?
•	Help you write a cloud-init script to install the Linux host from scratch?
•	Recommend a Linux distro or prebuilt image (e.g. Proxmox)?

Let me know how you’d like to start — I can tailor instructions or build scripts for any part of this.