// community

The Pock community runs on pock chat

No Discord. Our community lives on chat.pock.sh, the end-to-end encrypted chat we built on the same X-Wing key wrapping and signed-message crypto as the vault. If we won't trust our own product with our community, why would you trust it with your secrets?

Curious what actually happens to a message? See how pock chat works →

How to join

  1. 1

    Open pock chat

    Head to chat.pock.sh. The public community server is still being set up; its permanent invite link will live on this page.

  2. 2

    Sign in with your pock account

    Chat uses the same account as the vault. New here? Create an account. It takes a minute, and the free tier is plenty for chatting.

  3. 3

    Unlock and say hi

    Your keys unlock on your device, a member's client seals the room keys to you, and the channels open up. Messages you send are encrypted before they leave your browser.

this room is end-to-end encrypted

Every message in the community is sealed on your device and only members hold the keys. Our servers store ciphertext they cannot decrypt. Even channel names are sealed. Each member's keys are verified against pock's public, append-only key log, so the server can't quietly swap in its own.

The honest tradeoff: because the server can't read anything, there's no server-side search and nothing to browse before you join. When you first arrive, older history stays sealed until a member's client grants you the room keys. That usually takes moments, occasionally a short wait if the room is quiet. We think that's the right trade. It's the one we sell.

Come talk about

Get unstuck

Ask in #help about CLI setup, CI wiring, key recovery, or desktop quirks. Someone who hit the same wall will answer.

Shape the roadmap

Feature requests and workflow gripes land better in conversation. Tell us what pock should do next and why.

Ask the hard security questions

Skeptical of a crypto claim? Good. Bring threat models, audit questions, and “what if the server is evil” scenarios.

Show what you built

Share your agent pipelines, weird pock run incantations, and homelab setups. The best guides start as chat messages.

Bugs & security reports

Found a reproducible bug, or something that looks like a security problem? Email us with steps to reproduce. Security reports get priority; see the security page for what we promise in return.

Security at pock →

Prefer email?

Account trouble, billing, partnerships, or anything you'd rather keep one-on-one. Write to us and a human answers.

hello@pock.sh →