Key Insights:
CMiC runs as multi-tenant SaaS, private cloud (PaaS), or on-premise, and every option uses the same single database and code set.
Your deployment model decides who manages servers, upgrades, and hosting security. Your data model and workflows stay the same.
SaaS keeps you on the current release with no internal upgrade projects, reduces hardware capital spending, and makes IT costs more predictable.
IT capacity, integration needs, cross-border data rules, and security evidence are four practical signals for matching a model to your business.
A later move between models is a planned project, so early decisions on custom code and third-party services keep future options open.
Construction companies run finance, payroll, and project delivery across many jurisdictions, time zones, and partner networks. The software behind that work holds the company's financial record, so deciding where it runs, whether in a CMiC cloud-based deployment or on your own servers, is a business decision as much as an IT one.
For CMiC, the short answer to "Is it cloud-based?" is yes. The fuller answer explains how hosting choices affect your IT workload, costs, security, and data obligations. This article covers the ways to deploy CMiC, what each model changes for your teams, and how to choose and later change models.
Is CMiC Cloud-Based?
Yes. CMiC runs in the cloud, and it can also run on servers your company owns. Customers choose from three core deployment models: multi-tenant Software as a Service (SaaS), Platform as a Service (PaaS) delivered as a private cloud, and on-premise. CMiC's deployment guide also covers hybrid setups, which combine elements of more than one model.
Every model gives you the same construction ERP, the core system behind accounting, payroll, procurement, and project controls. What changes is where that system runs and which team keeps it running.
CMiC's SaaS option runs on Amazon Web Services (AWS) in a multi-tenant architecture, which means many customers share one hosted environment. CMiC hosts and maintains it, and your teams reach it through a standard web browser. CMiC has offered SaaS since 2014.
Private cloud gives your company a dedicated, single-tenant environment that no other customer shares. On-premise deployment places CMiC on your own servers, and your IT team owns the hardware, network, backups, and maintenance schedule.
Every option runs on the same single database. Job cost, payroll, procurement, and project controls connect in one place. CMiC also develops its software in-house on a single code set, so your chart of accounts, approval workflows, and reports work the same way in each model.
The choice, then, has little to do with features. It comes down to who carries which responsibilities, and that split is where the models begin to separate.
How Responsibilities and Costs Split across CMiC Deployment Models
Every cloud arrangement divides duties between the provider and the customer. U.S. federal cloud guidance describes this as a shared responsibility model. The provider typically handles hardware, infrastructure security, and software updates. The customer stays accountable for who can access the system and what they can do in it.
The balance tilts toward the provider as you move from on-premise to private cloud to SaaS. Four areas show how that balance changes your team's workload.
Infrastructure and hosting: On SaaS, CMiC runs the servers, storage, and backups. Private cloud gives you a dedicated hosted environment. On-premise puts hardware purchases, security patches, and replacement cycles on your IT team.
Upgrades: On SaaS, CMiC handles every update and patch, so you run the current version with no internal upgrade project. On-premise upgrades follow your own schedule because your team performs them. For private cloud, confirm in your agreement who schedules and runs upgrades.
Custom code and integrations: Dedicated environments usually leave more room for custom code and direct links to other systems. Multi-tenant SaaS favors standard configuration and supported connection points, since every change must work for all customers on the shared platform.
Security and access: Your team owns user roles, permissions, and approval rights in every model. Server and network security moves toward the hosting provider as you move toward SaaS.
The same split shapes your costs. On-premise ties up capital in servers, storage, and periodic hardware refreshes, plus the staff time to run them. CMiC's SaaS reduces that capital outlay and makes IT spending more predictable.
NIST's cloud computing guide treats economic factors as part of any cloud decision. A fair comparison runs across a full hardware refresh cycle and includes staff time.
Once you know who owns what and who pays for what, the useful question becomes which split fits the way your company runs today.
How Do You Choose the Right CMiC Deployment Model?
The Construction Financial Management Association (CFMA) held a 2025 webinar that challenged the assumption that every construction company must move its ERP to the cloud. Its advice was to evaluate the ERP partner before making any switch. The same thinking applies to choosing a CMiC model, and four factors deserve the closest look.
Start with IT capacity. A lean or outsourced IT function will struggle to patch servers, test upgrades, and manage backups across several offices, and SaaS removes that load. A large internal team with established server operations may findprivate cloud or on-premise a natural fit.
Next, map your integrations. List every system that exchanges data with your ERP, from estimating and scheduling tools to banking and union reporting. A heavy set of custom connections leans toward a dedicated environment, and a lighter set built on standard connections sits comfortably on SaaS.
Then check cross-border data rules, especially for payroll and employee records. The European Union requires safeguards whenever personal data leaves the European Economic Area, such as an adequacy decision confirming a country protects data to EU standards. Canada's federal privacy guidelines keep companies accountable for personal information they send to a third party for processing, including one abroad. Check the rules in every country where you employ people.
Finally, review security evidence. CMiC cites SOC 3 certification for its cloud environment, and a SOC 3 report is a public summary of an independent audit of provider security and availability controls. Ask whether a detailed SOC 2 report is available under a nondisclosure agreement, since that version includes the test results.
Your answers reflect the company you run today. Acquisitions, new regions, and IT restructuring can change them, which makes it worth knowing how a move between models works before you need one.
Planning a Move between CMiC Deployment Models
Deployment choices can change over the life of a platform. An on-premise customer facing a server refresh may weigh private cloud. A SaaS customer that acquires a business with heavy custom code may need a dedicated environment.
The single database works in your favor here. Your chart of accounts, approval workflows, and reporting logic share one foundation in every model, so the move centers on the environment around them. Three areas in that environment deserve attention before you set a date.
Custom code and direct database connections come first. Review everything your team wrote for a dedicated server against the connection points the target environment supports. Rework those items early so they never delay the cutover, the point when your teams stop using the old environment and start using the new one.
Third-party services come next, because the arrangement behind a service can depend on your deployment model. Tax calculation shows how. CMiC's on-premise and PaaS customers hold a direct agreement with the tax data provider and process monthly tax updates in their own environment, and CMiC is moving that service to a cloud version billed through CMiC. List every service like this and confirm how each one works in the target environment.
Timing is the third area. The U.S. Government Accountability Office treats cutover as a distinct phase of data migration, with its own leading practices. Schedule the switch away from fiscal year-end, payroll runs, and major billing periods. Run the same job cost and payroll reports in both environments and compare the results before you retire the old one.
Handled this way, a change of model becomes a planned project with a known scope. You confirm your numbers match, and your teams keep working on the platform they already know.
FAQs about CMiC Cloud Deployment
These answers go beyond the basics above, from software updates and security reports to field access and hybrid setups.
How Does CMiC Cloud Handle Software Updates?
On CMiC's SaaS deployment, CMiC handles all software updates, patches, and maintenance. Users work on the current version without running internal upgrade projects or planning for upgrade downtime. On-premise customers schedule and perform upgrades themselves.
Does CMiC Offer a Hybrid Deployment Option?
CMiC's deployment guide covers hybrid deployment alongside SaaS, private cloud, and on-premise. A hybrid setup mixes approaches, such as keeping some systems on your own servers and running others in the cloud. Confirm the exact split with CMiC during scoping, since hybrid designs vary by company.
What Security Certification Does CMiC Cloud Hold?
SOC 3 certification covers the CMiC cloud environment, according to CMiC. This public report summarizes an independent audit based on the American Institute of Certified Public Accountants (AICPA) Trust Services Criteria. For deeper due diligence, ask about access to a detailed SOC 2 report under a nondisclosure agreement.
Can Field Teams Use CMiC with Limited Connectivity?
Yes. CMiC's CONSTRUCT project management suite works offline, so teams can keep working on sites with weak connections. Data synchronizes automatically once the connection returns.
Can You Change CMiC Deployment Models Later?
A change of model works best as a planned project. Review custom code, third-party services, and integration points against the target environment. Avoid fiscal year-end and payroll periods for the switch, and confirm that reports match in both environments before you retire the old one.
Matching CMiC Deployment to Your Business
CMiC gives you a choice of multi-tenant SaaS, private cloud, or on-premise, with hybrid options for companies that need a mix. All of them share the same single database. Your IT capacity, integration needs, data rules, and cost priorities decide which model fits.
CMiC's track record supports that choice. More than 400 companies run CMiC in the cloud worldwide, and one-quarter of the contractors on the Engineering News-Record (ENR) Top 400 list use CMiC as their construction ERP.
Sources: