01 / The question
It started with a fairly simple question.
Why am I relying on someone else's infrastructure to manage something as personal and important as my family's passwords?
Like most families, we have accumulated a growing number of digital accounts over the years. Banking, shopping, utilities, subscriptions, schools, government services, social media and countless other platforms.
Every service wants an account. Every account needs a password. And somewhere along the way, managing all those credentials becomes a problem of its own.
My wife and I use multiple devices. We each have personal accounts, but we also have services we share. We needed something that worked across our phones and computers, allowed us to share certain credentials securely, and didn't require us to keep track of which password was saved on which device.
There are excellent commercial password managers that solve this problem.
But I was curious.
Could I build something myself, using equipment I already owned, without introducing unnecessary complexity or another ongoing subscription?
That question eventually led me to self-hosting a password manager at home.
What I discovered was that the software was probably the easiest part.
02 / Digital independence
The attraction of owning a little more of our digital lives
Over the years, I've become increasingly interested in the idea of digital independence.
Not because I believe every online service is bad, or that everyone should operate their own infrastructure. Quite the opposite. I spend much of my professional life working with technology, and I appreciate how much value well-managed platforms and services provide.
But I also think we've become very comfortable outsourcing almost every aspect of our digital lives.
Our photographs, documents, communications, passwords and personal information are increasingly managed through services we don't own and systems we rarely think about.
That arrangement has enormous benefits. It also creates dependencies.
I wanted to explore whether I could take responsibility for one small part of our family's digital life.
Not to disconnect from the modern world, but to understand it a little better.
03 / What I already had
Starting with what I already had
My first instinct was to look at hardware.
A small dedicated server? A Raspberry Pi? Perhaps a refurbished mini PC?
There were plenty of possibilities, and I spent some time exploring them.
Then I realised something.
I already had an older laptop sitting at home.
It wasn't particularly powerful by today's standards, but it was perfectly capable of running Linux and a relatively lightweight application. It had a screen, a keyboard and even a battery.
Why buy something new when I could give an existing device another purpose?
That decision became one of my favourite parts of the exercise.
We often talk about technological progress in terms of acquiring something faster, newer or more powerful. Yet sometimes, meaningful progress comes from using what we already have more intelligently.
There is something satisfying about taking a computer that might otherwise be forgotten and giving it a useful second life.
04 / Discovering Vaultwarden
Discovering Vaultwarden
After exploring the available options, I settled on Vaultwarden, an open-source, self-hosted server implementation compatible with official Bitwarden applications.
It offered much of what I was looking for: personal password vaults, the ability to share selected items within a family organisation, and access through mobile applications and browser extensions.
Importantly, my wife and I could have our own accounts while maintaining a shared space for credentials we both needed.
We wouldn't need to share a single master password or place every family credential into one person's personal vault.
The application itself was relatively straightforward to get running.
I used Linux and containerisation to keep the service manageable, and a private networking solution to allow access from our devices without making the password manager publicly accessible on the internet.
I also enabled additional account authentication protections.
From a technical perspective, everything was starting to come together.
Then came the real-world testing.
05 / Making it work
The difference between installing something and making it work
This was probably the most valuable part of the whole experience.
Installing an application and seeing its login screen appear is satisfying. But it doesn't necessarily mean you've built something reliable.
A family password manager has to do more than run.
It needs to work when someone changes phones. It needs to work from different computers. Shared credentials need to appear for the right people. Authentication must behave consistently. And nobody should need to understand the underlying infrastructure just to retrieve a password.
We encountered a few unexpected problems along the way.
One mobile application behaved strangely after signing in. After some investigation, the issue turned out to be related to how an organisation membership had been confirmed.
Another challenge involved competing VPN configurations on a Windows computer. The password manager was perfectly healthy, yet a browser couldn't reach it under certain network conditions.
Neither issue was particularly glamorous.
But both reminded me of something I've encountered repeatedly throughout my career:
A system can be technically correct and still fail to deliver a good user experience.
It doesn't matter whether you're building a public-facing digital service or a small password manager for your family.
People experience the outcome, not the architecture.
06 / Backups and recovery
The real responsibility begins with backups
Once everything was running, another question became impossible to ignore.
What happens if the laptop fails?
Or if the storage becomes corrupted?
Or if I accidentally break something during an update?
It would be easy to become excited about owning the infrastructure while overlooking the responsibilities that come with it.
With a managed service, much of that responsibility belongs to the provider. When you self-host, it becomes yours.
So I spent time building an encrypted backup process using existing storage within my home infrastructure.
I wanted the system to back up automatically, retain recoverable copies of important data, and give me confidence that those backups weren't simply files sitting somewhere.
I tested backup integrity and restored data to a separate temporary location.
But there's an important distinction between confirming that backup data is readable and proving that an entire service can be recovered after a serious failure.
A complete recovery rehearsal in an isolated environment is still part of my plan.
And I think that distinction matters.
A backup is only as valuable as your ability to recover from it.
The same principle applies well beyond personal technology.
In organisations, we often celebrate successful implementation. But the real test of a system is how well it behaves when something goes wrong.
07 / Recovering after a restart
What happens when the power goes off?
Another interesting part of the experiment was testing whether everything would start properly after a restart.
I wanted to know whether the password manager, its supporting services and the secure network connection would recover without someone having to sit in front of the computer.
After configuring the services, I performed a controlled reboot and checked that the application, remote access and backup scheduling returned as expected.
It worked.
That might sound like a small achievement, but it changed how I thought about the project.
Up to that point, I had been building something.
Now I was beginning to operate something.
Those are two very different responsibilities.
A service that works while I'm watching it is one thing. A service that can recover from routine interruptions and remain usable by my family is another.
08 / The benefits
So, what are the benefits?
For me, the benefits extend beyond avoiding another subscription.
More control over where our information is stored.
I'm making deliberate choices about the infrastructure that hosts our family password vault, how it can be accessed and how its data is backed up.
A shared system designed around our family.
Each of us can maintain personal credentials while securely sharing selected accounts when needed. The experience can extend across the devices we already use.
Making better use of existing equipment.
Repurposing an older computer reduced the need for additional hardware and gave a useful second life to something we already owned.
The freedom to learn and adapt.
I can understand how the different components work together, refine the setup and make decisions based on our requirements rather than relying entirely on predefined service offerings.
A better understanding of digital resilience.
Perhaps the most unexpected benefit was how much the project taught me about backups, recovery, identity, remote access and operational responsibility.
These are principles I regularly encounter professionally, but applying them to something personal gave them a different significance.
09 / Is it actually better?
But is self-hosting actually better?
Not necessarily.
I think this is an important point to make.
Self-hosting doesn't automatically make a system more secure, more private or more reliable.
A reputable managed password manager may offer stronger operational resilience than something maintained at home by a single person. It may have dedicated security teams, established recovery procedures, independent assessments and infrastructure that would be difficult to replicate personally.
And there's a cost to self-hosting that doesn't always appear on a bill.
Time.
You become responsible for updates, monitoring, backups, recovery, hardware failures and the consequences of configuration mistakes.
You also need to think about what happens when you're unavailable.
In my case, that last point matters.
If I build a system that only I understand, have I really created a dependable solution for my family?
Or have I simply introduced a new dependency: myself?
That's something I'm continuing to think about as I strengthen the setup and prepare for the eventual migration of our everyday passwords.
A successful family system shouldn't require the rest of the family to become system administrators.
Technology should make their lives easier, not introduce another burden.
10 / Ownership and responsibility
The bigger lesson: ownership and responsibility belong together
This little project began with passwords, but it has made me reflect on something broader.
We talk a great deal about digital transformation, innovation, automation and the opportunities that technology creates.
We talk less about what it means to take responsibility for the things we build.
It's relatively easy to demonstrate that a system works.
It's harder to demonstrate that it's resilient, maintainable, understandable and genuinely useful to the people who depend on it.
That applies whether the system serves two people in a household or thousands of people across an organisation.
For me, the most satisfying part of this journey wasn't getting Vaultwarden installed.
It was gradually understanding the decisions behind it.
Why make access private? Why separate personal and shared information? Why automate backups? Why test a reboot? Why document the configuration? And, perhaps most importantly, why make sure the people using the system don't need to understand any of those decisions?
Each question made the solution a little more thoughtful.
And each answer reminded me that good technology is rarely just about technology.
11 / Would I recommend it?
Would I recommend doing this?
If you enjoy learning, experimenting and understanding how systems work, absolutely.
Self-hosting can be a rewarding way to develop practical skills while gaining more control over parts of your digital life.
But I wouldn't encourage everyone to start with their most sensitive information.
Begin with something less critical. Learn how private networking works. Understand backups and recovery. Get comfortable maintaining a service over time.
And be willing to acknowledge when a professionally managed solution is the better choice.
For my family, this is still a journey. The infrastructure is running, the core services have survived a reboot, and the next stage is to complete further recovery and security testing before moving our everyday passwords across.
I'm pleased with what I've built, but I don't consider the work finished simply because the application is running.
Perhaps that's the biggest lesson of all.
Digital independence isn't about owning every piece of technology we use. It's about understanding our dependencies, making deliberate choices and being prepared to take responsibility for those choices.
Sometimes that begins with something as simple as an old laptop and a question.
Could I build this myself?
And sometimes the most valuable thing you gain isn't the system you end up with.
It's everything you learn along the way.
12 / Further reading
Further reading
For anyone interested in exploring the technologies and principles discussed here:
- Vaultwarden: Open-source project. The password manager server that inspired this experiment.
- Bitwarden: Official applications. Cross-device password management applications compatible with Vaultwarden.
- Tailscale Serve. Providing private access to self-hosted services.
- Restic: Backups done right. Open-source software for encrypted, verifiable backups.
This article shares my personal experience and the thinking behind the project. It is not intended as a production security guide or a recommendation to replace a professionally managed password service without first understanding the responsibilities involved.