I spend a lot of time talking about our centralized logging software: Loupe Server. It’s a way to track errors across your applications running anywhere in the world. But what I don’t discuss often is how it’s hosted. Loupe Server is unique in that you can not only subscribe to it as a SaaS; you can host it yourself.
The option to self-host a cloud service is not the standard expectation, but it’s a feature of Loupe important to our users.
Without the option, many couldn’t use it in the first place.
Here, I’ll go over a few reasons our users self-host Loupe for their error tracking and log management.
Security and Data Management
One of the main reasons to self-host your error tracking is when you have particular security needs for your log data. For many users, it doesn’t matter how secure the cloud platform is; they want to own the data storage directly for auditing and management purposes.
This is the most common reason why our users self-host Loupe. If you have strict data retention needs or desire complete control, we are happy to let you host Loupe in whatever way makes you the most comfortable. For some, that means using the Loupe cloud service, and let our team handle the hosting side of things. Other organizations have staff that can take data security into their own hands, and we’re happy to help them do that as well.
Security and data management don’t have effective one-size-fits-all solutions. And that means we can’t sell an effective error tracking system that way. Offering multiple ways to host Loupe allows us to fit each user’s security requirements better.
Put the Cost of Storage in Your Control
Part of the appeal for many cloud services includes saving on infrastructure costs. It really is a way for organizations to save money, especially start-ups. But when you already have the infrastructure to host a service yourself, the value proposition is much worse. Let’s say I already have the hardware to host an error tracking system, or I have a ton of Azure cloud space. In this scenario, it may cost less to host a service myself than to sign up for one over the long haul.
Most cloud services include a scaling cost for storage, including ours. For Loupe cloud, the pricing is between $5 to $15 for each GB over the individual plan’s allotted storage. And for many users, an extra $15 a month for a bit more storage is a reasonable exchange. But if you require hundreds of GBs of data over the allotted storage, that will get pricey.
In high storage, lower user count scenarios, self-hosting Loupe is less expensive long-term. The upfront costs are higher, but don’t involve any storage pricing. You pay an initial price per server, per user license, but not for data. As long as your user count isn’t super high, you’ll likely come out ahead if you require a lot of storage.
If that sounds like your situation, and you are looking for a self-hosted log management system, I would look at our plans and see if one would work for you.
Keeping Things Local
When I discuss centralized logging, I generally refer to situations where you want to track errors as they happen across the world. It’s the scenario where centralized logging is the best solution, but fails to show centralized logging’s utility in localized situations.
There are cases where you may not want to send your log data outbound (for security or logistical reasons), but still centralize it locally to simplify error tracking across multiple devices. Sure, for a group of five computers in a small office, self-hosted error tracking is overkill. But when you increase the number of devices to dozens, maybe hundreds, tracking your log data becomes much harder to do without a dedicated tool. Hosting an error tracking system on the local network is a good solution, as now you can manage the sheer number of devices, but still stay offline.
Deploy On-Premise Error Tracking it With Your Solution
Do you create a full system solution for your customers? Do you want to include an error tracking system as part of that solution without building your own? The self-hosted version of Loupe makes that possible.
We offer an OEM version of Loupe, which is undoubtedly a departure for a cloud service company. But what it allows our customers to include an error tracking system with their system solution. This helps their customers manage their own errors with their own deployment of Loupe while helping the system seller manage log data efficiently for all of their customers.
Overall, this is a niche scenario. But when it comes up, we’re glad we have an OEM version of Loupe to offer.
The Cloud is Not the Only Future
Cloud-hosted software as a service is a concept here to stay, and get more prominent as time moves on. But it’s not the only way software should be offered. There are just too many scenarios in which local software or self-hosted software makes more sense. That’s why we have that option for Loupe Server as well. So, if you feel that an error tracking solution would be better self-hosted rather than somewhere in the cloud, trust your gut and host it yourself.
If you want to give Loupe Server a try, you can learn more about our free trial in the link below. If you try and like Loupe, you can purchase a license for local hosting or use our cloud service. Either way, we just want to provide the best centralized logging solution we can.