Why I left my corporate job to build Bitflake

I have recently left my corporate job to start my own thing. That new thing is Bitflake.

I have always liked building things. I started with electronics at school and progressed through Android development, frontend, full stack, infrastructure, and eventually building teams. Now I want to take the next step and learn how to build a business.

Open source has always been part of my work

Open Source Software has always been a big part of my career. Most of the tech developers use is built on OSS. However, outside of the developer community its impact and strengths are less known.

With data sovereignty being on everyone's mind, especially in Europe, there is increased attention on open source. There are some great OSS alternatives out there that let you control exactly where your data is stored and processed. Nextcloud instead of Dropbox. Mattermost instead of Slack. OnlyOffice instead of Microsoft Office. These aren't hobby projects — they run in governments, universities, and banks across Europe.

The problem is complexity, not the software

But unless you know what Docker is, you will struggle setting up your own server. Running it at scale and keeping it updated and secure adds another layer of complexity. For most businesses, that's enough to make self-hosting a non-starter, even when they'd genuinely prefer to keep their data close.

That's why I am building Bitflake. I want to make it as simple as possible for businesses: one click to deploy open-source alternatives to your SaaS stack, running on infrastructure in your country, with one login for your whole team.

I'd love to hear from you

I am still in the building and validation stage of my journey, and would love to hear from you — especially if you work in a professional services firm and want to stop sending your data to US tech giants, or you've been asked where your data is stored without a good answer.

Have you ever worried about where your tools process and store your data?