Orviqa

Orviqa features

Orviqa reads a GitHub repository, works out who the project is for, and helps you reach those people and keep at it: what to fix first, where to post and what to say, what to do next each week, and what changed after you did it. Nothing is posted without your approval.

Understand the project

What the project is, who it is for, and what is holding it back.

Audience and positioning from the code

Reads the repository source, not just the README, to work out who the project is for and how to describe it.

The audience and positioning are derived from what the code actually does, so the first step of promoting a project is written down instead of carried in your head.

README audit

Names what is missing from the README and what to change, ordered by how much it costs you, with the copy to paste in.

The rules come from a published study of 2,069 public READMEs whose own error rate was measured against hand-scored labels.

Where the project standsno token cost

One sentence and five parts (README, repository basics, findability, follow-through and measurement), each rated strong, ok, weak or unknown.

Each rating shows the rule that produced it, the evidence and the next step. There is deliberately no overall score and no adoption part, because stars are not users and a single number would hide which part is weak.

Reach the people it is for

Where those users already are, and what to say there.

Named communities, with a draft for each

Finds the communities where the project’s audience already is and drafts a post in the form each one expects.

Where a community does not welcome self-promotion, it says so and suggests taking part without promoting instead of drafting a post about the project.

Growth Inbox

Public discussions on Reddit, Hacker News, GitHub and Bluesky where the project might genuinely answer what someone is asking, ranked.

Each one says why it matches and how risky promoting there would be. Replies to Reddit and Bluesky threads are drafted for your approval, and Reddit replies are capped at five a day and two per subreddit.

Scheduled discovery

Searches for new discussions weekly, twice a week or daily, within a weekly token limit you set.

It is off until you choose a cadence. Manual searches count against the same weekly limit, and a run does not start without enough left to finish an evaluation.

Feedback that changes the search

A community or search you keep marking as not relevant is skipped.

A place marked not relevant at least three times in 90 days, with nothing ever drafted from it, stops being searched. Each rule is listed with its reasons, and you can keep a place anyway.

Publishing you approveno token cost

Approved drafts go to Reddit, Mastodon, Bluesky, DEV, Hashnode, X, LinkedIn, Discord and GitHub releases, now or at a time you choose.

Nothing is posted without an approved draft. Before posting it checks whether the account is silenced and whether the destination accepts the post, and a scheduled post is checked again at the moment it goes out.

Keep going after the launch

The work that usually stops after the first week.

30-day growth plan

A month of tasks built for the project, starting with fixing the repository before any posting.

Every task says how to do it: a prompt for your coding agent, a button that drafts the post, or a short list of steps. Tasks that carry out repository fixes complete themselves when the fixes are done.

Next actionno token cost

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.

It says what the recommendation rests on, how much effort it takes and what it needs, so you can judge it rather than take it on trust.

Release announcements

Finds new GitHub releases each day without a webhook, reads every commit since the previous tag, and drafts an announcement.

Drafts are prepared when you ask, or automatically for each release worth announcing if you turn that on for the repository. Either way they are ordinary drafts that nobody posts without approval.

Weekly growth reviewno token cost

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.

It goes to workspace owners with a verified email, only in a week with something to report, and is assembled from what was recorded without calling a model. It can be turned off in Settings or from a link in the email.

Measure without fooling yourself

What changed, and what the numbers cannot tell you.

GitHub traffic history past 14 daysno token cost

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.

Views and clones are kept per day. Referrers and pages are kept as the 14-day windows GitHub reports, never presented as daily figures. GitHub only shows traffic to people with push access, so where the connection cannot read it, the page says traffic is unavailable rather than showing zeros.

Growth timelineno token cost

The last 60 days, with each thing you did beside that day’s stars, views, clones, site visitors, tagged arrivals and new referrers.

Each action’s views over its day and the two after are compared with every three-day window in the previous four weeks and described as above, within or below the usual range. It never says an action caused a change, and a day with unusual views and nothing recorded is shown as unexplained.

A record of every postno token cost

Every post it published, with the live link, and every one that failed and why.

The public project page counts its own views and clicks through to GitHub, and campaign-tagged arrivals can be read from GoatCounter if your project site uses it.

Work with your tools and team

Where the work happens.

Coding agents over MCPno token cost

Connect Claude Code or another coding agent, tell it to fix what Orviqa found, and it receives every finding with the steps and rules for each.

The agent prepares the changes in your own checkout and commits only what you approve. Each finding it completes shows as done on your dashboard.

Team workspaces

Several people on the same projects, with owner, admin and member roles, invitations bound to one verified email, and shared credit.

Background work for a team uses an owner’s GitHub connection, never a member’s.

What costs tokens

Only what calls a model: analysing a repository, researching an audience, evaluating discussions and drafting posts. Everything marked “no token cost” above is free to use as often as you like. The rest of the pricing, and the free credit new workspaces start with, is on the pricing page.