Repowise hosted

Your laptop sleeps.
Your codebase doesn't.

The open-source CLI knows your code while you run it. repowise.dev keeps knowing it, for you and everyone you work with, with the same engine. Here is one ordinary working day, and what hosted does at each point that a laptop can't.
Start freeCompare plans

  1. 9:00

    Already up to date

    A teammate pushed at midnight. When you open your laptop, the architecture map, the docs, the hotspots and the health scores already include that change.

    repowise.dev watches the GitHub repo. Every push starts a fresh index in the cloud, with a check every 30 minutes as a backup. Nobody has to remember to run an update, and nothing runs on your machine.

    Why the laptop can't

    A local index only moves while your laptop is on and the CLI runs. A teammate's midnight push waits until you pull and update.

    Pro and Teams: a new index on every push. Free: public repos with a Repowise badge refresh every week.

    How auto-sync works
    repowise.dev/repo/repowise-dev/repowise

    repowise-dev / repowise

    Codebase intelligence for AI and humans: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions via MCP.

    Indexed at 38bf3c52h agoUp to date with upstreamRefreshes on every push

    repowise.dev/repo/repowise-dev/repowise: up to date with upstream, refreshed on every push.

  2. 10:40

    Ask from anywhere

    On the train, you ask Claude why checkout got slow, from your phone. The answer comes from your real code: the function, the callers it reaches, the commit that changed it.

    Every repo on repowise.dev has its own MCP address. Add it to Claude.ai, Claude Desktop or ChatGPT as a connector, sign in once, and the tools your coding agent uses on your laptop work in the browser and on your phone too.

    Why the laptop can't

    A local MCP server listens on localhost. Claude.ai, ChatGPT and cloud agents run on other people's servers, and they cannot reach localhost.

    Free on public repos (AI answers come from the free 10 a month). Private repos: Pro and Teams.

    Connect Claude.ai or ChatGPT
    repowise.dev/repo/repowise-dev/repowise · Use in your agent

    Use repowise-dev/repowise in your agent

    https://api.repowise.dev/mcp/repowise-dev/repowise

    • Claude Code
    • Claude Web / Desktop
    • Cursor
    • Codex
    • VS Code
    • Windsurf
    claude mcp add --transport http repowise \
  https://api.repowise.dev/mcp/repowise-dev/repowise \
  --header "Authorization: Bearer rw_live_xxxxxxxx"

    Try asking

    get_answer("how is repowise put together?")
    get_why("why is repowise structured this way?")

    Every hosted repo has its own MCP address, with setup for each app.

  3. 11:15

    The review is waiting for you

    A pull request opens. Before anyone looks at it, the PR bot has posted one comment: the callers the change reaches, the files that usually change with it but were left out, and the tests to run first.

    A merge check sits beside it, so a risky change waits for a second look. When a pull request is fine, the bot stays quiet.

    Why the laptop can't

    A comment on a pull request needs something listening to GitHub all day, for every pull request, including the ones you did not open.

    Free on public repos. Private repos: Pro. Teams covers the whole organization.

    See the PR bot
    A real AI review thread on repowise-dev/repowise #3615, as GitHub shows it: the bot flags a P1 on lazy_load.py (a generator input leaves the new Java pass with no files), says how it checked, and the author replies that commit 43ee3dc fixed it with a test.
    repowise-dev/repowise #3615: an AI review point, fixed before merge.

  4. 14:30

    A leaked key, caught early

    The scan of your whole git history finds an API key someone committed months ago and deleted the next day. It is gone from the code, but it is still in the history, and it still works.

    After every index, repowise.dev scans every commit for secrets, and every night it checks your dependencies against newly published vulnerabilities. On Teams, the alert can also go to a Slack channel.

    Why the laptop can't

    A nightly check needs a machine that is on at night. A scan you have to remember to run finds the key after someone has used it.

    Pro and Teams. Slack alerts: Teams.

    See the security view
    The Repowise security view for repowise-dev/repowise: 40 code patterns in source, 3 high, and a fix-first queue with an AI prompt for each finding.
    repowise-dev/repowise: the security view, with what to fix first.

  5. Friday

    The week, at a glance

    Friday afternoon, the team looks back at the week: which repos got healthier, which files keep getting worse, and who owns what.

    Team workspaces put every repo in one place, indexed once and shared with every member, with health over time and rollups across repos.

    Why the laptop can't

    Every laptop keeps its own index at its own commit, so nobody looks at the same picture.

    Teams. Pro has workspaces with a single owner.

    How Teams works
    The code-health map for repowise-dev/repowise: every file drawn as a dot coloured by health, grouped by package, beside the files ranked from least healthy.
    repowise-dev/repowise: code health for the whole repo, the same picture for everyone on the team.

  6. Always

    No keys to manage

    Nobody on the team pastes an API key, picks an embedding model or watches a token bill.

    Models and search are included. Free accounts get 10 AI answers a month and docs built without an LLM. Pro adds $5 of AI credits every month, AI-written docs and unlimited chat.

    Why the laptop can't

    Written docs and answers from the CLI need your own LLM provider and key. Most people run it without one, and get keyword search and no written docs.

    Free: 10 answers a month. Pro and Teams: monthly credits and AI-written docs.

    Compare the plans
    The documentation for repowise-dev/repowise on repowise.dev: a repository overview page written by a model, with the page tree on the left.
    repowise-dev/repowise: docs written by a model on repowise.dev, with no key from the reader.

See your own repo hosted.

Paste a GitHub repo. A public one is indexed free, with no card.

See pricing
Start freeBook a demo