
Orviqa is a tool that reads your GitHub repository, works out who your project is for, and gives you a plan: README fixes, where to post, and a draft for each.
A startup from St Helens, the United Kingdom, founded by Bright Oparaji.
This page is designed to help you find out whether Orviqa.dev is good and if it is the right choice for you.
Orviqa (orviqa.dev) is for maintainers of open-source projects who have shipped something good and cannot get it found. Connect a GitHub repository and Orviqa reads the source, not just the README, then:
Nothing is posted without your approval, and where a number is needed that does not exist, you get a placeholder rather than an invented figure. Coding agents can pick up the fixes over MCP. There are free tools too: a README grader and a launch planner.
After the launch, it keeps the work going. The dashboard shows where the project stands in five rated parts, with no single score, and one next action chosen by fixed rules. It finds new GitHub releases each day and drafts an announcement from the commits. On Mondays owners get a short review of the week, only when there is something to report. It keeps GitHub traffic past GitHub's 14 days and shows a 60-day timeline of what you did beside what the numbers did, without claiming one caused the other. Discovery can run on a schedule within a weekly token limit, off until you turn it on. The ratings, next action, review, traffic history and timeline cost no tokens. Full list: https://orviqa.dev/features
Listed in
Audience and Positioning
Works out who the project is for and how to describe it, from what the code actually does
README Audit
Names what is missing from the README and what to change, ordered by cost
Communities with Drafts
Finds where that audience already is, with a draft for each venue in the form it expects
30-day Plan
A plan that starts with fixing the docs before any posting
Release announcements
Finds new GitHub releases each day without a webhook, reads every commit since the previous tag, and drafts an announcement.
Approval before posting
Nothing is posted without an approved draft; scheduled posts are re-checked before they go out
MCP for coding agents
Coding agents fetch the fixes Orviqa found and record what was done
Free Tools
A README grader and a launch planner, no account needed
Where the project stands
One sentence and five parts (README, repository basics, findability, follow-through and measurement), each rated strong, ok, weak or unknown.
Scheduled discovery
Searches for new discussions weekly, twice a week or daily, within a weekly token limit you set.
Feedback that changes the search
A community or search you keep marking as not relevant is skipped.
Next action
The single most useful thing to do now, ranked by fixed rules across failed posts, broken connections, critical README fixes, due plan tasks, discussions and releases.
Weekly growth review
A Monday email for each repository: what was posted and done, stars across the week, views, new referrers, discussions found, anything that failed, and the next action.
GitHub traffic history past 14 days
Keeps the repository’s GitHub views and clones day by day, and its top referrers and popular pages, after GitHub’s own 14 days have gone.
Growth timeline
The last 60 days, with each thing you did beside that day’s stars, views, clones, site visitors, tagged arrivals and new referrers.
Team workspaces
Several people on the same projects, with owner, admin and member roles, invitations bound to one verified email, and shared credit.
Orviqa reads the repository's source code, not just the README, to work out who a project is for. Everything else follows from that answer: the README audit, the communities it suggests, and a draft post for each one in the form that community expects. It is built for open-source maintainers rather than marketing teams. It posts nothing without your approval, and where a claim would need a number that does not exist, it leaves a placeholder instead of inventing one. Its methods are published, error rates included: the README audit rests on a benchmark of 2,069 READMEs whose own accuracy we measured and published.
Most tools in this space serve companies selling to developers: they track community activity or identify accounts to sell to. Orviqa does the maintainer's side of the job, which is getting a project found by the people it is for. It starts with fixing the docs before any posting, it drafts for named communities instead of broadcasting, and it fits how developers already work: the fixes can be picked up by a coding agent over MCP. There is no subscription. You pay for what you use, and new accounts get enough free credit for a complete analysis of most repositories.
Maintainers of open-source projects who have shipped something useful and cannot get it found: solo developers and small teams with a working project and few users. It also suits companies that maintain open-source projects and developer relations teams, who can share a team workspace with roles and shared credit.
Orviqa started from a simple observation: most open-source projects that fail to find users do not fail on code. They fail because nobody has written down who the project is for, the README does not prove it on the first screen, and the launch goes to the wrong places. Orviqa turns that work into a plan a maintainer can follow between the weeks they have time for it. We have tried to build it in the open: we published our README benchmark with its error rates, and when our own tool turned out to blame the README on almost every popular project, we tested it, wrote up the failure and fixed it.
TypeScript, Next.js and React, PostgreSQL with Prisma, the GitHub API, large language models from Anthropic and OpenAI, Stripe for billing, and the Model Context Protocol (MCP) for coding-agent integration. Hosted on Vercel, with background jobs on Fly.io.
We have collected here some useful links to help you find out if Orviqa.dev is good.
Check the traffic stats of Orviqa.dev on SimilarWeb. The key metrics to look for are: monthly visits, average visit duration, pages per visit, and traffic by country. Moreoever, check the traffic sources. For example "Direct" traffic is a good sign.
Check the "Domain Rating" of Orviqa.dev on Ahrefs. The domain rating is a measure of the strength of a website's backlink profile on a scale from 0 to 100. It shows the strength of Orviqa.dev's backlink profile compared to the other websites. In most cases a domain rating of 60+ is considered good and 70+ is considered very good.
Check the "Domain Authority" of Orviqa.dev on MOZ. A website's domain authority (DA) is a search engine ranking score that predicts how well a website will rank on search engine result pages (SERPs). It is based on a 100-point logarithmic scale, with higher scores corresponding to a greater likelihood of ranking. This is another useful metric to check if a website is good.
The latest comments about Orviqa.dev on Reddit. This can help you find out how popualr the product is and what people think about it.
Do you know an article comparing Orviqa.dev to other products?
Suggest a link to a post with product alternatives.
Is Orviqa.dev good? This is an informative page that will help you find out. Moreover, you can review and discuss Orviqa.dev here. The primary details have been verified within the last quarter. So they could be considered up to date. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.