[How-to] Repowise's Free Tier Covers Public Repos Only — Here's What You Actually Get

Repowise scores your code’s health and writes documentation automatically, aimed at both humans and AI tools reading your repository (a project’s code storage, usually on GitHub). It has a free tier. But before you sign up chasing that free tier, know the one limit that trips up most people: Repowise’s free plan only works on public repositories. If your code lives in a private repo, the free plan won’t touch it.

Here’s what that actually means, what the free tier can do, and where the paid plans start.

What the free plan actually includes

Repowise’s free tier gives you:

• 10 AI answers per month (AI answers are chat-style Q&A about your codebase — ask “what does this function do” and get a response)
• A single-repo size cap of 250 MB
• Commit analysis capped at 500 commits (a commit is one saved snapshot of code changes)
• Up to 2 repositories indexed at once
• A weekly auto-updated badge you can drop into your README

That’s a workable toolkit if you’re maintaining a small open-source project and want a health score plus some AI-assisted Q&A without paying anything. The 500-commit cap matters for older projects — if your repo has thousands of commits, Repowise’s free plan will only analyze the most recent 500, not your full history.

Getting started: Go to repowise.dev, connect your GitHub account, and point it at a public repository. Repowise indexes the repo, builds a health score, and starts generating documentation. You get 10 AI answers to spend that month, so save them for real questions rather than testing the feature.

Figure: repowise.dev official pricing page, captured 2026-10-08.

The wall: public repos only

This is the part the pricing page states but doesn’t shout about. Repowise’s homepage describes itself as “Built for open source,” and the free tier’s fine print confirms it: free access is public-repo-only. If you try to index a private repository on the free plan, it won’t work.

This isn’t a minor restriction. A lot of developers evaluating a code-analysis tool do so on their actual work — which, for most companies and many solo developers, means private repos. If that’s you, the free tier is effectively a demo you run on a side project or someone else’s open-source code, not a tool for your real work. You’ll hit the private-repo wall immediately and need to decide whether to pay.

Common blocker and fix: If Repowise says it can’t index your repo and the repo is private, that’s the free-tier restriction working as designed — not a bug. The fix is either to make the repo public (not an option for most private codebases) or move to a paid plan, which lifts the restriction.

When Pro and Teams make sense

If you need Repowise on private code, Pro is the entry point: US$15/month, billed monthly. That price includes US$5/month of LLM credits (a prepaid allowance covering the cost of the AI model calls behind your questions and auto-generated docs). Repowise’s pricing page also advertises “Save 20%” for annual billing, but it doesn’t spell out the resulting monthly or annual dollar figure anywhere on the page — so that’s as far as we can report it. If you want the exact annual number, you’ll need to start checkout and see the number the page quotes.

Teams is built for, well, teams: US$20 per seat per month (a seat is one person’s license), with a minimum of 3 seats. That floor means Teams starts at US$60/month, not US$20 — the pricing page states both numbers side by side (“US$60/month” and “US$20/seat/mo · 3 seats”). Annual Teams billing works out to roughly US$16 per seat per month, and the pricing page describes the discount as “about two months free” rather than a flat percentage.

Who actually needs Teams over Pro: if more than one person on your team needs independent access and AI-answer quotas, Teams’ per-seat model scales that way. A solo developer with one or two private repos has no reason to pay for 3 seats — Pro covers that case directly.

Common blocker and fix: If you’re a solo developer getting quoted the US$60/month Teams price, you’re looking at the wrong plan. Pro, at US$15/month, is the single-user option; Teams’ 3-seat minimum is specifically for groups.

Figure: compiled by AMPM from its verified data (last verified 2026-10-07).

🔍 AMPM exclusive check

We checked Repowise’s homepage, pricing page, and GitHub repo against each other rather than taking the pricing page alone at face value. The “public repos only” restriction isn’t phrased as a blunt rule inside the pricing table — it’s inferred from the homepage’s “Built for open source” framing combined with the free-tier description. A reader skimming just the pricing table’s bullet points could miss that this is a hard restriction, not a suggestion. That’s the gap between the official framing and what we confirmed: free really does mean public-only, not “mostly public, with some private access.”

Illustration: The free tier allows public access while completely blocking private repositories and strictly limiting monthly queries.

The other thing worth flagging: the annual-billing discount for Pro (“Save 20%”) has no dollar or percentage breakdown anywhere on the pricing page we checked. We’re not going to compute what 20% off US$15/month comes out to over a year — that’s exactly the kind of invented math we won’t do. If you need the real number, check out on the annual plan and read what it actually charges you.

Everything else — the free-tier limits, the US$15 Pro price, the US$5/month LLM credit inclusion, and the Teams per-seat structure — matched what’s stated on repowise.dev and repowise.dev/pricing as of our 2026-10-07 check. No other differences found this time.

Verdict: who should use it, who should skip it

Use Repowise free if you maintain a public open-source repo, want an automated health score and a README badge, and are fine with 10 AI answers a month and a 500-commit analysis window. It’s a reasonable zero-cost way to add some polish and documentation automation to a public project.

Skip the free tier — and budget for Pro at US$15/month — if your code is private. There’s no partial access or trial workaround; the restriction is structural. If you’re part of a team of three or more needing shared access, Teams starts at US$60/month (US$20/seat, 3-seat minimum), with annual billing bringing that down to roughly US$16/seat/month. Solo developers on private repos should start with Pro, not Teams.

Written: 2026-10-08 Price last verified: 2026-10-07 Tool last health-checked: 2026-10-08

🔗 Related on AMPM

• Repowise pricing & free tier

📎 Sources

All prices and quotas in this article come from AMPM’s verified dataset for Repowise (last verified 2026-10-07); primary sources:

• https://repowise.dev/pricing
• https://repowise.dev

🐾 Meet the cats: AMO and PIMI

AMPM is a Taiwan-based AI-tool pricing watchdog. Our motto: ask before you subscribe. Two cats argue every tool from two sides:

• ☀️ AMO — the budget-minded cat. Always asks: is the free tier enough, and is paying actually worth it?
• 🌙 PIMI — the performance-minded cat. Cares about whether it works well, fast, and gets your job done.

When they are done arguing, you know whether to pay. Every number is checked by us, with the verification date at the end.

🐾 Our sister sites also checked

• Travel insurance and flight-delay coverage checked
• Travel booking price checks and pitfalls