Kemble Work · Kemble Circle
One platform. Two surfaces.
Kemble Work runs your company. Kemble Circle runs your community. They share every piece of machinery below the shell — messages, threads, files, search, voice, permissions — so an improvement to one is an improvement to both.
Kemble Work
Kemble Circle
One frame, split down the middle. Both halves are the same components reading the same tokens — the difference is thedata-surfaceattribute, and nothing else.
Two products, one engine
Kemble Work
For companies. Internal channels, threads, files, search, voice and automation, with a permission model and an audit trail built for a security review.
- Public, private and announcement channels
- Threads, reactions, mentions and unread state
- Full-text search that respects private channels inside the query
- Roles resolved through organization, space and channel
- An audit log the organization can actually read
Kemble Circle
For communities. Spaces, roles, voice stages, invite codes and a moderation toolkit that exists rather than being promised.
- Categories, roles and per-channel permission overwrites
- Timeout, remove and ban, each with a recorded reason
- Stages where speaking is a separate permission from listening
- Shareable invite codes with an expiry
- Free, on the free plan, deliberately
K Buddy
The answer arrives where the question was
Every chat product has an assistant now, and almost all of them put it in a side panel — so the answer cannot be shown to anybody else, cannot be replied to, and vanishes when the panel closes.
Mention K Buddy in a channel and it answers in that channel, to everybody who can read it. It sees exactly what you see and no more, so an answer in a room is bounded by the person who asked for it.
Priya
@kbuddy what did I miss this morning?
K Buddyanswered here
Three things: the staging deploy is green, Ana moved the review to Thursday, and nobody has picked up the pricing copy yet.
Built the way it claims to be
Four things that are true of the code, not of the brochure.
- Real time, without a refresh
- One socket carries messages, typing, presence and voice state for everything you can see. Presence is reference-counted per account, so a second device disconnecting does not mark you offline.
- Permissions that resolve, not permissions that are declared
- A closed catalogue shared by the server and every client, resolved through a scope chain with per-channel allow and deny applied last. A deny wins at every layer.
- Nothing crosses a tenant boundary
- Every tenant-scoped route resolves the organization from the session before it reads, and a foreign id answers 404 rather than confirming what exists.
- Limits you can read before you hit them
- The pricing page fetches the same plan catalogue the enforcement code reads. Not a copy — the same resolved value.
Start with one channel.
A workspace and a community are the same free account. Bring one team or one community and add the other when you want it.