PlotBox Blog For The DeathTech Industry

Not all Clouds are Equal: Cloud-Native vs Cloud-Hosted Cemetery Software

Written by Graeme Arthur | 7/25/25 2:01 PM

 

| Read time: 3 mins

‘The cloud’ has become a catch all term when talking about cloud-based technologies. And as an oversimplification, it obscures much of the nuance in how those services are built and deployed, as well as how your data is captured and managed.

That’s important because when exploring digital upgrades, what’s being offered to you as a cloud service may not necessarily meet your needs or expectations - both in the here and now, and in the future.

This matters because when comparing cloud-based solutions, you’re not always comparing apples with apples. And comparing two things that are fundamentally different won’t give the best idea of what’s right for you.

To ensure you’re not being ‘cloud-washed.’, we look at the differences between two common deployment models - cloud-native and cloud-hosted, and the benefits of a purpose-built platform vs a retrofitted legacy product that’s ‘dressed up’ in the cloud.

 

Why ‘the cloud’?

 

‘The cloud’ reflects a shift in how businesses operate, as we increasingly rely on cloud-based applications and technologies for everything we do - from creating documents and file sharing, to all forms of collaboration and communication.

And there are numerous benefits for bereavement services and deathcare operators:

 

Reduced costs: with minimal start-up outlays and predictable operating expenses;

Reduced risk and legacy protection: safely securing and preserving your records from loss or damage;

Greater efficiencies: with a single source of truth accessible by anyone from anywhere at any time;

Future-proofing: removing old, unstable IT infrastructure, systems and retired databases from the equation.

Greater security: regularly backing up data, stored securely across multiple data centers.

 

With all of this in mind, you’re undoubtedly asking yourself if your current systems allow you to meet these changing needs and expectations.

You may also be asking if your current or future vendor is able to provide you with a solution that meets those needs.



Cloud-hosted.

 

And it’s here where you may encounter offerings that are, in essence, a ‘cloud-hosted’ version of your existing solution.

Cloud-hosted applications typically take a traditional on-premise application and migrate it to a cloud server.

This ‘lift and shift’ approach means taking it as is and moving it into the cloud, where it's run as a virtual machine. [1] 

It often retains a ‘monolithic' architecture, meaning that the application remains as one single, large, interdependent unit 

This monolithic structure can potentially necessitate remote-desktop-style workarounds that restrict usability and speed.

Here, the core architecture of the application doesn’t change - typically still relying on legacy codebases (the source code for the software system) [2], and old database structures with limited flexibility and scalability.

One major downside to this approach is that existing limitations or issues can still remain. It’s also worth noting that migrating to the cloud doesn’t necessarily mean that it’s utilizing the more modern approaches, or advanced functionality of a cloud environment. [3] 

Imagine moving your entire office with all of its existing furniture and layout into a rented building. You may be in a new location, but you’re not taking full advantage of all of the new building’s features.

In contrast, solutions like PlotBox that are designed for the cloud from day one take a cloud-native approach.



Cloud-native.

 

The cloud-native approach is predicated on building and managing applications from the ground up within the cloud environment itself.

In this way it can take advantage of “the elasticity and distributed nature of the cloud.” [4]

Rather than the single, monolithic nature of cloud-hosting which is highly interdependent [making changes and deployments more difficult over time], cloud-native applications are built around smaller, independent services.

This makes it easier to achieve greater speed, agility, scalability and cost efficiencies. [4]

The self-contained nature of cloud-native [that is, components designed to be as independent as possible] also enables your provider to more easily make updates, fix issues, and deliver new features without downtime or negative impacts on service delivery. [5]

All together, for you that means no clunky installations, no server maintenance, no workarounds, and no VPNs, while giving greater accessibility, more seamless software updates, and better all-round performance.



Why it matters.

 

All of this matters because, rather than maximizing the potential benefits of a cloud environment, ‘legacy systems in disguise’ may create hidden risks:

 

Poor performance - not being designed to leverage the full elasticity of the cloud (not automatically adjusting resources based on demand), limiting performance and productivity [6], 

Integration limits - often legacy applications are reliant on older APIs or communication protocols (rules governing exchange of data), without modern digital ecosystems in mind;

Security vulnerabilities - they may not be designed to take full advantage of cloud security capabilities [6], or with vulnerabilities inherited from the original design;

Lack of true scalability for growing services - often requires increasing the capability of the entire application, being more inefficient and more costly than cloud-native;

Cloud-native, in contrast, unlocks true digital transformation: greater levels of integration and automation, real-time data insights, with more flexibility and scalability for a more modern user experience.



Why PlotBox?

 

PlotBox is trusted by over 2,000 cemeteries, crematories and funeral homes globally and has been built and designed for the web from day one.

Because we’re not adapted from older desktop software, there are no time-sapping, costly workarounds to existing infrastructure; rather, we can provide quicker deployments and greater flexibility, resilience and responsiveness with automatic updates without disruption.

Our teams fully encapsulate the ‘cloud-native’ ethos that prioritizes agility, resilience and efficiency.

Our exceptional dev skills combined with our experience in the deathcare and bereavement sectors combine to deliver a best-in-class platform backed by a modern cloud infrastructure.

That makes us the ideal option for cemeteries, crematories and funeral homes wanting to secure their future.

Is digital transformation on your agenda? Let's connect.

 

 

Refs.

[1] What is Lift and Shift in Cloud Migration?

[2] What is a codebase?

[3] Cloud hosted vs cloud native solutions

[4] What is cloud native?

[5] What is Cloud Native?

[6] What does cloud-native mean vs cloud-hosted?