Why We Built thefaq.app

The Problem

Every product needs a FAQ page. It sounds simple — write some questions and answers, put them on a page, done.

But when we tried to add FAQ content to our products, we kept running into the same problems:

Option 1: Use a help desk. Tools like Zendesk and Intercom have knowledge base features, but they charge per agent ($55-$115/month each), require buying the entire support suite, and lock your content behind proprietary theming systems. We just wanted a FAQ page, not a $500/month help desk.

Option 2: Build it yourself. Write a database table, build CRUD endpoints, create an admin UI, add search, handle SEO markup, build an embeddable widget... for what should be a solved problem.

Option 3: Use a static page builder. WordPress plugins, Notion public pages, or hand-coded HTML. Fast to set up, impossible to maintain at scale, and no API for programmatic access.

None of these options worked for a technical team that wanted to:

• Manage FAQ content through a REST API
• Embed answers inside our product (not just on a marketing page)
• Automate content updates from CI/CD pipelines
• Get SEO benefits without manually writing JSON-LD schema
• Keep costs predictable as the team grows

So we built thefaq.app.

The Core Idea: FAQ as an API

The mental model is simple: Stripe for FAQs.

Stripe made payments programmable. We make FAQ content programmable. Every feature is available through a REST API before it gets a dashboard UI. The dashboard is a first-party API consumer, not a privileged backend.

import { TheFAQApp } from "@faqapp/core";

const faq = new TheFAQApp({
  apiKey: process.env.FAQ_API_KEY,
  organization: "my-org",
});

// Your FAQ content is data, not a locked CMS
const questions = await faq.questions.list({ collection: "billing" });
const results = await faq.questions.search("cancel subscription");

This means your FAQ content works everywhere:

• Marketing site via the embeddable widget
• In-app help panel via the API
• Mobile app via the same API
• Slack bot, docs site, or anywhere else you can make an HTTP request

One source of truth. Many surfaces.

What We Prioritized

API Access on Every Plan

Most competitors gate API access behind enterprise tiers ($200+/month). We believe the API is the product, not a premium add-on. Our free tier includes 1,000 API requests per month.

Flat-Rate Pricing

Per-agent pricing punishes growing teams. A 10-person team on Zendesk pays $550-$1,150/month. On thefaq.app, you pay the same flat rate whether you have 1 user or 100.

Developer Experience

• Official SDKs for JavaScript/TypeScript (@faqapp/core, @faqapp/nextjs)
• OpenAPI spec for code generation
• Scoped API keys (read, write, admin)
• Standard REST conventions

Built-In SEO

FAQ pages should rank in Google. We auto-generate FAQ schema markup (JSON-LD), clean URLs, sitemaps, and Open Graph tags. Your FAQ pages qualify for Google rich results without you writing a line of JSON.

AI-Powered Content

Writing FAQ content is tedious. Our AI generates draft answers from your existing documentation, support history, or product context. You review and edit — the AI handles the first draft.

What We Deliberately Left Out

thefaq.app is not a help desk. We don't do:

• Ticketing — Use Linear, Zendesk, or whatever your team already uses
• Live chat — Use Intercom, Crisp, or Slack
• Phone support — That's a different product entirely
• CRM — Not our lane

We do one thing well: API-first FAQ and knowledge base management. This focus means faster development, a simpler product, and lower prices.

If you need a full support suite, we're not the right tool. If you need a great FAQ with a real API, we're exactly what you're looking for.

The Stack (for Fellow Developers)

Since our users are developers, here's what we're built on:

• Next.js — App Router, Server Components, API routes
• TypeScript — End to end, including SDKs
• Prisma — Database access, never raw SQL
• PostgreSQL — Primary data store
• Zod — Validation everywhere (API input, SDK responses, forms)
• Vercel — Hosting and edge delivery

The entire platform is a monorepo with shared packages for the API layer, database client, SDK, and UI components.

Where We're Going

We're just getting started. On the roadmap:

• More SDKs — Python, Go, Ruby
• Webhooks — Get notified when content changes
• Bulk import/export — Move content in and out easily
• Advanced analytics — Search queries, deflection rates, content gaps
• Custom widget themes — Match your brand precisely
• Team collaboration — Comments, review workflows, content approvals

Try It

If you're a developer who needs a FAQ page and doesn't want to pay help desk prices or build from scratch, try thefaq.app free. Full API access, no credit card required.

Related Reading

• Best FAQ Software for Developers — How we compare to other tools
• API-First FAQ vs Traditional CMS — The architectural case for API-first
• Knowledge Base API Guide — Deep dive into building with a KB API
• How to Build a FAQ Page with an API — Step-by-step tutorial
• Developer Tool Launch Checklist — Ship support docs before day one
• Introducing thefaq.app on Product Hunt — Our launch announcement and what's available today