Why I Finally Ditched Cloud Notes and Went Self-Hosted with Docker

I’ve spent the last few years jumping between note-taking apps like some kind of digital nomad. OneNote, Notion, Evernote, Obsidian, Apple Notes—you name it, I’ve probably given it a shot. Each time I’d think, “This is it. This is the one.” Then something would break my workflow, or I’d worry about vendor lock-in, or I’d realize I was paying for features I’d never use.

The real breaking point came when I realized I had no idea where my most important notes actually lived. Some in Microsoft’s servers, some in Notion’s infrastructure, some scattered across different devices. If any of these companies decided to pivot their business model or shut down a service, my data was at their mercy. That’s when I discovered Docker, and honestly, it changed how I think about self-hosting entirely.

The Problem With Trusting Someone Else’s Infrastructure

Let’s be real: cloud services are convenient. They’re designed to be. Sync across devices? Check. Access from anywhere? Check. Zero maintenance? Absolutely. But that convenience comes with a hidden cost, and I’m not just talking about monthly subscriptions.

When you store your data with a cloud provider, you’re making a bet. You’re betting that:

• The company won’t get acquired and gutted
• Their security practices will hold up forever
• They won’t change their pricing model
• They won’t shut down the product
• Their servers won’t experience a catastrophic failure

Any one of these bets can go sideways. I’ve watched Evernote stumble through years of mediocre updates. I’ve seen Notion’s pricing climb steadily while feature parity with competitors improved. These are good companies, but they have shareholders, board meetings, and changing priorities. Your note-taking app isn’t their core business—profit is.

The other thing nobody talks about is the psychological toll of not owning your data. There’s this low-level anxiety that sits in the back of your mind. What if they lock me out? What if I need to export everything? What if the export format is broken?

Docker Made Self-Hosting Actually Feasible

Here’s what I didn’t understand before: self-hosting used to require serious technical chops. You needed to manage servers, handle updates, deal with security patches, set up backups—it was a whole job. I’m a founder who ships products, not a DevOps engineer. I don’t have time for that.

Docker changed the equation completely. Instead of wrestling with installation scripts and dependency hell, you run one command. One. Then your application is running in an isolated container, and it just works.

The beauty of Docker is that it packages everything your application needs—the code, the runtime, the dependencies, all of it—into a single unit. You don’t have to install anything globally on your server. You don’t have to worry about version conflicts. You just pull the image and run the container. If something breaks, you spin up a new one.

For someone like me who wants to own their data but doesn’t want to become a system administrator, Docker is the bridge. It’s simple enough to actually use, but powerful enough to run serious applications.

What Self-Hosting Actually Gives You

Once I set up my self-hosted note app using Docker, the benefits became obvious pretty fast.

First, the data anxiety disappeared. My notes live on a server I control. I have the backups. I have the access logs. If I want to switch to a different note app in five years, I can export everything. No vendor is going to lock me out or change their terms of service and force me to pay more.

Second, I can customize the hell out of it. I’m not limited to whatever features the company decided to build. If I need a specific integration or workflow, I can modify the code or add extensions. That freedom is intoxicating when you’ve been using commercial products for years.

Third, the performance is actually better. No syncing delays. No waiting for their servers to respond. Everything is instant because it’s local or it’s your own infrastructure. That might sound like a small thing, but when you take thousands of notes, speed matters.

Fourth, and this is weird to admit, there’s genuine satisfaction in owning the infrastructure. I know what I’m running. I know where the data lives. I know exactly who has access. That’s not paranoia—that’s just being responsible with your own information.

The Real Story Here

The article title mentions giving up on cloud note apps “one Docker command later.” That’s exactly right, and it’s the part that matters. Docker made the possibility of self-hosting accessible to regular people. Not just engineers. Regular people.

I’m not saying everyone should self-host their notes. If cloud apps work for you, go for it. But if you’ve ever felt that nagging doubt about where your data really lives, or if you’ve ever thought about what happens when a service shuts down, Docker gives you an actual alternative. Not a theoretical one. A real, working alternative you can deploy in minutes.

The startup world taught me that the best tools are the ones you actually use and trust. I trust my own infrastructure more than I trust any company’s promises. That’s worth the minimal effort Docker requires.

Source: After testing every OneNote alternative, this self-hosted tool is the only one I trust with my data