<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Qerron]]></title><description><![CDATA[Qerron]]></description><link>https://qerron.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Fri, 20 Nov 2026 17:16:33 GMT</lastBuildDate><atom:link href="https://qerron.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Passkey vs password: what actually changes]]></title><description><![CDATA[A password is a shared secret you can type into the wrong site. A passkey is a key on your device, used for a specific site.]]></description><link>https://qerron.hashnode.dev/passkey-vs-password</link><guid isPermaLink="true">https://qerron.hashnode.dev/passkey-vs-password</guid><category><![CDATA[passkeys]]></category><category><![CDATA[Security]]></category><category><![CDATA[privacy]]></category><category><![CDATA[password manager]]></category><category><![CDATA[cybersecurity]]></category><dc:creator><![CDATA[Sara Larson]]></dc:creator><pubDate>Wed, 18 Nov 2026 15:36:36 GMT</pubDate><content:encoded><![CDATA[<p>If you already use unique passwords, a manager, and a second factor, the next question is the one behind the manager itself: what unlocks it, and what happens if that secret is guessed, reused, or typed into the wrong site?</p>
<p>That is the real difference in a passkey vs password comparison. It is not a new coat of paint on the same secret. It is a different kind of unlock.</p>
<h2>A password is a shared secret.</h2>
<p>You invent a string. You and the service both know it, or the service stores a value derived from it. To sign in, you type that string — or a manager types it for you — into a form. If the form is on a lookalike site, you have just handed the secret over. If the same string is reused elsewhere, a leak in one place can open another. If it is the master password for a vault, it is the one secret that opens the rest.</p>
<p>None of that makes passwords foolish. They are how most of the web still works. It does mean the risk sits in the secret itself: something that can be typed, copied, phished, or replayed.</p>
<h2>A passkey is a key, not a string you type.</h2>
<p>A passkey uses public-key cryptography. The private part stays on your device, or with the password manager your operating system already provides. The site stores only a public key. When you sign in, your device proves you are present — Face, fingerprint, or a security key — for that specific site. A lookalike page on another domain does not get a reusable secret, because there is not one to type.</p>
<p>If you have used a passkey on a website before, the prompt will feel familiar. You are not inventing a new string. You are approving a sign-in with something you already have.</p>
<h2>What this means inside Qerron.</h2>
<p>Qerron is a <a href="https://qerron.com/blog/password-manager-without-master-password/">password manager without a master password</a>. You sign in through Internet Identity with a passkey. We do not keep a password database of ours to leak. The vault still has a lock. The lock is the passkey, not a string you have to invent, write down, or keep from being typed in the wrong place.</p>
<p>Items in the vault are encrypted on your device with vetKeys threshold encryption before they are stored. We cannot read them, and no single server can either. The sign-in method and the storage method are separate jobs. Both are described in <a href="https://qerron.com/how-it-works/">how a passkey vault works</a>.</p>
<h2>What this is not claiming.</h2>
<p>A passkey is not a promise that a product is unhackable. Devices can be lost. You should register more than one way to sign in, the way you would keep a spare key. Qerron does not remove the need to be careful about where you send a <a href="https://qerron.com/blog/share-a-password-securely/">sharing link</a>, or about whom you name for <a href="https://qerron.com/emergency-access/">emergency access</a>.</p>
<p>It does remove the master password from the middle of the product: no new secret to memorize, and nothing reusable to steal in a phishing mail just to open the vault. You can try the full product for fourteen days, with no credit card required. Personal is $48 a year. Household is $72 a year.</p>
<p><a href="https://qerron.com/">Try it free for 14 days</a>, no credit card needed.</p>
<hr />
<p><em>Originally published at</em> <a href="https://qerron.com/blog/passkey-vs-password/"><em>qerron.com</em></a><em>.</em></p>
]]></content:encoded></item><item><title><![CDATA[Why I build on the Internet Computer]]></title><description><![CDATA[I built Qerron on the Internet Computer because I wanted the vault to live in a place that is not one company’s private servers. Every time a large cloud…]]></description><link>https://qerron.hashnode.dev/why-i-build-on-the-internet-computer</link><guid isPermaLink="true">https://qerron.hashnode.dev/why-i-build-on-the-internet-computer</guid><category><![CDATA[internetcomputer]]></category><category><![CDATA[passkeys]]></category><category><![CDATA[privacy]]></category><category><![CDATA[Security]]></category><category><![CDATA[Web3]]></category><dc:creator><![CDATA[Sara Larson]]></dc:creator><pubDate>Tue, 17 Nov 2026 14:36:12 GMT</pubDate><content:encoded><![CDATA[<p>I built Qerron on the Internet Computer because I wanted the vault to live in a place that is not one company’s private servers.</p>
<p>Every time a large cloud has a bad day, the same pattern shows up. Mail stalls, logins fail, admin pages will not load, and the people who depend on those tools wait on a fix they do not control. I wrote about that pattern when I first published <a href="https://qerron.com/blog/when-the-cloud-goes-down/">When Microsoft goes down, half the internet goes with it</a>, and in more detail — with official incident reviews cited — in the notes that followed. The point was not that one company is uniquely careless. The point was concentration: too much of the world’s access sitting behind too few control planes.</p>
<h2>No single point of failure, as a design choice.</h2>
<p>The Internet Computer is a public network of subnets, run by independent node providers, that agree on state through a consensus protocol. Official documentation describes how a canister is replicated across the nodes of its subnet, and how chain-key cryptography splits a subnet’s key so no one node holds the whole secret. I wanted Qerron to be a canister on that network, not a database on a rented machine in one vendor’s region.</p>
<p>That does not mean the network can never have a problem, and it does not mean the product is unhackable. It means the failure domain is different. A configuration change in one company’s edge fleet, or an outage in one company’s identity system, is not automatically the same event as the vault being unreachable. For a sourced walk through that architecture, see <a href="https://qerron.com/blog/what-is-the-internet-computer/">what the Internet Computer Protocol is</a> and <a href="https://qerron.com/blog/microsoft-outage-how-the-internet-computer-is-built/">how the Internet Computer is built</a>.</p>
<h2>Cost, and sovereignty.</h2>
<p>On a conventional cloud, a small product can quietly become a stack of separate bills: compute, storage, a database, a content network, an identity service, and the surprise that shows up when traffic spikes. On the Internet Computer, the canister pays for its own compute and storage with cycles. Official documentation says users interact with apps for free, the way they use any web service: the people using the app are not asked to buy fuel to click a button. For me, the practical hope is straightforward, predictable cost, without piling up a new vendor each time the product needs a door.</p>
<p>Sovereignty is the other half. I did not want the vault — the logins, the notes, the plan for the person who should open it if you cannot — to sit only on a landlord’s servers, under terms that can change, in a place I cannot move without starting over. The Internet Computer is a public network. The app and its data are not a tenant in someone else’s account. You can also <a href="https://qerron.com/blog/what-qerron-can-do/">export your data</a>. If we ever shut the company down, the plan is that the canisters can keep serving the vault.</p>
<h2>What I actually built.</h2>
<p>Qerron is a private passkey vault. You sign in with a passkey, not a master password. Items are encrypted so we cannot read them. You can share a vault with a one-time link, and set a named-person check-in so someone you trust can be let in if you stop checking in. It is a storage and access tool. It is not a will, not legal advice, and not a custodian of your assets.</p>
<p>I am Sara Larson, founder and president of Qerron. If you want a short, factual page about me, see <a href="https://qerron.com/about/">About the founder</a>. If you want to try the vault, you can start a 14-day trial with no credit card required. Personal is $48 a year. Household is $72 a year.</p>
<p><a href="https://qerron.com/">Try it free for 14 days</a>, no credit card needed.</p>
<hr />
<p><em>Originally published at <a href="https://qerron.com/blog/why-i-build-on-the-internet-computer/">qerron.com</a>.</em></p>
]]></content:encoded></item></channel></rss>