Where to Host Your Acumatica: SaaS, Private Cloud, or On-Premise?

Choosing the right hosting environment for Acumatica is a critical decision that impacts your performance, scalability, and long-term costs. Let’s break down the pros and cons of the three main options: Acumatica SaaS, Partner Hosting, and Self-Hosting (On-Premise).

Option 1: Acumatica SaaS (The Public Cloud)

It sounds perfect: no server maintenance, no hardware costs, and everything is managed by Acumatica. However, there are several "catches" you should know about.

• Catch 1: The Storage Ceiling. You start with 100GB. If you exceed this, the system keeps working, but you lose the ability to create snapshots. This is a major issue for your support team; without snapshots, debugging complex issues in a test environment becomes nearly impossible. Increasing storage is quite expensive.

• Catch 2: The S3 Integration Trap. In the Acumatica SaaS environment, offloading attachments to AWS S3 or Azure is complicated. While the forum says it’s possible, implementing it often requires separate purchases and complex setups that most aren't ready for.

• Catch 3: Data Ownership Costs. Need a copy of your own database? It’s your data, but Acumatica charges a significant fee for this service. Given that snapshot restores have size limitations, you may eventually need that database copy for troubleshooting.

• Catch 4: Performance Restrictions. If you try to run heavy database scripts for data maintenance, Acumatica’s monitoring will likely throttle or restrict your activity to protect their multi-tenant environment.

• Catch 5: Limited Upgrade Control. Your upgrade timeline and versioning are largely dictated by Acumatica. You have very little flexibility compared to other models.

  
  

Pros: No hardware to manage, automated backups, and hassle-free base system updates.

Option 2: On-Premise / Private Cloud

This includes hosting on your own server or a dedicated server provided by an Acumatica partner.

The Partner Hosting Model:

• Catch 1: The Access Gap. Some partners provide a dedicated instance, while others give you zero backend access. In the latter case, getting a database copy depends entirely on your relationship with that partner.

• Catch 2: Maintenance Fees. You will pay the partner for server maintenance and management.

• Catch 3: Backup Integrity. You are relying on your partner’s professional standards. While usually reliable, it's rarely 100% guaranteed unless you verify it yourself.

  
  

The Self-Hosting (Your Own Server) Model:

• Catch 4: The Hardware Split. Acumatica recommends running the application and the database on separate servers. While it runs on a single server, doing so can cause performance bottlenecks—especially when creating and restoring snapshots.

• Catch 5: The MSSQL vs. MySQL Trap.

  • MSSQL: Most implementations require a paid Microsoft SQL Server license—a significant additional cost. You could use SQL Express (free up to 10GB) if you store files outside the database, but this is rarely a long-term solution.

  • MySQL: While Acumatica technically supports MySQL, it is much less tested. Many customizations fail on MySQL, and performance issues are common. Our advice: Avoid the MySQL trap. (Note: MYOB Advanced in Australia uses MySQL and, in our experience, performs worse than the standard MSSQL-based Acumatica).

• Catch 6: Maintenance Responsibility. Whether you use AWS, Azure, Google Cloud, or a local server with a static IP, you are responsible for backups, security, and maintenance.

  
  

Pros: Full control over your versioning, easy S3 integration for file storage, no limits on snapshots, and instant access to your database for deep forensics.

Final Thoughts

Acumatica SaaS is great for businesses with standard processes and small databases. But if you have heavy data requirements, need deep customizations or want full control over your "source of truth," a Private Cloud or Self-Hosted environment is often the more cost-effective and flexible choice.