Relay13 and ConnectLog exist because every relationship needs a thread, a receipt, a workspace, and a next action. I do not want customer messages living outside the operating system.
Messaging / relationship OS · 📬 pain first
Relay13 + ConnectLog
Leads die in texts, emails, DMs, screenshots, and forgotten follow-ups.
Founder note
Why Gray built this lane.
What it does
The practical operating layer.
Client request inbox
This is not a brochure bullet. In the 0S, Relay13 + ConnectLog has to connect the user action to a route, a session, a receipt, or a handoff so the work can be trusted later.
ConnectLog relationship workspace
This is not a brochure bullet. In the 0S, Relay13 + ConnectLog has to connect the user action to a route, a session, a receipt, or a handoff so the work can be trusted later.
Durable/realtime messaging posture
This is not a brochure bullet. In the 0S, Relay13 + ConnectLog has to connect the user action to a route, a session, a receipt, or a handoff so the work can be trusted later.
AI response add-on boundaries
This is not a brochure bullet. In the 0S, Relay13 + ConnectLog has to connect the user action to a route, a session, a receipt, or a handoff so the work can be trusted later.
Competitor stack
How it stacks up without lying.
The comparison is category-level on purpose. Specialist tools are not bad; they are often excellent at the narrow job. The 0S argument is ownership, proof, shared auth, payment activation, and cross-lane context.
| Intercom / Zendesk | Strong support platforms. Relay13 wins when messages must connect to 0S workspaces and proof. |
|---|---|
| Slack / email | Useful communication. ConnectLog adds relationship memory. |
| CRM inboxes | Good sales context. Relay13 adds platform-native routing. |
Truth ledger
What we can say out loud.
✅ Runs as part of the 0S operating model, not as a loose side project.
✅ Uses the shared FS27/SkyGate/Free99 gate posture when mounted into the 0S.
✅ Needs proof receipts, owner visibility, and cost boundaries before it is sold as unlimited.
✅ Can be positioned strongly without pretending third-party primitives do not exist behind the scenes.
✅ AI replies need owner approval and caps.
✅ Messages should still route when AI is exhausted.
✅ Every inbound path needs a receipt.
Proof and receipts
What backs the page.
🧾 Production Relay13 proof
Relay13 + ConnectLog is marketed as part of a receipt-driven system. The proof may be a live route, a worker test, a browser proof, a stress run, or a platform truth file.
🧾 ConnectLog UI proof
Relay13 + ConnectLog is marketed as part of a receipt-driven system. The proof may be a live route, a worker test, a browser proof, a stress run, or a platform truth file.
🧾 WebSocket/proof receipts
Relay13 + ConnectLog is marketed as part of a receipt-driven system. The proof may be a live route, a worker test, a browser proof, a stress run, or a platform truth file.
🧾 FS27 contact ecology proof
Relay13 + ConnectLog is marketed as part of a receipt-driven system. The proof may be a live route, a worker test, a browser proof, a stress run, or a platform truth file.