DevOps cloud hosting solution for enterprises

Cloud migration from AWS to Hidora: 5x hosting bill reduction

To run a successful business, especially for companies who just started their way it is important to stay available for the customers all the time. Meanwhile, it could be very expensive for startups to use such popular solutions like AWS, for example. How can startups get high-quality hosting at low prices? Let’s find out in this case study.

We talked to Steven Titren, a co-founder of DigiReward, who shared his experience of using Hidora PaaS and explained how DigiReward reduced its hosting spendings by 5x times comparing to AWS.

Logo digireward

To put it simply, DigiReward was previously hosted on AWS. The founders decided to move to Hidora because of:

  • Pricing (cheaper and simpler than on AWS);
  • Better level of support;
  • Vertical & Horizontal scalability;
  • Better performance.

application migration hidora

About DigiReward

DigiReward is a French startup that was founded 2 years ago. The DigiReward team has developed an application for rewarding members of a community.

Initially started as an application to reward users for their actions on social networks (likes, shares, comments on Facebook, Twitter and Youtube) and on some physical media (QR Code scanning, geolocation…) DigiReward soon became a truly multichannel reward solution, capable of engaging users on many physical and digital media.

This application helps companies grow the engagement levels of their users in social media, websites, apps, points of sale, newsletters and more by offering an innovative reward system.

The company’s fans and customers can turn their actions (purchases, likes, reviews, etc.) into points. With these bonuses the user can access a virtual shop offering goodies, coupon codes, physical products and invitation to events. It’s a kind of virtual currency that the user can redeem for real products.

DigiReward helps companies grow their community and increase the number of happy and loyal customers.

What is the architecture of your application on Hidora?

Today we have a simple LAMP (Linux, Apache, MySQL, PHP). To build a new, more scalable version of the application we have added Reddis and MongoDB. Moreover, we enabled high availability for our production application by adding an extra load balancer and PHP web server.

What problems did you have before migrating to Hidora? What solution did you use before?
Before moving to Hidora we were using AWS hosting solution. The big problem with Amazon is poor customer support and very high prices. You have to pay for instances, public IP addresses, traffic, backups, etc.

Customer testimonial

co-founder of DigiReward

“We paid 5x times more on AWS as we do now on Hidora. The pricing difference is huge and we are very happy with our current hosting bill.”

Reasons why you migrated to Hidora?

For all applications every spending is important. We paid 5x times more on AWS as we do now on Hidora. The pricing difference is huge and we are very happy with our current hosting bill.

Especially, taking into consideration the fact that Hidora provides us with an outstanding level of support. We are very happy about the individual approach to us as a customer.

In terms of performance, on AWS we had a pretty big instance and when we moved to Hidora we started to use very small instance but the performance stayed the same.

One of the main differences is how Hidora bills us: at AWS we were billed for VMs resources limits (RAM and CPU). We had to order more resources than we really needed to handle traffic spikes. These things changed when we migrated applications to Hidora. In contrast with AWS, Hidora charges us for resource usage, but not for limits. We use the same machine types, but it costs us less because of this cool billing policy.

co-founder of DigiReward

“Today I’m very satisfied with Hidora’s cost of hosting services, the level of support and the user-friendliness of the tool that every developer in my team can use without any training.”

Do you use horizontal auto-scaling in Hidora?

I consider that auto-scaling is an essential feature for seasonal businesses. As most of our clients are seasonal businesses (retail, and companies that have big traffic on holidays) the traffic differs from month to month. When we have low traffic, we don’t need a lot of resources to cover our needs. So we don’t need to worry that we will not cover the next traffic spike of millions of connections. Without scalability we would have to overpay for a large server, that we would actually not be using most of the time. Hidora is a very easy solution to make a scalable architecture.

How do you use pre-prod environments? Do you stop pre-prod environments when they are not needed to save money?

We have 2 pre-production environments : one for the team and one for the new customers. We schedule the internal pre-prod environment to be active starting from 8 a.m. and finishing when the last developer finishes his work. This saves money, as we are not using it during night time.

We also use pre-prod environments on Hidora to make demos of our application to prospective customers. In this case we start the pre-prod environments just for 2 hours and this provides dramatic money savings for us.

How your Dev and Ops processes changed after migration to Hidora?

Hidora is a very easy tool to use because of a simple dashboard where our developers simply create instances, comparing to the complex interface of AWS. After migrating to Hidora, our system administrators started saving time significantly on routine tasks like environment creation, database management, performance tuning and application server configuration. Currently we are also working on implementing a new CI/CD pipeline using Gitlab on Hidora.

Could you, please, describe your experience with Hidora?

Today I’m very satisfied with Hidora’s cost of hosting services, the level of support and the user-friendliness of the tool that every developer in my team can use without any training.

Also, I would like to mention that the documentation published by Jelastic covers the most important points. But if the documentation doesn’t cover my problem then the Hidora team answers any question I may have. I know I will always get an individual and personal approach.

Written by

Matthieu Robin Hidora
Matthieu ROBIN

Matthieu Robin is CEO at Hidora, an experienced strategic leader, a former system administrator who had managed and configured more environments manually than anyone on the planet and after understanding that it could be done in several clicks established Hidora SA. He regularly speaks at conferences and helps companies to optimize business processes using DevOps. Follow him on Twitter @matthieurobin.