Guardian: complete visibility when working with staging environments

Back To Resources

Staging environments are a vital element of software testing and deployment, the point at which code, updates and builds are integrated and tested against something as close to a production environment as possible. Ideally, they would be identical, but that’s typically not the case.

Get these steps right and you can have confidence that your software will work as expected when it is deployed. However, in reality there will always be some differences between the staging environments and the production environment. For example, a staging environment is often dependent on the infrastructure developers work with, and typically they will have full control here, whereas a production environment is ‘locked down’. This means that testing will not be 100% accurate.

These differences introduce a significant risk: however careful your testing, defects can be released into the production environment. Resulting in business, operational, and environmental issues. For example this can impact security, data integrity, reliability of services leading to a business impact on customer trust. Do you know and can you measure the differences across your staging environments?

Complete visibility

Getting a good understanding of these differences between the staging and production environments can help you to identify where defects could creep in. But finding these differences can be time-consuming and labour intensive to do.

Which is where Cloudhouse Guardian comes in. Guardian gives a surface view of what is the same and what is different across your staging and production environments, allowing you to check that everything is configured as you wanted. The simple user interface shows the differences and similarities between the two so you can quickly and easily compare them.

What’s more, if you are running regular or ongoing updates, Guardian also allows you to create policies to ensure your preferred configuration criteria are adhered to each time. These policies may be your own or for example as defined by the Center for Internet Security (CIS) allowing you to achieve best practice configuration.

This oversight from Guardian can give you confidence that you won’t be caught out by the unexpected. The insight ensures consistency and efficiency, reducing the risks associated with updates.

Find out more

To find out more about Guardian and how it can be used with staging environments, please contact us for a no obligation conversation.

About Cloudhouse

Avatar photoCloudhouse is experienced in problematic application migration and config monitoring systems to fix the unfixable and modernise any IT estate – whether it’s run on-premises or in the cloud. With two proven solutions; Alchemy: Cloudhouse Application Packaging Solution modernises IT estates by fixing unfixable apps and moves them onto a supported operating system.

Load More


How much does Cloudhouse cost? Down Arrow

Cloudhouse costs are split into two elements – the licensing required to deploy application compatibility packages, and the professional services needed to create the application compatibility packages.

Licensing is offered on a per user basis for desktop applications and a per server basis for server applications. There are discounts available based on volumes.

Professional Services costs are dependent on the nature and complexity of the application. We quote a cost for packaging once we have been able to see the application, or portfolio of applications.

Contact us here with your requirements and we will provide you with a quote.

Packaging and Maintaining Applications
Who is responsible for packaging desktop and server applications? Down Arrow

Cloudhouse provide the Professional Services to package applications.

Requirements for Test and Development Down Arrow

Cloudhouse recommend packaged applications are tested in the standard UAT environments used for natively installed applications, or applications packaged in App-V. The more representative the test environment is of the live environment, the greater the chance of finding any issues prior to go-live.

Updating Applications Down Arrow

Service packs and updates can be applied to the applications in a package using the Editor, refer to Updating, Editing and Maintaining Containers which describes how a new snapshot is created for the update, and how it is then applied to the package.

Who manages Cloudhouse operationally within an account? Down Arrow

Cloudhouse recommends the same team who manage the operations of native apps.

Automation and Deployment Down Arrow

Applications running in Application Compatibility Packages can be deployed, and managed with same tools, or scripts used to deploy natively installed applications e.g. SCCM, InTune, LAN Desk. Please refer to Supported 3rd Party Products and Versions for details.

How do we know which of our departments/ teams should support the Package? Down Arrow

The Cloudhouse Package does not include OS components, it only contains the packaged application plus Cloudhouse components. Cloudhouse recommend the same team that is responsible for supporting applications packaged with App-V, or delivered as natively installed applications, support Cloudhouse Application Compatibility Containers.

Documentation for Service Desk & Service Management Down Arrow

Full documentation is made available to Cloudhouse partners and customers as required.

Do Cloudhouse provide training? Down Arrow

Cloudhouse offers a full packaging service that can scale to meet any requirement. In the event, however, that a partner wishes to offer application compatibility packaging as part of a wider solution, Cloudhouse will work with that partner. Please contact us here for details.