One product, two surfaces

August 5, 2026 · The Kemble team

A company chat tool and a community platform look like two products. Underneath they are almost entirely the same one: messages, threads, reactions, files, search, voice, presence, permissions. What differs is navigation, density and theme — the shell, not the engine.

So Kemble builds the engine once. Work and Circle are two shells over one implementation, and a surface is a view predicate rather than an authorization boundary. Nothing server-side grants or withholds on it; access resolves on organization and membership alone.

Why that matters to you

Every improvement to search, permissions or voice lands in both products on the same day. A company that runs an internal workspace and a customer community is not running two systems with two permission models and two audit trails — it is running one, with two front doors.

It also means the honest answer to “can Circle do X, which Work does?” is usually yes, and when it is no, the reason is a deliberate difference in the shell rather than an accident of which product got the feature first.