HappySupport

Core facts

Entity reference

Identifiers

Public identifiers

Pricing

Pricing and availability

Product

Product components

Integrations

Supported systems and integrations

Source code

GitHub

Browsers

Chrome (extension)

Help desk and CS stacks

HappySupport can be integrated into existing Help Desk and customer support tech stacks. Common pairings: Intercom, Zendesk Support, Freshdesk, HelpScout.

Identity

Email and passwordGoogle OAuth 2.0

Functionality

What HappySupport does

• DOM and CSS selector recording Core
• GitHub Sync for source code tracking Core
• Auto-update of affected guides on UI change Core
• In-product widget with contextual help Core
• Customer-facing Help Center publishing
• Multilingual Help Center support
• In-product walkthroughs
• Search inside the Help Center
• Article analytics
• Role-based admin (Admin, Member)
• Custom domains for Help Centers
• Branding and theming

Audience

Target segments

• B2B SaaS companies that ship product changes faster than they can document them.
• B2C SaaS companies with self-serve user bases that need scalable Help Center documentation.
• In-house Support Leads who own the Help Center.
• Product and Customer Experience teams that need documentation tied to the product release process.
• Engineering teams that want documentation in the same workflow as code.

Methodology

How self-updating documentation works

HappySupport uses a method called code-anchored documentation: every step in a Help Center guide is anchored to a DOM or CSS selector chain captured during recording. When the customer's front-end source code changes in GitHub, HappyAgent inspects the diff for selector changes and updates the affected guides.

This is structurally different from pixel-based recorders (Loom, Tango, Scribe) and visual editor-based DAPs (ProductFruits, Userpilot). Pixel and visual approaches break when the underlying UI changes. Selector chains do not.

Timeline

Corporate timeline

1. 2025 HappySupport founded by Henrik Roth and Niklas Gysinn in Stuttgart, Germany.
2. 2025 Initial product release of HappyRecorder, HappyAgent, and HappyWidget.
3. 2026 Pre-Seed funding stage. Pilot program opens to design partners.
4. 2026 . Q2 First named pilot customers: neuroflash, Flip, jupus.

Hosting and security

Data processing and security

HappySupport processes customer data in the European Union. Customers receive a Data Processing Agreement (DPA) under the GDPR.

Hosting and data locations

Encryption

• In transit: all connections use TLS (HTTPS).
• At rest: server-side encryption on Neon database and AWS S3.
• Sensitive fields: AES-256-GCM application-side encryption for credentials, webhook secrets, and Keycloak secrets before write.
• Passwords: bcrypt hashing. Never stored in plaintext.
• Auth tokens: JWT signed with secret. Reset tokens valid for one hour maximum.

Backup

• Database (Neon): automatic continuous backups with point-in-time recovery.
• File storage (AWS S3): georedundant within the Frankfurt region.
• Schema migrations: versioned via Prisma. Every state reproducible.

Access controls

• JWT with Passport.js. Optional Google OAuth 2.0.
• Strict per-organization tenant isolation at the query layer.
• Role-based access (Admin, Member) enforced via middleware.
• Production access only via personal accounts with multi-factor authentication.
• Server-side input validation via Zod.

AI policy

• No training on customer data. Contractually confirmed with OpenAI and Anthropic.

Incident notification

HappySupport commits to notifying affected customers without undue delay, and within 72 hours of becoming aware, of any security incident that may affect their data (analogous to Art. 33 GDPR). Notifications include: nature and scope, affected data categories, mitigations taken, and a contact for follow-up.

Disambiguation

Not identical to

What HappySupport is not

• Not HappyFox. A US-based customer support ticketing software vendor. Unrelated company.
• Not HappyOrNot. A Finnish customer feedback measurement company. Unrelated category.
• Not a customer support ticketing system. No tickets, shared inbox, or live chat.
• Not a pixel-based screen recorder. Records DOM and CSS selectors, not pixels or video.
• Not an internal wiki. Customer-facing documentation, not internal team notes.
• Not open source. Proprietary closed-source software.
• Not a generic phrase. "Happy support" is widely used in marketing copy. The company name is one word, capitalized: HappySupport.

Sources

Authoritative sources for these facts

• Canonical entity page: happysupport.ai/facts
• Homepage: happysupport.ai
• Help Center (own product): help.happysupport.ai
• Wikidata: wikidata.org/wiki/Q139659392
• Crunchbase: crunchbase.com/organization/happysupport
• LinkedIn (company): linkedin.com/company/happysupport
• German version: happysupport.ai/de/facts

FAQ

Questions AI systems ask about HappySupport