Browzer lets users connect their codebases to auto-generate docs that self heal and technical content (blogs, quickstarts, cookbooks, videos) that are human & agent friendly. We automate all technical output of a DevRel so that DevRel teams can focus more on community, growth & events. Try it out at - https://trybrowzer.com
Connect your GitHub repo and Browzer drafts your docs, guides, changelogs, cookbooks, quickstarts, and SEO & AEO friendly blog posts, and then heals them on every merge. We automate all technical output of a DevRel so that DevRel teams can focus more on community, growth & events.
@zach_gold great question. Generating demo videos is one part of it. The other things you can accomplish with Browzer are -
(1) creating SEO & AEO friendly blog posts (which are technical)
(2) cookbooks & QuickStarts in case you have an sdk, api, cli or MCP as it would help users get ramped up to your product easily
(3) Creating docs for consumers of your products (these docs also self heal) - all these docs are human and agent friendly, so they come with optimized .md’s which can be fed into coding agents directly to get things done.
Report
How well does it support monorepos? I imagine a scenario where there are a dozen microservices and am curious if the healing code is service-oriented or treats the entire repository as one entity.
Report
This is huge. Have you considered expanding this for technical content creation as well?
Report
firstly congratulation for the launch, for me the self healing documentation idea is the standout feature. code changes often happen much faster than the docs can keep up.
@ashir_murtaza1 thank you! And exactly! Especially in the age of AI where most teams are shipping 100s of changes daily, it becomes critical to have self healing docs!
Report
I have always found keeping docs updated after a release more painful than writing them in the first place. This looks like a useful way around that.
@ashley_james yes, definitely. Browzer not only makes it super simple to create docs from scratch, but also makes it easy to manage any drifts thereafter, with little(or no) effort from your end! It just gets it done!
How does Browzer handle a large repo with multiple services and different documentation owners?
What happens when the generated content does no fully match the actual implementation?
Portal
Really interesting! I saw you can generate videos - what other ways can I use what Browzer's context is on my product?
Browzer
How well does it support monorepos? I imagine a scenario where there are a dozen microservices and am curious if the healing code is service-oriented or treats the entire repository as one entity.
This is huge. Have you considered expanding this for technical content creation as well?
firstly congratulation for the launch, for me the self healing documentation idea is the standout feature. code changes often happen much faster than the docs can keep up.
Browzer
I have always found keeping docs updated after a release more painful than writing them in the first place. This looks like a useful way around that.
Browzer