Cloud Hosted is not Cloud Native: Why the Difference Matters for Construction Estimating
Not all cloud software is created equal. Understanding the difference between desktop applications delivered through a browser and genuine cloud-native SaaS platforms is becoming increasingly important for construction, infrastructure and enterprise organisations.
Just because software runs in the cloud does not mean it was built for the cloud.
The construction industry has undergone a significant shift towards cloud-based software. Estimating, cost planning, quantity takeoff, scheduling and project controls solutions are increasingly advertised as cloud-enabled, web-based or Software as a Service (SaaS).
However, behind those descriptions, there can be fundamentally different technologies, architectures and approaches to software delivery.
Some solutions have been designed from the ground up as modern, browser-native applications. Others remain traditional desktop software, hosted on remote infrastructure and delivered to users through a browser using application streaming or virtual desktop technologies.
Both can provide access to software over the internet. Both may be offered through a subscription. Both can deliver business value.
But cloud-hosted software and cloud-native SaaS are not the same thing.
For organisations investing in technology that will support major projects, enterprise collaboration and long-term digital transformation, understanding that distinction matters.
At Sterling, we believe the underlying architecture of software is just as important as the functionality it provides. That is why Sterling has been developed as a cloud-native SaaS platform, rather than taking traditional desktop estimating software and simply moving it into the cloud.
A desktop application in a browser is still a desktop application
For decades, construction estimating software was developed primarily for Windows desktop environments.
These applications often evolved from single-user systems into networked and client-server solutions. Although many became sophisticated and functionally capable, their underlying architectures were originally designed around installed desktop software.
With the growth of cloud computing, technologies emerged that allow these applications to be hosted remotely and accessed through a web browser.
Examples include Amazon WorkSpaces Applications (formerly Amazon AppStream 2.0), Microsoft Azure Virtual Desktop with RemoteApp, Citrix DaaS and Omnissa Horizon.
These are established and capable technologies, designed to provide access to applications and desktops running within centralised infrastructure.
They can be particularly valuable where organisations need to retain existing software, support specialist Windows applications or provide remote access without undertaking a complete redevelopment.
However, there is an important distinction.
Streaming a desktop application through a browser changes how the software is accessed. It does not automatically change how the software was designed or built.
The application may still depend on Windows-based execution environments, remote application sessions, centrally managed software images and associated infrastructure.
The browser effectively becomes a window into software running somewhere else.
That is fundamentally different from an application designed to run natively through the web, using modern application services, APIs and cloud infrastructure.
Cloud delivery is not the same as cloud-native architecture
The term SaaS is frequently used to describe software that customers access on a subscription basis, with the supplier taking responsibility for hosting and maintaining the application.
Under that broad definition, desktop software delivered through application streaming can form part of a SaaS offering.
However, the commercial delivery model does not tell the whole story.
The real architectural question is whether the application has been designed to take advantage of modern cloud technologies or whether existing desktop software has simply been relocated to cloud infrastructure.
Cloud-native applications are designed around principles such as scalability, resilience, automated deployment, managed services, secure integration and the ability to evolve continuously.
Rather than relying on an individual desktop application session to deliver the user experience, a browser-native application communicates directly with centrally managed application services and data.
This can provide significant advantages in how software is developed, operated, secured, integrated and scaled.
Moving legacy software to the cloud may provide remote accessibility and centralised management.
Building software for the cloud creates opportunities to fundamentally improve how the application works.
Why does this distinction matter to construction and infrastructure?
Construction estimating is no longer simply about an individual estimator producing a cost plan.
Major construction and infrastructure programmes involve increasingly complex relationships between estimating teams, quantity surveyors, designers, planners, procurement specialists, sustainability professionals, commercial teams and project controls.
These teams need to work with connected information, often across different organisations, locations and project stages.
An estimate might begin as an early cost plan, develop through quantity takeoff and detailed resource-based estimating, progress through procurement and scheduling, and ultimately become part of the ongoing commercial management of the project.
That requires more than remote access to an estimating application.
It requires an underlying environment designed to support collaboration, structured data, controlled workflows, integration and continuous development.
Sterling has been built around this principle.
Its browser-native architecture allows estimating, 2D and 3D takeoff, resource libraries, cost and carbon calculations, bid packages, forecasting and lifecycle information to operate within a connected platform.
Multiple authorised users can work within the same project environment, supported by permissions, structured information, auditability and controlled project data.
Rather than treating estimating as an isolated desktop activity, Sterling supports estimating as part of a connected enterprise workflow.
The objective is not simply to make estimating software available anywhere. It is to make estimating data useful everywhere it is needed.
The hidden complexity of desktop software delivered through the cloud
Application streaming can reduce some of the challenges associated with traditional desktop deployment. It can centralise software maintenance, simplify access and reduce the need for installations on individual devices.
However, it also introduces a different set of architectural and operational considerations.
Depending on the solution, these can include managing desktop application images, Windows environments, application compatibility, session capacity, remote compute resources and the performance of streamed user interfaces.
Costs may also involve virtual compute capacity, session usage, licensing, graphics resources and the underlying infrastructure required to deliver application sessions.
Modern application streaming platforms offer sophisticated management and scaling capabilities, so these challenges are not necessarily disadvantages in every deployment.
Nevertheless, the underlying desktop application remains a consideration when determining scalability, integration options, performance and long-term operating costs.
A browser-native SaaS application follows a different model.
Users interact with a web application, while the underlying services and infrastructure are designed to support shared application workloads, controlled access, service-level scalability and continuous delivery.
This does not eliminate infrastructure costs or automatically guarantee better performance.
It does, however, provide a fundamentally different architectural foundation on which to optimise the application for enterprise-scale delivery.
For organisations evaluating long-term software investments, it is important to understand not just the subscription price, but also the technology and operational model behind the service.
Built for continuous development, not periodic desktop upgrades
One of the key benefits of modern SaaS is the ability to evolve the platform continuously.
Traditional desktop software has often followed a release model involving application installation packages, version compatibility, workstation upgrades or centrally managed desktop images.
Application streaming can simplify this by centralising the application and making updated versions available to users.
However, cloud-native development takes a broader approach.
Modern deployment pipelines, automated testing, containerisation, controlled releases and application monitoring allow software providers to develop and deliver improvements frequently and consistently.
Sterling operates on a continuous development and delivery model, with regular platform enhancements, performance improvements, new capabilities and integration updates.
Its modern technology stack supports ongoing product development without requiring customers to undertake traditional desktop application installations.
This is particularly important for enterprise organisations where software needs to respond to changing requirements, evolving standards, new integrations and emerging technologies.
A modern estimating platform should not simply support today's workflows. Its architecture should make tomorrow's requirements easier to deliver.
Sterling SaaS: Multi-Tenant or Single-Tenant deployment
Not every organisation has the same requirements for software deployment.
For some, a shared SaaS environment provides the right balance of functionality, efficiency, scalability and managed service delivery.
For others, particularly those operating within highly regulated environments or delivering nationally significant infrastructure programmes, additional requirements may exist around infrastructure segregation, security controls, data governance and operational assurance.
Sterling supports different SaaS deployment approaches to meet these needs.
Multi-Tenant SaaS
Sterling can be delivered through a managed multi-tenant SaaS environment, where organisations benefit from shared platform infrastructure while maintaining logical separation of their application data, users and access permissions.
This model supports efficient platform management, continuous development and scalable access without customers needing to manage the underlying application infrastructure.
Single-Tenant SaaS
For organisations requiring additional environmental separation, Sterling can also be delivered through a dedicated single-tenant deployment.
This provides a separate application environment and enables the hosting, infrastructure, networking, operational and security arrangements to be defined around an organisation's specific requirements.
Importantly, single-tenant SaaS does not mean reverting to desktop software or adopting a traditional installed application.
It remains the same modern, browser-native Sterling platform, delivered through a different infrastructure and operational model.
The distinction is important: multi-tenant and single-tenant describe how the service is deployed and isolated, not whether the underlying software is genuinely cloud-native.
Cloud flexibility without compromising sovereignty
For many enterprise organisations, particularly those operating within defence, nuclear, critical national infrastructure and the public sector, the location and control of data are becoming increasingly important.
Cloud adoption needs to be considered alongside data sovereignty, security sovereignty, organisational governance and regulatory obligations.
A cloud-native application should provide flexibility in how these requirements are addressed.
Sterling has been developed with a cloud-portable architecture, using modern technologies that support deployment across different infrastructure environments.
Depending on client requirements, deployment options can include UK-hosted private cloud infrastructure and appropriately configured public cloud environments, including platforms such as Microsoft Azure, Amazon Web Services (AWS) and Google Cloud, subject to the agreed technical architecture and deployment scope.
The objective is to allow organisations to define their requirements for hosting and operational control, rather than having those requirements dictated solely by a fixed software delivery model.
For some clients, a standard UK-hosted SaaS service may provide the appropriate solution.
For others, a dedicated environment within their preferred cloud provider, tenant arrangements or approved infrastructure may be required.
These decisions can form part of the technical and security discussions during solution design.
The cloud platform should support the customer's security and governance requirements, not force the customer to compromise them.
Data residency and sovereignty are not the same thing
Hosting data in a particular country is an important consideration, but geography alone does not establish complete data sovereignty.
Organisations must also consider who can access their information, where administrative operations take place, which legal jurisdictions may apply and how data is protected throughout its lifecycle.
For highly regulated environments, relevant considerations may include the location of primary and backup data, the jurisdiction of infrastructure and service providers, administrative access, identity management, encryption, audit logging, support arrangements and incident response responsibilities.
Sterling is designed and developed in the UK, with UK-hosted deployment options and a security-focused approach to enterprise application delivery.
The platform supports controlled access, role-based permissions, secure authentication, encryption and auditability as part of its broader security architecture.
For organisations with more demanding requirements, the deployment and operational arrangements can be assessed against their security policies and procurement obligations.
Neither a multi-tenant nor a single-tenant deployment automatically guarantees regulatory compliance or sovereignty.
Those outcomes depend on the complete technical, contractual and operational arrangements.
This is why Sterling approaches security and deployment as part of the overall solution architecture, rather than treating hosting location as the only consideration.
Integration and AI readiness depend on architecture
Another important difference between traditional desktop software and modern cloud-native platforms is how information can be accessed and exchanged.
Construction organisations increasingly operate complex technology ecosystems incorporating BIM and Common Data Environments, estimating, scheduling, ERP, procurement, project controls, carbon data and reporting platforms.
The value of those systems depends increasingly on the ability to exchange structured information without repeatedly exporting, reformatting and reimporting data.
Desktop software can provide APIs and integrations, and application streaming does not inherently prevent integration.
However, an API-driven, cloud-native architecture provides a strong foundation for making integration part of the application design rather than an additional mechanism around the user interface.
Sterling has been developed with integration as a core architectural principle.
Through established APIs, connected data workflows and its secure Model Context Protocol (MCP) service, Sterling can exchange information with other enterprise systems and support controlled AI-assisted workflows.
This enables connections with platforms such as Autodesk, Procore, Microsoft SharePoint, Primavera P6, Microsoft Project and external carbon data services.
The aim is not to require every organisation to replace its existing technology.
It is to make Sterling part of a connected ecosystem in which estimating, quantity, cost, carbon and programme information can move between systems in a controlled and meaningful way.
As artificial intelligence becomes increasingly embedded within construction technology, access to governed, structured application data will become even more important.
The future of estimating is not simply an application that users can access remotely. It is a platform whose data and capabilities can participate securely in wider digital workflows.
Questions organisations should ask when evaluating cloud estimating software
When evaluating software described as cloud-based or SaaS, organisations should look beyond the marketing terminology.
Is the application genuinely browser-native, or is it a Windows desktop application streamed through a browser?
Does the architecture support concurrent collaboration, centrally governed data and structured integrations?
How are application updates delivered, and what infrastructure is required to support additional users?
Can the solution be deployed in an environment that meets the organisation's security, data residency and governance requirements?
What options exist for multi-tenant or single-tenant delivery?
Can the platform integrate securely with existing enterprise systems and future automation technologies?
These are not simply technical procurement questions.
They influence the long-term cost, flexibility, resilience, usability and strategic value of the software investment.
For construction and infrastructure organisations making technology decisions that may affect programmes for many years, the answers can be just as important as the functionality demonstrated on screen.
Why Sterling was built differently
Sterling was developed with a clear objective: to provide a modern, connected environment for cost and carbon estimating across the construction and infrastructure lifecycle.
That required more than recreating existing desktop estimating functionality within a web browser.
It required an architecture designed around collaboration, structured information, scalability, integration, security and ongoing innovation.
From early cost planning and detailed resource-based estimating through to digital takeoff, forecasting, lifecycle assessment and connected enterprise workflows, Sterling brings these activities together within a browser-native SaaS environment.
Its deployment architecture also provides flexibility for organisations with differing security, hosting and sovereignty requirements, supporting both multi-tenant and dedicated single-tenant delivery approaches.
As construction technology continues to evolve, the importance of the underlying software architecture will only increase.
Cloud-native does not mean that every problem is automatically solved, or that traditional desktop solutions have no remaining value.
It means the software has been engineered around a different set of possibilities.
Possibilities that allow information to become more connected, applications to evolve more rapidly, infrastructure to be managed more flexibly and organisations to make greater use of the data they already hold.
Cloud-native by design. Not desktop software delivered through the cloud.
The construction industry needs software that supports the way modern projects are delivered, not simply a different way of accessing the software of the past.
Moving a desktop application into the cloud can change where it runs.
Streaming that application through a browser can change how users access it.
Yet neither automatically transforms the architecture of the software itself.
Sterling represents a different approach: a modern, browser-native SaaS platform built to connect people, processes and data across estimating, cost, carbon and the wider project lifecycle. With flexible deployment, enterprise security, UK development, data sovereignty considerations and an architecture designed for integration and continuous innovation, Sterling provides a foundation for organisations looking beyond simply accessing software remotely.
Built for the cloud. Designed for the enterprise. Ready for the future of construction.
To learn more about Sterling's cloud-native architecture, SaaS deployment options or enterprise security capabilities, contact the Sterling team to discuss your requirements.
