KeyPears Is Coming Home to Astrohacker

Password managers store secrets. Chat apps send messages. Email is federated but not end-to-end encrypted in any way that helps you hand someone a database URL without also handing it to a dozen intermediaries.

None of them do all three well: hold secrets under your key, send private messages across operators, and share a secret the way you share a DM—then let the recipient put it in their vault.

KeyPears does. It is a hybrid post-quantum federated end-to-end encrypted messaging system and password manager. The network shape is like email. The security baseline is built for 2026. And it is coming home under Astrohacker.

What KeyPears is

Short version:

• Messaging that is end-to-end encrypted by default, with hybrid classical and post-quantum crypto on the normal path—not a “secure mode,” not an enterprise checkbox.
• A vault for passwords and other secrets. The node stores ciphertext. Your client unlocks and encrypts. The operator of a node is not supposed to read your logins or notes.
• Addresses like email: name@domain. You talk to people on other domains the way email talks to other mail servers.
• Anyone can run a node. The network is multi-operator by design, not a single company silo wearing a federation sticker.
• Discovery and delivery follow an email-shaped architecture: domains, well-known configuration, pull-style delivery between nodes—not one global chat host that owns every conversation.

This is what “email for 2026” means in practice: the social model people already understand (addresses, domains, someone else’s server), without SMTP-era plaintext and without pretending a SaaS inbox is the same thing as a protocol.

We already said the hard crypto part out loud. KeyPears went hybrid post-quantum on the default path—every message, every signature, every account. That write-up is still the right reference for the construction: KeyPears Goes Hybrid Post-Quantum.

Already launched — now moving home

KeyPears is not a fresh pitch deck. It launched earlier as its own product surface in the Astrohacker portfolio—secret exchange, messaging, identity under one roof. See the portfolio intro and the fold-in note if you want the company timeline:

• Introducing Astrohacker
• Folding the Portfolio into Astrohacker

What is new is not the idea. What is new is where the work lives.

We are bringing KeyPears into the Astrohacker home—code, product path, and company front door at astrohacker.com. Legacy labels and older hosts can lag. Cutover is project by project. The direction is set: KeyPears belongs under Astrohacker, not as a permanent peer brand on a product mall homepage.

This post is a status report, not a product launch URL. No install checklist. No “sign up here” subdomain. When something is ready to use in public, we will say so plainly. Until then: capability and architecture first.

The password manager half

You get a vault. Names and types for list and search. Sensitive fields— usernames, passwords, free-form notes—live inside client-encrypted blobs. The node can help you find “the GitHub login” without knowing the password.

That is the boring half, and boring is good. A password manager that treats crypto as plumbing should feel ordinary: unlock, create, edit, lock.

The messaging half

You get private channels between addresses. Messages are end-to-end encrypted with the hybrid construction (classical and post-quantum together). Nodes exchange ciphertext. Opening a conversation can require proof of work at the recipient’s difficulty so spam is not free.

Federation is real work, not a slide. Same-domain delivery and cross-domain delivery are both part of the product story: Alice on one operator’s node can reach Bob on another, the way email works when two people do not share a host.

The server still sees addresses, routing metadata, and ciphertext. It does not get a free pass into the body of the message.

The part that matters most for developers

Passwords are table stakes. The interesting product is secret exchange.

Teams constantly need to pass:

• environment variables
• database URLs
• API keys
• service tokens
• other config that should never land in a public channel

Today that material travels through chat apps, email, paste sites, and “quick” screenshares. The history is searchable forever by the wrong people. The clipboard is a gossip protocol.

KeyPears treats a vault item as something you can send as a private message. The recipient sees a secret card, not a dump of fields in chrome. They can save it into their own vault, re-encrypted under their key, with enough provenance to know it came from a message—without the node reading the secret itself.

That loop—hold → share → receive → store again under a new key—is the product. It is why messaging and the vault are one system, not two apps glued together with a CSV export.

No federated system of this shape exists as a coherent product: hybrid post-quantum e2e messaging, client-encrypted vault, email-like multi-operator network, and first-class share a secret like a message. KeyPears is first because the stack is one protocol story, not a password manager bolted onto a chat SaaS after the fact.

Status: what is real now

Honest list.

Built and proven in the Astrohacker KeyPears path

• Account identity with address-shaped names and proof-of-work gates where spam would otherwise be free.
• Client-side vault unlock and encryption; ciphertext-only sensitive fields on the node.
• Hybrid post-quantum message encryption and signatures on the messaging path.
• Same-domain send/receive and federated delivery between nodes.
• Share a vault secret as an encrypted message; recipient optional save-to-vault.

In progress

• Folding KeyPears fully into the Astrohacker product home.
• Production packaging, discovery, and the open path for other people to run nodes with their own domains.
• Polish that turns lab-proven paths into something you install without a map.

Not this post

• A claim that a new public host is live today.
• A rebrand name announcement (old posts still say “Astrohacker Keys (TBD)” for a reason).
• SMTP replacement, mailing lists, or “we fixed compromised devices.”

If a device is owned or a password is weak, cryptography will not save you. If you need MIME and mailing lists, use email. KeyPears is for secrets and private messages under modern crypto—not for recreating 1995’s mail stack.

Why under Astrohacker

One of the through-lines of this company is that cryptography is plumbing, not a product category. Money systems and secret systems both need boring, defensible crypto so the interesting product can be something else: cash that moves, secrets you can actually share safely, agents and humans with identity under human control.

KeyPears is the identity, messaging, and secret-exchange layer of that picture. It already showed up as the protocol direction for how services talk when we wrote about EarthBucks network plans. Bringing it home to Astrohacker is the same unification story as the rest of the portfolio: one company brand, one front door, protocol-shaped infrastructure that other operators can run.

What to do

Follow the company blog and astrohacker.com. That is the home for status as KeyPears moves in.

If you care about the crypto baseline, re-read the hybrid post-quantum post. If you care about the company fold-in, re-read the portfolio unification post. If you care about the product: password manager and private messaging, with developer secret share as the wedge that neither email nor a siloed vault solves alone.

We are not inventing a new category label for a pitch. We are finishing a system that already had a launch and a protocol spine—and putting it where the rest of Astrohacker lives.

Hack the universe.