cirrux

Who is behind Cirrux?

I'm Rick Pastoor, the founder of Cirrux. Is this whole thing run by one guy? Mostly, yes. What started as a side project in 2025 grew into a full-time thing, and these days I work with a small group of freelancers too. But before I tell you how I think about that, let me briefly tell you how I got here.

I'm a software engineer at heart. My first company was building web apps, co-founded with a friend during my studies. We turned that into a successful business, building custom web applications for clients. We built the first generation native mobile apps for iOS and Android, we built games in Flash and we created fun integrations with early Twitter.

After that, I joined Blendle as a frontend engineer. After a few months, this turned in to a product role, where I was responsible for leading six teams of engineers to build the platform to help people find and pay for the best journalism in the world. A lot of fun.

While I was working at Blendle, I started writing and publishing articles about productivity and self improvement. I'm skipping over a few things here, but this ultimately turned out into a book called GRIP, which I self-published in 2019, and sold over 130,000 copies worldwide.

Working on GRIP made me think a lot about time and calendars (the calendar is the centerpiece of the book), so naturally I started working on a calendar app. It was called Rise, and together with a brilliant team we spent a few years learning the ins and outs of managing time, integrating with all kinds of other apps, building highly responsive UI and a thousand other things. I wrote a long piece on what happened with Rise, which you can find on the old website.

That brings us to Cirrux, because after wrapping up Rise, I started thinking about what to work on next. Building a full workspace, after spending so much time on just the calendar, was not high on my list initially. But after seeing the huge shift in demand for native European tools, I figured that this was a real opportunity to truly build something new and different in a space that is notoriously hard to break into.

Will Cirrux still be around in five years?

Folks ask me a lot: Cirrux started as a one-person company, how sustainable is that? And what happens when you're not around? Questions that make a lot of sense, especially when you're about to move your company's mail somewhere new. Here's how I think about it.

Who pays for this. Cirrux is self-funded. There are no investors and no outside shareholders, so nobody can push me to grow faster than I can support, or to do dramatic things to close a next funding round. Customers pay for Cirrux, and that's the business. I also believe the next generation of companies doesn't need hundreds of people. My goal is a small and passionate team that uses the leading edge of AI to do a lot of the heavy lifting.

If something happens to me. Cirrux is no longer just me: Arnoud Vermeer joined the team for infrastructure. He knows the system, and if I can't do it, he keeps Cirrux running for at least six months, tells every customer what is going on within a week, and helps anyone who wants to leave take their data with them. For security I work with outside specialists. On top of that, I'm leveraging an optional escrow service to ensure source code access if something would happen to me or the company, which is especially relevant for larger companies.

If something happens to the company. Your content is yours, and the terms say so. We only process it on your behalf. If Cirrux were ever sold, the buyer takes over our agreement with you on the same terms. Your data is not an asset someone can buy and then do something else with.

Getting your data out. Mail, calendars, contacts and tasks all run on open standards (IMAP, CalDAV and CardDAV), so any compatible app can make a full copy at any time, without asking us. There's also a public API and an open source command line client. A one-click export of everything is on the list.

What Cirrux is built on. The mail servers (IMAP and SMTP), the calendar server, the sync engine and the apps are our own code, written from scratch. They run on widely used open source foundations like PostgreSQL and Ruby, but Cirrux is not a repackaged open source suite. Two outside components handle specialist jobs: rspamd for spam filtering and ClamAV for virus scanning. Both brilliant pieces of software that do a fantastic job at their specific tasks. Both run on our own servers in Frankfurt. The full list of companies that touch any of your data is in the privacy policy.

The last few months have been a lot of fun, and I'm grateful for all the support from the community. Can't wait to see where this grows into. If you have questions or thoughts, feel free to reach out. Happy to chat.

—Rick Pastoor