Hi HN,
We noticed a common issue working at companies like Amazon and Capital One, searching for documentation relevant to our projects was time-consuming and difficult.<p>After doing some research, we found:
- Service catalogs and internal search tools at many companies rely on keyword search (so you can’t just search in natural language for a package that “fetches user favorites”)
- Relevant docs can be scattered in many different places
- If bugs arise or docs are missing, you have to wait to talk to the right engineer on another team<p>Plato lets teams create “spaces” for their services/repos with:
- An OpenAPI spec plus links to documentation, GitHub, and Slack support.
- A chat window that can read your docs using RAG to answer questions about the service and help with debugging issues.<p>The idea is to fit this all into one page, to let devs get the necessary information to start implementing as quickly as possible.<p>We looked at other developer-portal-like tools such as Backstage and Cortex, but didn’t see anything that focuses on making services searchable and making the documentation experience better. We thought that enterprise-search companies like Glean didn’t optimize the workflow of a developer well enough for our liking.<p>That being said, we’re still looking for ways to significantly improve the documentation and API search experience, and are open to feedback. Feel free to sign up, try it out, and email us directly if you have feature requests, suggestions, or other ideas:<p>rohan@platoportal.com
arjun@platoportal.com<p>Link: <a href="https://platoportal.com" rel="nofollow">https://platoportal.com</a>