Knowledge infrastructure for modern support
Turn product truth into working surfaces
Give support, product, and engineering one maintained layer for answers, docs, and workflows. Publish docs sites, power customer portals, and keep support teams aligned as sources change.
New ticket
Describe your issueHello Joyce!
The cancellation policy for a booked class may vary depending on the studio you are booking with. Generally, we allow you to cancel a class reservation without any penalty up to a certain time before the class starts. However, if you cancel within 24 hours of the class start time, you may be subject to a late cancellation fee. This fee is typically deducted from your credits or charged to your payment method on file.
Did this not solve your issue?
Support answers grounded in source truth
Resolve repeat questions with answers grounded in current product docs, support history, code changes, and connected business systems.
Customer portals with actions
Let customers search docs, check account context, start approved workflows, and escalate to support from one authenticated portal.
Processed message: We are experiencing 404 errors on the cron endpoint since this morning. Upon reviewing the logs, it appears that this error is not properly detected.
Original message: Help! Cron is alwys retunning 404s now its happening all the time since this morning!!! Ntohing to see in the logs!
Knowledge-aware triage
Categorize, summarize, translate, and route tickets with context from your code, docs, policies, and customer history.
May 14, 12:28 AM
Hi Tyler!
Yes, the cancellation policy for a booked class may vary depending on the studio you are booking with. Generally, we allow you to cancel a class reservation without any penalty up to 12 hours before the class starts. However, if you cancel later than that, you will be subject to a late cancellation fee. This fee is deducted from your credits.
Best,
Joshua
AI Draft Composer
Draft replies that reflect current policies, product behavior, brand voice, and the source material behind them.
The infrastructure layer beneath your knowledge
Connect 3,000+ sources across code, support, CRM, wikis, meetings, websites, and APIs. DevDocs.ai syncs, normalizes, permission-scopes, and refreshes that content into a structured knowledge layer your docs, portals, support team, and products can build on.
GitHub Repo
GitLab
Notion
Fireflies
Salesforce Knowledge
Jira
Website
GitHub Discussions
Zendesk
Salesforce Case
HubSpot
GitBook
Front
GitHub Issues
Confluence
DevDocs.ai supports encryption at rest, and is actively pursuing SOC 2 Type II compliance.
Ship docs sites and portals from the same layer
Publish public docs, authenticated customer portals, support centers, in-app help, and internal knowledge surfaces without copying content into another system.
Publish branded docs sites
Turn connected source truth into searchable docs sites with scoped content, consistent design, and freshness checks built in.
Launch customer portals
Give authenticated customers a place to search docs, see account-aware context, request help, and hand off to support.
Find gaps before tickets spike
Use search, support, and portal analytics to identify missing, stale, or conflicting knowledge before it becomes support volume.
Build products on governed knowledge
Use REST APIs, SDKs, and an MCP gateway to read source-aware answers, sync content, publish docs experiences, and connect approved tools without rebuilding auth or OAuth plumbing.
curl https://api.devdocs.ai/v1/train -X POST \-H "Authorization: Bearer <TOKEN>" \-F 'file=@./post.md'
curl https://api.devdocs.ai/v1/chat -X POST \-H "Authorization: Bearer <TOKEN>" \-d '{"messages": [{ "role": "user", "content": "How do I claim my credits?" }],"model": "gpt-4-32k"}'
curl -X GET "https://api.devdocs.ai/v1/insights/queries" \-H "Authorization: Bearer <TOKEN>" \-d '{ "from": "2023-09-01T22:00:00" }'
1import { DevDocsAI } from '@devdocsai/react';2import { syncSource } from '@devdocsai/core';34export default function CustomerPortal(): ReactElement {5 return <DevDocsAI6 projectKey={process.env.NEXT_PUBLIC_PROJECT_KEY}7 portal={{8 surface: 'customer-docs',9 sources: ['docs', 'support', 'policies'],10 requireAuth: true,11 }}12 />13}
Ready to ship from one knowledge infrastructure?
Publish docs sites, launch customer portals, and keep support grounded in the same source truth your teams already maintain.