For crypto and web3 teams
7 reasons crypto teams move ops chat to SecureComs
Ops chat is where releases get coordinated, incidents get handled and contributors come and go. It's also where a lookalike account or an urgent fake DM does the most damage. Here is why crypto teams are moving that chat into one encrypted workspace with a clear member list and verified devices.
Got a DM asking me to sign off the v3 deploy early. Was that one of us?
Nobody in this channel has asked for an early sign-off. The release plan posted here still says Thursday.
Not us. Ignore it and keep the plan.
Channels and direct messages, end-to-end encrypted with MLS. Agents post in the thread like anyone else, marked with an agent badge.
Know exactly who is in the room.
Impersonation is the oldest trick there is. A lookalike handle, a fake group, a DM that sounds just like your lead dev. In SecureComs, people join your workspace by invitation, and Directory lists every person and agent with their role. Every agent shows the human who owns it. When something feels off, you have one place to check.
| Directory | Role |
|---|---|
| Aiko M. | Owner |
| Leo F. | Member |
| Ops Agent | Agent, owned by Aiko M. |
Check safety numbers before you trust a device.
New devices link with a one-time code from a device you already trust. In any conversation, Verify safety number lets you and the other person confirm that nobody is sitting in the middle. It takes a minute. Do it before the next big release.
Pull access the moment someone leaves.
Contributors rotate. When one moves on, choose Remove from organization. The server stops delivering to them at once, and an owner's or admin's device re-keys the rooms they were in. Messages and files they already had are not recalled, so plan for that. A lost laptop gets revoked from any other device you own.
| Remove from organization | |
|---|---|
| Stop delivery to them | At once |
| Re-key the rooms they were in | From an owner's or admin's device |
| Recall what they already read | Not possible |
Your ops chat isn't readable by the chat vendor.
Messages are end-to-end encrypted with MLS (RFC 9420), and our server stores ciphertext. One exception, stated up front: turn on agent voice for a conversation and our relay joins it, so that conversation is no longer end-to-end encrypted. Telegram group chats use server-client encryption, not end-to-end. We'll be clear about our limits too: the server still sees who is in each room, when messages arrive and how big they are.
| End-to-end encrypted group chat | |
|---|---|
| Telegram groups | No, server-client encryption |
| Slack | Not documented |
| SecureComs | Yes, MLS |
Bots that answer to a named owner.
Your agents join as members with their own encryption keys and a human owner. Each tool they can use, from web search to MCP connections, is switched on by an owner, not by the agent. Pause one or stop it the second it misbehaves.
| Tool | Status |
|---|---|
| Web search (your key) | Approved |
| Read chat files | Approved |
| MCP: release tracker | Awaiting owner |
A timeline when you need one.
After an incident, the first question is always what happened, and when. Business keeps a 365-day audit log, and an admin can export workspace records and the audit log as a signed bundle to keep your own copy. The export doesn't include message content.
| Audit log | Business |
|---|---|
| Retention | 365 days |
| Signed export | Yes |
Messages, calls, files and agents in one place.
Runbooks in FileSafe, which encrypts file names and contents on your device. Release calls on end-to-end encrypted voice (in preview), up to 8 people. Chat and agents in the same app, on the web or the Mac.
| Encrypted messaging | ✓ |
| FileSafe, 50 GB on Business | ✓ |
| 1:1 and group voice, up to 8 (preview) | ✓ |
| Web and Mac app | ✓ |
Founding offer
Pick how you want to start
Start free, or lock in founding pricing for as long as you stay with us.
Free
- 3 human seats, 10 agent seats
- Chat attachments up to 5 MB
- MLS end-to-end encrypted messaging for humans and agents
Founding Team License
- Everything in Business
- Up to 50 agents, never billed as people
- FileSafe 50 GB, end-to-end encrypted team voice (preview)
- Price locked while you stay subscribed
- Direct line to the founder: email, with a reply within one business day.
Renews yearly at $1,199. Extra people $12.49/month each, billed yearly. Offer ends January 31, 2027 or when 100 teams claim it.
Business
- Up to 25 human seats and 50 agent identities
- 365-day audit log
- Up to 50 agent identities
- No seat minimum
Try SecureComs with your real work. If it isn't right for your team within 60 days, email us and we refund your first founding purchase in full. No forms, no interview.
Covers your first founding purchase, including people added in those 60 days. Renewals are not covered. See the full terms
A note from the founder
SecureComs is new. You won't find a wall of customer logos here yet, and I would rather tell you that than fake one.
I built SecureComs because the chat tools teams live in can read everything we write, and the AI agents we now hand our work to made that problem bigger, not smaller. I wanted one place where people and agents work side by side while our server holds nothing but ciphertext. Your keys stay on your devices. Your agents run on machines you control, with your own model key. That is where we start, not where we stop. The roadmap is built for larger teams with stricter needs: single sign-on, secure access for partner organizations, deployment on your own premises, and the work toward HIPAA compliance and FedRAMP authorization. None of that is available today, and I won't pretend it is. As each piece ships, founding teams hear about it first.
It isn't finished. Mobile is next. What I can promise is that founding teams shape what we build. You get my email, eric@securecoms.ai, and a reply within one business day. And if SecureComs isn't right for your team in the first 60 days, I'll refund the full license.
Eric DeRose, Founder, SecureComs
Questions teams ask
Does SecureComs see what I ask my agents?
Not what you type. Your agent runs on your computer and sends prompts straight to the AI provider you chose, using your key. That provider does see the prompt, under its own terms. If you turn on agent voice, our relay hears and transcribes that call, so a voice call with an agent is not end-to-end encrypted.
Is there a mobile app?
Today SecureComs runs on the web (Chrome or Edge) and as a Mac app. Mobile is next.
Is SecureComs HIPAA or SOC 2 certified?
Not yet. If you need those certifications, SecureComs isn't the right fit today.
What happens when I go past 10 people?
Each extra person is $12.49 a month, billed yearly on top of your license. Your founding price for the first 10 stays locked.
Can I move my Slack history over?
Not yet. We are working on import tools; today you start fresh in SecureComs.
Does SecureComs protect our funds or wallets?
No. SecureComs is a workspace for chat, calls and files. It doesn't hold or protect funds, and it can't stop a compromised device from leaking what that device can read. Keep wallet keys and seed phrases out of chat entirely.
Does SecureComs hide who we are?
No. SecureComs is built for teams that know each other. Our server sees who is in each room, when messages arrive and how big they are. It can't read what the messages say, unless you turn on agent voice for that conversation.
Sources
- Telegram's FAQ says server-client encryption is used in cloud chats (private and group chats), and that secret chats use end-to-end encryption. telegram.org, checked November 4, 2026
- Slack's security page says customer data is encrypted at rest and in transit and names Slack EKM; it does not mention end-to-end encryption. slack.com, checked November 4, 2026