A month ago, I released ConfigMesh, a native macOS app that syncs your dotfiles and app settings across machines using end-to-end encryption. I spent months building what I felt was a solid product, complete with a zero-knowledge architecture, smart diffing, version history, and granular control over what gets synced.
When I launched, I tried the usual avenues like a DevHunt launch, Reddit sponsored posts, and Twitter boosts. Traffic came through, but downloads were sparse. People were landing on the site, reading the feature list, and then bouncing. It didn’t seem to be a problem of understanding what ConfigMesh does, but rather that the offer itself wasn’t quite right.
After a month of reading feedback, having conversations with users, and taking a step back, I recently shipped ConfigMesh 1.1. This post covers a couple of assumptions I got wrong and how I decided to adjust course.
Reassessing the price of syncing text files
I originally launched ConfigMesh at $5/month (or $50/year). From my perspective as the developer, that felt reasonable. I had built encryption infrastructure, a sync server, and a native macOS app over months of development.
From a potential user’s perspective, though, the math looked very different. Dotfiles are tiny. We are mostly talking about kilobytes of data, meaning a typical user’s entire config collection is smaller than a single iPhone photo. Paying $5/month to sync that amount of data felt disproportionate, regardless of the engineering that went into it.
I fell into a common pricing trap for indie developers. I priced based on what it cost me to build instead of what people were actually willing to pay. The perceived value of syncing text files has a hard ceiling, and $5/month was above it. It didn’t really matter that the encryption was robust or that the sync engine was smart. The sticker price created friction before anyone got to experience any of those features.
The clearest signal came from Reddit. I posted ConfigMesh on a Mac apps subreddit, and the feedback generally split into two camps. Some people said the price was just too high for what the app does. Others mentioned they didn’t want another subscription at all, regardless of the price. That second group was an interesting signal because it highlighted a preference for the business model itself rather than just the dollar amount.
For ConfigMesh 1.1, I dropped the subscription price to $1.99/month or $19.99/year. It is a significant cut, but I think it better matches where users anchor the value of this kind of tool. More importantly, the subscription is no longer the only option.
Trust and data ownership
ConfigMesh uses end-to-end encryption with a key that only you hold, meaning the server literally cannot read your data. From a cryptographic standpoint, it shouldn’t matter where the data is stored because it is indistinguishable from random noise without your key.
I assumed that technical guarantee would be enough for most users, but I was mistaken.
The feedback from Reddit made this clear. People weren’t just pushing back on the price, they were pushing back on the storage model. When I mentioned I was working on a Dropbox backend, the interest shifted noticeably. That was the option people actually wanted. They didn’t just want cheaper cloud storage, they wanted to use their own storage.
This makes sense when you think about how people view sensitive data. Ownership and control are emotional, not just technical. Saying “your data is encrypted on our servers” will always feel different from “your data is on your Dropbox,” even when the former is arguably more secure. You can’t just engineer your way past those feelings.
The deeper realization was that some users don’t need managed cloud storage at all. They already pay for storage like Dropbox, iCloud, or a NAS. They don’t want another cloud backend to manage. They just want the sync engine itself.
Adding Bring Your Own Storage
To address this, ConfigMesh 1.1 introduces a one-time purchase option with no included cloud storage. Instead, you can sync against your own Dropbox account.
There are some real tradeoffs here. Dropbox is generally slower than the managed backend and can be more error-prone. Sync conflicts are also harder to resolve gracefully when you don’t control the underlying storage layer. It is a compromise, but it is the compromise that users were asking for.
Your data on Dropbox is still fully encrypted. On disk, it just looks like encrypted blobs that are completely unreadable without your key.
Here is how the tiers work now:
- Subscription ($1.99/month or $19.99/year): Includes fully managed, encrypted cloud storage. This is the fastest and most reliable sync option. It is the same as before, just at a lower price point.
- One-time purchase: Includes the app but no cloud storage. You sync against your own Dropbox. It is a bit slower, but you own all the storage.
If you are on the one-time purchase tier and try to use the managed ConfigMesh backend, you will see a clear upgrade prompt instead of a confusing error.
Dropbox is the first supported provider, and I plan to add more in the future.
Takeaways
If I could go back to the launch, I would try to validate my pricing assumptions as cheaply as possible. I could have launched with a lower price and a free trial to test willingness to pay before building so much conviction around a $5/month price point.
I also learned that when users tell you they don’t trust something, it is better not to argue with their reasoning. Just give them an alternative they are comfortable with. Sometimes the best feature you can build is just getting out of the way.
ConfigMesh 1.1 is available now at configmesh.app. If you tried it before and bounced on the price or the storage model, I hope you will give it another look.