The product is the source of truth
Customer-facing knowledge should follow what the product does, not drift into a separate reality.
The premise
Every product change. Every knowledge surface. Automatically in sync.
MIT
Publishing engine license
Git
Where your content stays
Documentation, SDK references, release notes, examples, tutorials, and AI context are usually maintained separately. Teams have to rediscover what changed, decide which surfaces are affected, and repeat the same update across each one. No system owns that understanding.
Documentation platforms, wikis, content management systems, and knowledge bases store what a team already knows. Thally connects product evolution to customer-facing knowledge. It discovers the communication work a change creates, prioritizes it, and prepares the right updates for review.
Customer-facing knowledge should follow what the product does, not drift into a separate reality.
Find what changed, gather evidence, and map the affected knowledge before drafting new words.
Show why an update is needed, which sources support it, and when no communication change is required.
Thally prepares reviewable work. Your team keeps judgment and publishing authority.
Thally's first job is narrow: understand how a product change affects documentation and help teams keep those pages synchronized. The publishing engine is available under the MIT license, content stays in Git, and humans review the updates. Each accepted review and correction improves the product-specific understanding behind future changes.
Teams should not have to remember every place a product change needs to be explained. As Thally expands, shipping the product should surface the work across documentation, SDK references, examples, tutorials, release notes, AI context, and the knowledge surfaces still to come.
We build Thally so product evolution is continuously reflected everywhere customers learn about it. Contact us directly with questions about the product, support, or company.
Contact Thally