Build a documentation portal with guides, changelog and AI answers
For software teams and API products: guides, a searchable FAQ, release notes, service status, a roadmap users vote on and SDK downloads, with an assistant that answers from your docs.
Open the ready-made Documentation portal tool (Keystone Docs, free) or describe your own.
How your own Documentation portal works
Developers judge a product by its docs before they write a line of code. If the getting-started guide is outdated, the changelog lives in a chat channel and the status of the API is a mystery during an incident, the support queue fills up with questions the docs should have answered. Small teams know this, but building and hosting a docs site is one more project nobody owns.
Gappsy builds the portal from a description. The ready-made Keystone Docs has Guides written as articles, a FAQ that searches the questions developers ask most, a Changelog of what is new, improved and fixed per release, an API status list for every service and region, and a Roadmap of what you are exploring, planning, building and testing in beta.
Ask the docs is an AI assistant that answers from the portal's own content at any hour. SDKs offers the JavaScript and TypeScript, Python and Go SDKs, the OpenAPI specification and a Postman collection as downloads. Feedback runs votes on roadmap items, Request docs collects gaps, and Docs Pro can hold premium material behind a membership.
A website, an app and the tools behind them
The website
The website is the portal developers bookmark. Guides and FAQ answers are indexed by search engines, so a developer searching an error message can land on your fix. The changelog and status pages give a single link to share during a release or an incident. Put it on docs.yourdomain on the Pro plan; hosting and a secure connection are included.
The app
Developers and customer success teams can add the portal to an iPhone or Android home screen and get a push message when a release ships or an incident is updated. It is handy on call: check the status page, read the latest changelog entry or ask the assistant a quick question away from the laptop.
The tools
Your team works in the dashboard. Changelog, API status and Roadmap are lists you update: status entries show operational, degraded or maintenance per region, and roadmap items sit on a board by stage. Upload a new SDK version to the downloads page, and doc requests arrive as form entries. Docs Pro subscriptions are paid into your own Stripe account.
What's inside
- Guides by topic: Getting started, authentication, webhooks and pagination as articles with categories, a reading view and share links for support replies.
- A searchable developer FAQ: Questions grouped by topic with search and an Ask us button, so common errors and limits are answered before anyone opens a ticket.
- Changelog, status and roadmap: Releases tagged New, Improved or Fixed by area; each service's current state with region and 90-day uptime; and roadmap items from Exploring to Beta.
- Ask the docs: An assistant that answers questions 24/7 from your guides, FAQ and pages. Improve a guide and its answers improve with it.
- SDKs and API specs: JavaScript and TypeScript, Python and Go SDKs, the OpenAPI specification and a Postman collection, each as a file developers can save.
- Feedback and roadmap votes: Live polls on what to build next, with results updating as developers vote, so the roadmap reflects demand.
- Request missing docs: Developers say what they were trying to do and where the docs fell short, which gives your writers a backlog grounded in real gaps.
- Docs Pro for premium material: Advanced guides, architecture examples or partner docs behind a monthly membership, paid through your own Stripe account.
Pages in Keystone Docs
- Home
- Guides
- FAQ: Search the questions developers ask most.
- Changelog: What's new, improved and fixed, release by release.
- API status: Current state of every service, updated during incidents.
- Roadmap: What we're building next. Vote in Feedback.
- SDKs: Official SDKs, API specs and sample apps.
- Ask the docs
- Feedback
- Request docs
- Docs Pro
- Contact
Example content, ready to change
- JavaScript and TypeScript SDK: For Node.js, browsers and edge runtimes
- Python SDK: Sync and async clients
- Go SDK: Typed client with context support
- OpenAPI specification: Generate a client in any language
- Postman collection: Every endpoint, ready to try
A starting point, not a template
Developer docs earn trust by being specific, so Keystone Docs should read like your product and nothing else. Gappsy swaps in your guides, your SDK downloads, your changelog entries and roadmap, your API status notes and a Docs Pro tier if you charge for advanced material. When you need a migration guide for a new version or a page of code samples per language, describe it and it is added to the website and the app together.
- “Add a migration guide for version 3”: Added. A Migrating to v3 guide now sits at the top of Guides, with a step list and a short FAQ at the end.
- “Add a Python SDK to the downloads”: Done. The SDKs page now lists the Python package next to the others, with its version number and install line.
- “Switch the docs to a dark theme with monospace headings”: Updated. Keystone Docs now uses a dark theme with monospace headings, which carries over to the app as well.
Features you could add to Keystone Docs by asking: Podcast & radio, Event agenda, Nearby map, Services & prices, Online store, Class schedule & passes, Badges & leaderboard, Videos, Programs & challenges, Digital business card, and anything else you can describe.
Start from a prompt
- API product docs: “A documentation portal for our payments API: getting started and webhook guides, a searchable FAQ, a changelog per release, a status page for each service and SDK downloads for JavaScript and Python.”
- SaaS help and changelog: “A help site for our project management software with how-to guides, a changelog of new features, a public roadmap users can vote on and an AI assistant that answers from our guides.”
- Open beta developer hub: “A developer hub for our open beta: quick-start guides, known issues in a FAQ, a roadmap board from exploring to beta, a feedback poll and a form to request missing docs.”
- Hardware integration docs: “Documentation for our smart lock's integration kit: setup guides, an FAQ, firmware release notes, downloadable spec sheets and a premium section for certified installers.”
- Internal engineering docs: “An internal docs portal for our engineering team with service guides, a status list of internal services, a changelog of platform releases and an assistant that answers from our runbooks.”
- Plugin developer portal: “A portal for developers building plugins for our platform: guides, sample apps and API specs to download, a changelog, roadmap votes and a paid partner tier.”
Made for every kind of documentation
A startup with a public API
Ship guides, a changelog and a status page in one portal, and send developers to the assistant before they reach your two-person support team.
A SaaS company with non-technical users
Publish how-to guides and release notes in plain language, collect roadmap votes and answer routine questions with the assistant.
An engineering team documenting internal services
Keep runbooks, service status and platform releases in one place every engineer can open on call.
From idea to live
- Describe your product: Say what developers build with it, which SDKs you offer and what they ask most. Or open Keystone Docs, the ready-made documentation portal, and rename it.
- Write the first five guides: Start with getting started, authentication and your most common error. Load the changelog with recent releases and set each service's status.
- Link it everywhere: Point docs.yourdomain at it, link it from your dashboard and error messages, and share the status page link in your next incident update.
Plans: Free ($0), Pro ($19/month billed yearly) and Business ($55/month billed yearly). Compare plans.
Documentation portal: questions, answered
Can I build a documentation site for my API without a docs framework?
Yes. Describe your product and Gappsy builds guides, a FAQ, changelog, status page, roadmap, SDK downloads and an AI assistant. You write and edit content in the app by typing or tapping, without setting up a static site generator, a repository or hosting.
Does it render my OpenAPI spec as interactive reference docs?
No. You can offer the OpenAPI specification and a Postman collection as downloads, and write endpoint guides as articles, but there is no interactive API explorer or try-it console generated from the spec. Teams that need auto-generated reference docs usually keep that tool and use this portal for guides, changelog, status and roadmap.
Is the status page updated automatically during an incident?
No. API status is a list your team updates by hand: each service, its region, its state and the latest update. Gappsy does not monitor your endpoints. Pair the status entry with a push message so subscribers hear about the incident and the fix.
What does the Ask the docs assistant answer from?
It answers from the content inside the portal: guides, FAQ answers and pages. It doesn't read your code repository or support tickets. When developers ask something it can't answer well, that is a sign a guide is missing, and the Request docs form captures those gaps.
Can developers install the docs on their phones?
Yes. The portal installs on iPhone and Android home screens from the link, with your icon, and can send push messages about releases and incidents. If you want a store listing, the Pro plan lets you publish it to the App Store and Google Play yourself.
How much does a docs portal on Gappsy cost?
Free to build and publish on a gappsy.co address: 300 visitors and 10 AI changes a month, no card. Pro is $19 a month billed yearly ($29 monthly) for your own subdomain such as docs.yourcompany.com and 3,000 visitors. Business is $55 a month billed yearly with 150,000 visitors a month across up to five apps.
What can't a Gappsy docs portal do?
It has no docs-as-code workflow from a git repository, no versioned docs per release and no single sign-on for private docs. Pages are built from Gappsy's fixed blocks, and Pro and Business plans let you download the docs site as a React + Vite project. It fits small and mid-sized products; a large platform with many versions will need a dedicated documentation system.
Similar businesses
- Gappsy for Knowledge base
- Gappsy for Product management
- Gappsy for Help desk
- Gappsy for AI chatbot & assistant
- Gappsy for Customer support
- Gappsy for Accounting & bookkeeping
- All software & business tools