Orviqa

Open-source launch planner

Describe the project and who it is for. You get a launch plan built for it: what to fix first, which communities fit and which to skip, a dated checklist, draft outlines for each channel and what to measure instead of stars. No signup, and nothing is posted for you.

Optional

With a repository, the readiness checks use what its README actually contains.

0 / 400

One or two sentences. The first sentence is used in the drafts.

Optional

How the plan is made

By published rules, not a language model, so the same answers always produce the same plan and nothing is invented about your project.

  • Readiness starts from what every launch needs (a README that explains itself, installation that works, a demo, a licence, a release) and adds items for your objective: good first issues if you want contributors, an upgrade guide for a major release. With a public repository, items are marked done or to do from the README quality checker's reading of its README.
  • Channels are rated for fit from your category and audience. Product Hunt is only suggested for applications, Lobsters only for low-level developer tools, DEV only when the audience is developers. Each comes with what to check before posting, never a claim that a community allows promotion.
  • The checklist is dated backwards from your launch date when you give one, and spreads posting over weeks rather than one day.
  • Drafts use your project's name and first sentence and leave everything else as brackets, because a post only works in your own words.
  • Measurements depend on what kind of project it is: downloads and dependents for a library, image pulls for a self-hosted app, first-time contributors if that is your objective.

Launch questions

How do I find relevant communities for my open-source project?

Start from the people, not the platforms. Write down who has the problem your project solves and where they already ask about it: the forum or chat of the language or framework you build on, the subreddit where the problem comes up, the newsletter they read. A small community where the problem is discussed every week is worth more than a large general one.

Then read each one before posting. Look at the rules, the posts that did well and the ones that were removed. The planner suggests where to look for your category and audience; it does not know any community's current rules, so it always tells you to check them.

How can I promote an open-source project without spamming?

Post where the project genuinely fits, one community at a time, written for that community, and stay to answer questions. Share the problem and what you learned, not only a link. Take part in a community before you post your own work there, and never ask for upvotes.

How do I measure open-source adoption?

Use several signals, because no single one measures use. Package downloads and dependents show installs, GitHub's traffic page shows which sites sent visitors, and issues and discussions opened by people you do not know show someone tried it. Stars are a cheap bookmark: worth watching as a trend, not as the goal.

How does the planner decide what to recommend?

From fixed rules, not a language model. Each channel has a rule that rates its fit for your category, audience and objective as strong, later, or not recommended, and the readiness list, checklist and measurements change with your objective. If you give a public repository, its README is checked with the README quality checker and readiness items are marked done or to do from what it actually contains.

Does the planner post anything or store what I enter?

No to both. It never posts: drafts are outlines for you to finish, check and post yourself. What you enter is used to build the plan and is not saved.

Related: the best communities for open-source projects · the open-source launch checklist · GitHub stars vs active users · check readiness locally with your coding agent (Orviqa Lite)