osFoundry / Platform
Public KB hosting
Your KB on your own domain, fully indexed, with a chat widget and ticket queue out of the box.
What it is
Public KB hosting turns the knowledge you keep inside osFoundry into a public help center that lives on your own domain. You point a subdomain (or a root domain) at it, publish your articles, and the pages are served as fully indexed, crawlable HTML so search engines and readers can find them directly. It is one of the Apps & Backend surfaces in osFoundry, so the same workspace where you write and organize knowledge is the one that serves it publicly, without a separate CMS, hosting account, or support-desk subscription.
Inside osFoundry, your knowledge base is already the source of truth your agents read from. Public KB hosting publishes that same content outward and layers two things on top of it out of the box: an AI chat widget that answers from your published articles, and a ticket queue for the questions the widget cannot close. Because osFoundry is bring-your-own-key, the chat widget runs on the model and API key you choose — a local model on your own machine, a cloud provider you already pay for, or a self-hosted endpoint — with no reseller markup on the tokens it spends. The widget grounds its answers in your KB content rather than answering from a generic model, so responses stay tied to what you have actually documented.
This matters because a public knowledge base usually means stitching together a docs host, a search index, a chat/support widget, and a ticketing tool from four vendors, each with its own seat pricing and its own copy of your content. Here the content stays in one place you control, the pages are indexed for real search visibility, deflection happens through the chat widget, and anything that escalates lands in a queue you can work — all from the workspace you already use. With no per-seat fees and keys you own, the cost of running a public help center scales with usage you control rather than with the number of people on your team.
Key capabilities
- Serve your knowledge base on your own domain or subdomain as fully indexed, crawlable pages
- Embed an AI chat widget that answers from your published articles, not a generic model
- Capture unresolved questions in a built-in ticket queue instead of a separate helpdesk
- Run the chat widget on your own model keys — local, cloud, or self-hosted — with no reseller markup
- Publish straight from the same osFoundry workspace where you author and organize knowledge, with no per-seat fees
Use cases
- SaaS founder: publish product docs on docs.yourdomain.com and let the chat widget deflect common questions before they reach the team
- Support lead: front the public help center with an AI widget and route everything it can't answer into the ticket queue to work
- Solo operator: run a searchable public knowledge base and an answer bot on a local model, paying only for tokens you use rather than support-tool seats
Frequently asked questions
Can I host the knowledge base on my own domain?
Yes. You point your own domain or a subdomain (for example docs.yourcompany.com) at it, and the KB pages are served there as fully indexed, crawlable HTML so they show up in search and can be linked directly.
What model powers the chat widget, and who pays for it?
The widget runs on the model and API key you bring — a local model, a cloud provider, or a self-hosted endpoint. osFoundry is bring-your-own-key with no reseller markup, so you pay your provider directly for the tokens the widget uses, or nothing beyond your hardware if you run a local model.
How is this different from just using a hosted help-desk product?
A typical setup means separate vendors for docs hosting, search, a chat widget, and ticketing, each with per-seat pricing and its own copy of your content. Here the content lives in the same osFoundry workspace where you author it, the pages are indexed, the chat widget answers from those articles, and unresolved questions drop into a ticket queue — all in one place, with no per-seat fees.