Octri.dev - Generate customizable Docs, SDKs, MCP server, and monitoring
by•
Upload an OpenAPI spec and Octri generates a fully customizable documentation site, high-quality client SDKs in ten languages (TypeScript, Python, Go, Rust, Ruby, PHP, Java, Kotlin, Swift, Dart) and an MCP server so AI agents can call your API.
The new part: every SDK reports its own production errors back, so you see integration failures before your users file tickets. GitHub sync regenerates everything on every merge.
Replies
Hi Product Hunt, I'm Emad, one of the makers of Octri. 👋
If you ship an API you know the routine: write the docs by hand, bolt on an SDK generator, then have no idea when those SDKs break inside someone's production app. Octri does the whole thing from one OpenAPI spec: a docs site, SDKs in ten languages (TypeScript, Python, Go, Rust, Ruby, PHP, Java, Kotlin, Swift, Dart) and an MCP server so Claude or Cursor can call your API.
What is new though? Let me tell you! The SDKs monitor themselves. A failed call in a user's app comes back as a de-minified stack trace tagged to the exact release. No separate error-tracking setup! more about how it works and its security here: https://octri.dev/monitoring
GitHub sync regenerates and republishes everything on every merge. Free tier is available to try it out and keep it if your API doesn't need more than the offered limits + we offer an OSS program as well for the open-source community! more about it here: https://octri.dev/open-source
Point it at your own spec and try it out free! All comments and feedback are welcome. We'll be here answering every one of them!
Congrats👏 on the launch@emad_khair the whole setup and UI looks incredibly slick.
@priya_kushwaha1 Thank you so much Priya! Really appreciate the support!
@emad_khair Anytime, it’s a brilliant product keep up the great work.👏👏
@emad_khair Thanks for the free tier and the open-source program, Emad. Letting small teams and OSS projects try it properly makes a big difference
@jedidiah_behar5 Thank you so much Jedidiah! We are so happy to support both indie developers and OSS! It's exactly why we launched Octri! 🙌
Python and TypeScript SDK generation usually breaks on edge cases excited to test this, congrats for shipping @Octri.dev team
@vikramp7470 Thanks a lot Vikram! Indeed and a lot of generators out there fail exactly there!
We run the generator against a growing set of real-world specs, picked because they're messy. We have and still are battle testing our generator to make sure it handles 95% of the cases always without interference!
Make sure to check out our free and no signup spec auditor to check how your spec ranks: https://octri.dev/openapi-audit
@emad_khair Sounds solid, running against messy real-world specs makes total sense.
congrats on getting this out the door.. will there be options to customize the doc themes in the future?
@deepaksingh09 Hey Deepak! Thank you!
We already offer plenty of customization options + custom code/CSS support to give you full freedom to make your docs look the way you want! We still plan to evolve it even more during this quarter!
Huge congrats for launch, great to see a solid free tier alongside dedicated support for open-source projects.
@charan_t_m Thanks a lot Charan! The free-tier is actually pretty generous too since it allows a small API to benefit from all of our features at no extra cost at all!
When an SDK sends back a failed call, what data goes with it? Can I make sure no request bodies or user info are included?
@julian_ting2 Hi Julian, That's a good question!
For the monitoring, We actually by default not collect request bodies but if you added it as a required field we redact all the sensitive fields automatically. also, on the redacting note we actually have 2 layers of redacting that happen before any data is stored that filters out any sensitive data from reaching us. The first layer is on the client side and the second is as soon as the data reach Octri. All that is to ensure that no user data ever reach us except the error they ran into.
in addition to that, we also offer custom fields that you can add incase you named a sensitive field in a different language and it could get through our redaction system to be caught as well in the redaction stage.
More details about the telemetry here: https://octri.dev/dpa/monitoring
Happy to answer any other questions you might have!
Amazing idea. Love it. Super excited to try it out on my own. Congrats on the launch though!
@suryansh_tiwari2 Thanks a lot for your support! 🙏
one spec → docs, sdks and mcp is neat 👏 self-monitoring sdks are the cool peice
@petrkovacik Exactly! Thanks Petr for your support!
This looks super useful ! Having the SDKs report their own failures back automatically is a massive time saver. Quick question : how hard is it to add custom CSS to the generated docs site ?
@axel_paulin Thanks a lot Axel! You can easily add custom-CSS through our dashboard settings through a simple text-box that takes in your CSS code and applies it to your docs site!
We designed the Studio over 3 years to make it as easy as possible for anyone to go in and customize the docs looks with as little of knowledge about code/CSS as possible!
Also, our UI based customization tool is pretty powerful with all the built-in components, custom components that you can build with it, and the powerful Notion-like docs editor!
Hey @emad_khair Really like the idea of closing the loop between SDK generation and what actually breaks in production. How does Octri handle API changes over time, can it detect breaking changes in the OpenAPI spec and flag which generated SDKs or existing integrations might be impacted before a new version is shipped?
@dounia_boughalem Thanks a lot Dounia!
That's a really good question! Yes, we watch your spec and automatically generate SDKs and update the changelog with what exactly could break current integrations if they decide to update.
in addition to that, we actually have internal build checks, tests, and linting run before publishing. So a problem introduced in a recent update gets caught before the SDK goes out to public! These checks are available on literally all tiers (even free!), so all the SDKs produced by Octri maintain the highest possible quality!
I like that the SDKs are not just generated once and left alone. The production error feedback makes the whole workflow feel muh more practical for real API integrations.
@anthony_adams_ Exactly! We also have full info about the monitoring part and it's telemetry if you're interested here: https://octri.dev/dpa/monitoring