Releasing fast shouldn’t mean breaking things. As your product grows, Ogoron takes over your QA process end‑to‑end. It understands your product, generates and maintains tests, and continuously validates every change - replacing a systems analyst, test analyst, and QA engineer. Get predictable releases, fewer bugs in production, and full coverage without manual effort. Ship faster. Stay in control. Break nothing
Free Options
Launch Team / Built With
How does Ogoron authenticate with our private repos and runners?
Ogoron
@toki_tango Great question!
In practice, Ogoron is a CLI-first tool, so authentication is usually handled by the environment it runs in. For GitHub, we already support private repositories through our main integration and billing flow.
For other Git systems, the setup is still more manual today, but it is straightforward to support via the CLI as well. If that is relevant for your setup, feel free to reach out to me at vmynka@ogoron.com for early access.
As for private runners, there are no special restrictions on our side. The main requirement is that the runner must have network access to our services and to the external LLM provider endpoints we use, which currently means OpenAI
Does it support Dockerized applications and container orchestration tools like Kubernetes or AWS ECS? Most of our stack runs in containers.
Ogoron
@aleh_suprunovich Thanks for the question! Yes – containerized applications are very much in scope for us, and Docker is currently the primary path we support.
Deeper support for orchestration layers like Kubernetes and AWS ECS is still on our roadmap, but in practice containerized environments are usually a natural fit for Ogoron rather than a problem. The container boundary gives us a fairly clean and unified system-under-test, which is often helpful for automation
We had a rather vivid discussion in the team on how to best run Ogoron trials on Product Hunt. The result is that we provide two modes:
- Bring Your Own Key. Use your own OpenAI API key during the trial, without limitations.
- Use an Ogoron-managed OpenAI API key during the trial. This has somewhat limited functionality but hopefully lets understant the product utility.
I am eager to hear the pros and cons of these approaches from the Product Hunt community
Time Tracking for Jira by Standuply
@nick_mikhailovsky1 BYOK makes sense for power users, but I’d optimize for a frictionless first experience with a managed key and move people to BYOK after they see value.
Does it learn from past bugs to improve future test generation? We had a recurring issue with timezone handling - would it catch that next time?
@artem_galeev Thank you for the great question! You correctly noted that Ogoron generates tests but don't run the tests by itself. And in a strong ML sense it does not learn from the bugs. But all the tests and their results eventually get into the context Ogoron uses, so in a sense it does learn
If a product replaces a system analyst and a QA engineer, can it handle complex business cases that are not visible in the code or UI?
Thank you for the great question!
@iosfixed A lot of business cases can actually be derived from the website copy and public documentation. All the business cases that Ogoron have derived are available for the human review in the for humans tree. You can also put the documentation into the repo and Ogoron will use it.
We do have the integrations with Jira, Confluence and Notion in the product backlog. Drop me an email and I will let you know when the integrations arer available
Does it work with Cypress instead of Playwright for UI tests? Our team has invested heavily in Cypress and would prefer not to rewrite everything.
@lordice222_james James, please drop me a email at nickm@ogoron.com. We had Cypress in our product map, but not immediately. If you are ready to start immediately using ogoron if we suppurt Cypress, we can move Cypress up in the backlog
Ogoron
Hi everyone! I’m the Chief Marketing Officer at Ogoron
We built this product to change how we ship. As a team with a strong development background, we were tired of slow releases, constant regression risks, and heavy QA cycles.
So over the last few months, we created a tool that reads your code, generates test cases, and keeps regression coverage up to date. Now we ship features to production faster, with close to zero bugs, and no longer think about scaling our QA team.
Would love to hear your thoughts and really appreciate your support.