New Auto-generated GIFs from every click. Watch demo

Building the future of software discovery

We started HappySupport because we watched documentation die one release at a time. Every product update turned help articles into lies. We decided to fix the root cause instead of the symptoms.
Smiling man with dark curly hair, beard, glasses, and a brown shirt against a dark background.
Smiling man with dark curly hair, beard, glasses, and a brown shirt against a dark background.
Smiling man with dark curly hair, beard, glasses, and a brown shirt against a dark background.
Smiling man with dark curly hair, beard, glasses, and a brown shirt against a dark background.

The problem we couldn't unsee

Every software team we talked to had the same dirty secret: their help center was outdated. Not by years. By weeks. Sometimes by the time the article was published, the UI had already changed. The result? Support teams answering questions the docs should handle. AI chatbots confidently giving wrong answers because the knowledge base underneath was stale. Customers losing trust, one bad article at a time.

Why existing tools don't fix it

Help center tools give you a nice editor and leave you alone. Screen recorders capture pixels that break on the next redesign. Digital adoption platforms bolt guidance on top without touching the documentation underneath. Nobody connects what your developers ship to what your customers read. That gap is where documentation goes to die.

So we built a new kind of help center

HappySupport records your software at the code level, not as screenshots. When your team pushes a UI change to GitHub, our agent detects what's affected and updates the documentation. No manual work. No reminders that get ignored. We didn't just build a better editor. We built the feedback loop between your codebase and your knowledge base that should have existed from the start.

What we believe

Code is truth
We record metadata from your actual UI, not pixels. What's in the DOM is the single source of truth. Everything else is a guess.
Maintenance is a bug
If a guide needs manual updating after every release, the tool is broken. Documentation should evolve with the product, not chase it.
Help belongs inside the product
Switching tabs to read a help article is friction. The best documentation meets users exactly where they are, inside your app.

Built by humans with the power of AI.

Backed by founders
who lived this problem

Nikas Gysinn
Co-Founder & CEO
Henrik Roth
Co-Founder & CMO
Fabian Silberer
Investor
Benedikt Brand
Investor

Today, you read a help article and then try to find the right button in your software. Tomorrow, you click the button inside the article and it takes you straight there. We're building documentation that doesn't just describe your product. It acts inside it. Guides that walk users through your software step by step. A knowledge base that updates itself with every deploy. An AI layer that gives correct answers because the data underneath is always current.