Browzer
Put your technical content on autopilot
Start new thread

Browzer - Put your technical content on autopilot

by
•
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.

Add a comment

Replies

Best
Maker
📌

Hey Product Hunt

I'm Rahul, the founder of , a tool to put your technical content & docs workflows on autopilot.

We built it because in the previous iteration, I noticed 30% of our free trial users were DevRels who used our product to create product guides for their web-apps.

I decided to pivot into building a tool to automate the most time consuming parts of DevRel's job - creating blogs, quickstarts, cookbooks, demo videos, and other digital resources, so that you got more time to focus on what you love doing, the IRL stuff like building communities & talking to users.

With Browzer, you can connect your codebase, and through our agent mode, you can prompt Browzer to create any technical content that you like. This can also be put on a schedule, so you have fresh content that churns out every week. Content queues up in your Library for you to then review and publish.

We have a free 1-week trial, and paid plans for using Browzer thereafter.

Would love to get any feedback from the PH community, especially from anyone building devtools.

I'm here all day to answer questions the community might have!

In case you'd like to have a longer convo with me you can reach me at or +1 (716) 398-2852.

How do you handle cases where the workflow changes slightly but the existing documentation is still mostly correct?

Congrats & team!

Again thanks for sharing another cool product <3

Maker
thanks Hamza! Yes, is the best & we’re truly grateful to him for hunting Browzer. About your question - we understand how the code changes made affect what’s in the docs. Sometimes, you might have certain semantic changes which doesn’t affect forward facing APIs, but just the internal logic. Such changes, although recognized, don’t trigger a docs update. However, if a function name in your sdk changes, or a new route is added to your api, those things trigger an update to the docs
Maker

    thanks !

do give a try out 🙌

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.

Maker
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!

This looks really useful! One question on privacy/IP protection - how are you handling this? Connecting a codebase sounds like an intelectual property leakage risk (but that's just my marketer-at-a-corp-environment perspective, I'd be curious to know if it actually a risk or just a perceived one)

Maker
I see where you’re coming from & it’s a valid question. We ask users to install our github app because that app is responsible for looking at the codebase and suggesting technical content that’s relevant. None of your code is ever stored on our end, plus we have zero day retention policies with our upstream inference providers so you can be certain that they’re not stored upstream as well. Additionally, we’re in the process of getting our SOC2 Type 2 to give people a breather.

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.

Maker
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!
Maker

The video content generation is no less than a boom. It saves your so much hours of the efforts & time that goes in scripting, editing and this that. Browzer makes it supereasy. You just say it - and Browzer makes it ready to publish. All built for your product - in the way you love it.
- from the founding engineer

Maker
glad to have you on the team! Go Browzer ✌️

How does Browzer handle a large repo with multiple services and different documentation owners?

what stood out to me is how Browzer keeps the content tied to the actual code. in practice that could save developers a lot time updating docs and exp after small code changes.

Maker
thanks Jabari! Yes! Would love for you to try out Browzer. And if you have any feedback please let me know.

Interesting touch which is the demo video generation. I can see it being especially useful when a developer needs to understand a product quickly.

Maker
yup, that’s the goal. Plus videos are super frustrating to create generally. Our goal is to help make the process of creation of motion videos & explainers about your product, as simple as possible. Would love for you to try it out & give us some feedback!

What happens when the generated content does no fully match the actual implementation?

123
Next