ABOUT

I built Klos because I lived this problem.

PM · founder · Florida, US

THREE MOMENTS

The moments that built Klos.

A few years ago, my wife and I were apartment-hunting in a city we'd just moved to. The broker emailed for IDs, pay stubs, the last three months of statements, a letter from my accountant. I scrambled through inboxes and screenshots. The broker forwarded my reply — sometimes with their own attachments mixed in, sometimes with another applicant's information visible — to a landlord I had never met. I had no choice. I had no control. I hoped for the best.

A year later, I rolled up to a gate guard at a friend's community. License. Registration. The guard list with my name on it. I dug through my glove box and my phone for a minute and a half while the line behind me grew. The glove box, I realized, is not a document management system.

And not long after, the school called and asked for my daughter's most recent psych eval. It was somewhere in a seven-year-old Gmail thread, on a desktop I'd retired, in a cloud folder I'd renamed twice. The school needed it within the week. I knew I had it. I just couldn't find it.

THE RANGE ARGUMENT

Why now.

A twenty-two-year-old does not know what it feels like to scramble for a passport copy at a consulate, to reconstruct insurance records after a car accident, to wonder if the document your property manager is asking for is current. You have to have lived enough of life to know the problem is real — and to know it's recurring.

The other piece is timing. Klos is being built by someone who is old enough to need it, curious enough to understand how to build it, and in a moment in history where the gap between those two things has finally been bridged. One person — with an AI-native stack — can ship a product that a team of ten would have built ten years ago.

IN MY OWN VOICE

What Klos is — for me, first.

I built Klos to be the place my most important documents live — findable when I need them, fresh when I share them, mine when I revoke. The product is for me first, which means it's specific where it could have been generic, calm where it could have been dramatic, and honest about its limits where most vault products decide to oversell.

WHO KLOS IS FOR

If you've lived this, you know.

If you've lived a mortgage application, a school registration, a parent's hospitalization, a divorce, or a passport renewal under deadline pressure — you know the problem. Klos is for you.

If you're rebuilding after divorce →

WHAT KLOS REFUSES

The non-overlaps.

Klos is not a co-parenting tool. If you and the other parent need a court-mandated communication log, that's OurFamilyWizard. Klos is the other room — the one that's yours.

Klos is not a password manager. 1Password is for your Netflix login. Klos is for your passport. Use both — they solve adjacent problems with adjacent primitives.

Klos is not a Family Operating System. A household is not a small company. Klos does one thing — the documents that matter — and refuses the "operating system" framing the category drifts toward.

Klos doesn't overpromise. Only you can see your documents. Access ends when you revoke. What recipients do outside Klos is outside Klos's control — and we don't pretend otherwise.

How Klos is built →

GREYMOON

Klos is the first product of GreyMoon Ventures, my holding company. Based in Florida, US.

Get Klos.

Get Klos