Infront’s Software

Save time, money and alleviate aggravation with Infront’s software solutions.

Designed from the learning’s of our clients’ challenges, we develop Management Packs (MPs) to meet their needs then make our MP software available to all our clients for use.

Management Packs Available for Purchase

Management Packs Available for Free

Orchestrator Client Testimonial

Infront Consulting Orchestrator Pack lets us keep track of our Runbooks and their status. As more and more Runbooks are added to the environment, it was becoming a headache to identify problematic ones. With the Infront Orchestrator Management Pack, we were able to identify and remedy Runbooks that were having issues. Nice product!

— John Rea, TW Telecom Corporation

 

Beekeeper  (Formerly OPAS)

Tired of late-night patching?
Failing compliance and security audits?

With Beekeeper  you can fully automate patch management to minimize errors and reduce downtime to create a more secure and compliant environment, ultimately resulting in a better return on investment.

  • 100% compliant every month
  • Applications validated automatically after a server reboot
  • Monthly cost savings in OpEx budget
  • Work life balance for IT staff
  • Zero downtime of highly available applications during scheduled maintenance windows

With Beekeeper you can fully automate the validation checks of your application to eliminate human intervention and action. Integrate Beekeeper with System Center Configuration Manager and you can automate the end-to-end patching and application validation of your high availability applications and eliminate downtime.

Beekeeper is a SaaS offering that takes over where SCCM (System Center Configuration Manager) or any other patching tool leaves off and guarantees 100% patching compliance.  Beekeeper is used to assist companies get past the 80-yard line where patching tools stop and accomplishes the hardest part – getting past the last 20 yards.  Beekeeper makes patching entirely automated;  reducing the attack surface and vulnerability to an attack on applications that are way behind on patching or have never been patched.  Download the trial and see for yourself.

 

Origin Story

Beekeeper  was originally developed as an automation solution for an American regional grocery chain client that was using System Center Orchestrator and multiple, complex, dependent Runbooks.  Our client’s Exchange team was frustrated by the fact that they had to spend most of their Friday nights waiting for their Exchange servers to be patched only to have to test that the Exchange application started properly and was healthy after the Exchange servers were restarted after patches were applied.

Infront created the automation to test the health and functionality of the Exchange servers using Runbooks in Orchestrator. We worked with our client to identify what steps they took to validate that the Exchange application (used for email) was online and functioning properly. A number of the steps taken at the time were interactive, meaning that the IT admin logged into the Exchange server and looked for services to confirm that they were started, opened Outlook and sent an email and then confirmed receipt–A ton of manual steps.  Infront evaluated each of the manual steps and then looked at how we could automate this process with our programming skills. Part of this process was to look for any steps that had to be performed in a specific order.

The Infront team successfully completed this project, and our client had a functioning and powerful automated Exchange validation system that eliminated the need for the Exchange team to work weekends for patching.   Now our client’s Exchange team is only called or emailed if the validation routines fail.  This saved the American regional grocery chain a great deal of money on overtime and provided much better work life balance.   Our client is a family owned company that prides itself on family values, so this initiative aligned really nicely to support that.

When Infront started to experiment with the code developed outside of the client’s environment, we found that it didn’t scale well to 1000’s of servers. System Center Orchestrator was a performance bottleneck, so we rewrote the entire engine and eliminated our dependency on Orchestrator. We branded the new, rewritten solution, Beekeeper because whenever we enter a large datacenter, the servers sound like a humming beehive while the IT admins are the beekeepers. That server buzz sound is hard to miss.

Let us help you build your business case:

Current Operational Costs

How much time are your application owners spending validating the health of their applications after the servers they run on are rebooted?

Reduce Production Outages

Avoid a 60-minute production outage by reducing your risk with Beekeeper and save up to $474,000.*

*Based on Ponemon Institute 2013 Cost of Datacenter Downtime Study

Allocation of Resources

The cost of resource re-allocation could amount to $105,000 per source.* Beekeeper  eliminates patching downtime, redeploying your staff on projects that add value to the business.

*Based on industry averages

Average Cost of Breach

Save by protecting your system with Beekeeper , since a single data security breach can cost up to $5.85 million,* and the reputation of your brand.

*Based on Ponemon Institute 2014 Cost of Data Breach Study

Honeypot-Logo&Symbol-Horizontal

HoneyPot

Would you like to Understand Your Azure Expenditures?

Infront’s HoneyPot will provide:

  • Deeper insight into your Azure expenditures
  • Proactively identify cost centers that aren’t inline with expectations
  • Chargeback or showback expenditures by site, department, application or other data dimensions
  • Manipulate your Azure financial consumption based on your requirements
  • Present data to management in a business context

Origin Story

Honeypot was developed by the Infront team for a Boston based software company who began migrating their applications from multiple global data centers to Azure.  The client was originally set up so that there was a business unit for each of the different applications.  Their goal was to have a tool to track the usage of different Azure IaaS resources (CPU, Memory, storage) and charge back the individual business units for their portion of the Azure monthly invoice.   Honeypot was born.

The Microsoft bill breaks out utilization by CPU, Memory, and Storage but it doesn’t look at any ‘tags’ on the system. Tagging in Azure allows the owner/administrator of the VM to identify it. For example, you could add a location, an owner, an application name, or whatever information you want to make it identifiable. It could be marked as test or prod to identify the environment.

The creation of the chargeback tool allowed the Boston software company to see a breakdown of their Azure usage and the consumption costs to the correct business unit.

Attached is a slide-deck that shows some of the ways we can breakdown the data.

Review a Sample Report