Imagine it runs an invoicing service on AWS with Maestro

This case study features Imagine it. Since 2021 Imagine it has deployed the Rails application with Cloud 66 Maestro on AWS.

Imagine it

Can you tell us about the infrastructure set up before you moved to Cloud 66?

To make life a bit easier we migrated our co-located server to a VPS. The benefits we wanted were the ability to scale the server as we grew, to be able to take snapshots, and also to quickly fire up a new server in case of emergency. Things felt a bit safer but snapshots required the server to be offline for some time so it only became a tool for disaster recovery and not something that helped us in our day-to-day work. We also suffered from the outages of our cloud provider. Usually, the interruptions were brief so there was no point in moving all systems to another data center but we felt helplessly out of control over the availability of our apps. The long term solution would be to move to some kind of redundant setup (High Availability). We also wanted to outsource as much of the sysops as possible and started to look for alternatives:

Engine Yard

+ They know Rails

- Expensive

-The platform felt outdated


+ Also known to make Rails hosting simple

- Expensive

- Inflexible

- Didn’t support the new AWS region in Sweden

Managed hosting

- You have to find the right partner

- The partner would need to know a lot about our services to make a redundant solution work good


- Felt outdated and unreliable


- Too complicated if we had to set up everything ourselves

We then stumbled upon Cloud 66 and it looked very promising.

+ They know Rails

+ The platform felt up-to-date

+ Flexible hosting

+ Affordable pricing

Why did you choose Maestro Kubernetes?

How easy or complicated was the migration to Cloud 66?

For the database layer, we chose to use AWS Aurora and not the database service provided by Cloud 66. Fast automatic failover and file system level replication across 3 availability zones fitted in nicely with our plans to get High Availability.

Once all preparations were done (all file system dependencies migrated to ActiveStorage) the actual server migration went smoothly. We only had to migrate our database to Aurora and then switch the traffic to Cloud 66.

Now that all systems are up and running we finally feel that we have a hosting solution that is maintainable in the long run. Having all our apps running in Maestro gives us a great overview and control through the Cloud 66 dashboard. It’s wonderful how simple they make it to add Failover Groups, Load Balancers, SSL, etc.

Lastly, what are Imagine it future plans?

Originally published at on June 16, 2021.

DevOps-as-a-Service to help developers build, deploy and maintain apps on any Cloud. Sign-up for a free trial by visting:

DevOps-as-a-Service to help developers build, deploy and maintain apps on any Cloud. Sign-up for a free trial by visting: