Hi Alin! What's your background, and what are you currently working on?
Aloha! I’m Alin Dobra (29) and I’m the CEO & Founder of Bunnyshell, a SaaS startup for applications that really need near 100% availability and reliability. I have more than 10 years of experience in building big projects and I love to automate things. I am very passionate about everything about technology, marketing, sales, and psychology.
I started working in software engineering in 2011, became the CTO and then CIO of a conversion marketing company and decided to build my own cloud tools once I realized the product I needed didn’t exist.
So I created Bunnyshell, with a seductive proposition: set up your servers across different cloud platforms in just a few clicks. Automate, launch, and provision, deploy, monitor, scale, and stay secure. No time wasted, no specialized and expensive sysadmins required, no testing needed, no hidden costs. No headaches, just cloud.

We launched Bunnyshell in March 2018, got a €750K investment in under 18 months, and today we provide services to corporate clients all over the world.
What's your backstory and how did you come up with the idea?
When I was 23, I was promoted to CTO at an outsourcing development company, a Magento & Symfony partner, and I had to manage the relationship with customers and a team of over 30 people. Basically, I was a child with a lot of responsibilities.
I didn’t know what my attributes were, so I started reading about it. What it really meant to be a first-time CTO. And from this research, I found something very interesting and valuable. Something truly WOW that guided me in the next few years:
“The CTO should have a plan for everything. For everything that happens wrong, it’s his fault.”
So I started to learn and do whatever it took to make things happen: recruitment, HR, retention, sales, account management, development, sysadmin, DevOps, etc.
In the next few years, I learned and tested a lot of things in real-life, and I kept following the same motto: that I needed a plan (which sometimes involved plans A, B & C) for everything. It’s this attitude that helped me become a Managing Partner at that great company.
After I worked out how to create teams and build software, I found myself wanting more. I wanted to build products, to find solutions for real use cases and problems, to make a contribution to the rest of the world.
So I left the company and joined a startup in the marketing space, a product designed for eCommerce, which improved conversion rates through A/B testing, personalizations, and popups. This was also the first time I’d ever heard of anything related to A/B testing, user personas, conversion rates, micro conversions, funnels, and a lot more terms and acronyms widely used in the marketing industry. It was a challenge that I wanted and was ready for.
Once the business started growing, it also became challenging from a technical perspective: more than 200k requests/minute, more than $15K/month at AWS. So I reached out to Microsoft and we became a part of their startup program, which landed us some credits (some, as in more than $100K - so thank you, Microsoft!)
We only needed to migrate our infrastructure from AWS to Azure to start saving $15K/month. So I started looking for a way of doing this that would allow us to operate our infrastructure after the migration in the same way as we did in AWS.
And I was very intrigued to find that this type of platform didn’t exist.
Since I wasn’t having any luck and because I really didn’t like having to depend on other people (remember - I was the guy with the plans) and I love automation, I created the tools internally. From provisioning to deployment, monitoring, and alerting. We successfully migrated from AWS to Azure and created our tools to manage the infrastructure - but this migration took 4 months!
You could call this my A-ha moment: when I realized that this type of tool needed to be created. A platform that took care of the exact same things every app needs, everything sysops related: provisioning, monitoring, alerting, backups, autoscaling, etc.
Who doesn't need backup or security or uptime? We all want the benefits of automation - not to automate again and again and again. Why reinvent the wheel over and over again?





