| You know, I think normally the common sense buy-vs-build wisdom would win out here, but this is truly an offering that is trivial to build out and is aimed towards an audience that can forgive the common UX perils of home built solutions. Not to mention there are great off the shelf open source alternatives that work FANTASTIC and have most of the offerings listed on this SaaS product. I use https://github.com/Rebilly/generator-openapi-repo which took literally minutes to setup. Here's my workflow: * I type "npm start" in my docs project repo and load the tab that contains the syntax-highlighting enabled editor window in the browser. * I modify my swagger.yml to update my documentation in the editor * I use the dev preview tab (a separate node web dev server on another port) to see how the documentation looks * Once I'm satisfied, I commit and push everything into the git backed repo. My api docs exist on a github page so I don't even need to worry about hosting. As soon as I push my changes, they are live on my docs site. I've setup a CNAME record to point apidocs.mycompany.com to the github page and presto, I have a whitelabeled documentation site that I can update on a dime, for free, with absolutely zero monthly charge. I have a hard time understanding how even the most elementary of developer couldn't manage to do this. I can't imagine it takes more than two hours for a mediocre web developer to get running (at most). At what point do you have the financial responsibility to reasonably consider implementing an elementary task yourself instead of SaaSifying yet another area of your company? $49/mo is less than my hourly rate, in theory, but doing it once means one less SaaS bill at the end of the month. In what use case is buying this product justifiable? |