Your AI finally understands
your product

Give your AI a human-level understanding of your product

GitMir delivers a living model of how your product works — directly to your AI via MCP.

Repositories, documents, conversations, services and data go into GitMir Intelligence. Out of it come business logic, features, answers, legal, scheme fragments, decisions, metrics and architecture of Supabase Studio: An unpaid invoice restricts the organization; Billing & Subscription; Where is it riskiest to make a change?

The main areas of Supabase Studio and how they connect; the customer path above lives in Billing & Subscription.

See what a commit changed in your product

How the business logic of upgrading a plan changes over 4 commits. Commit 00, Instant upgrade: An upgrade changes the plan at once and turns the paid features on in the same moment. Commit 01, Verify the card: “Unlock at once” is gone: the new plan waits for the card check, paid features turn on once payment is verified, and the customer is asked to finish the check. Commit 02, Require owner permission: “Any member can upgrade” is gone: only a billing owner upgrades the plan; a member asks the owner instead. Commit 03, Add confirmation: “One-click upgrade” is gone: the owner confirms the new price before paying; an upgrade confirmation and a sales follow-up are added.

Give your AI a human-level understanding of your product

Supabase Studio product map. GitMir opens Billing & Subscription: the customer path “Change an organization's plan”, the status flow “Invoice status” and the rules “An unpaid invoice restricts the organization” and “The spend cap decides whether an overrun costs money or availability”. An unpaid invoice restricts the organization: Billing & Subscription → Organization · Project. The spend cap decides whether an overrun costs money or availability: Billing & Subscription → Usage · Project Settings. Billing & Subscription links to Project (6 links), Organization (4 links), Usage (3 links), Project Settings (3 links).

The whole system, in one model

An illustrative payments company as one model: business logic (onboarding, payments, refunds, invoices, partner payouts, closing accounts), the rules and constraints that govern it — each tied to the code and the policy where it is written — the security layers over it, and the AI agents and people who act inside it. The model finds where a rule is not enforced, and traces one refund from a support agent through approval, roles, card data and the audit log.

See what a change affects before it merges

What could break if the plan upgrade changes? A pull request changes 4 files; the model shows it reaches 8 areas, 8 records and the customer path “Change an organization's plan”, 6 areas and 3 records of them outside the diff.

Give every agent the product understanding its task needs

An agent asks over MCP: What happens to a paused subscription after 30 days? The answer names the commit the model was built from, 7a3f91c; a newer push, c41e0b8, is not in the model yet, so the answer is marked STALE and the agent is told to say so.

Check a PRD against what the product does

Moving to a paid plan: what we want to change: 8 requirements held against the Supabase Studio model before estimating — 4 already work, 2 contradict the product, 1 new, 1 need a question. The document says “A customer with an unpaid invoice can upgrade right away.”; the product says “It also blocks specific operations elsewhere — deploying a read replica, linking an AWS Marketplace contract, changing plan.”. The document says “Organizations billed through AWS Marketplace can upgrade in the dashboard.”; the product says “Organizations billed through Vercel or AWS Marketplace are sent to those places instead, since the subscription is not Supabase's to change.”.

Find what is wrong before a customer does

GitMir read Supabase Studio without being asked: 30 findings, 8 high. 124 move(s) in this product are possible with nothing recorded about who may make them or when — 54 of them on records marked sensitive. Invoice status has 3 states nothing leaves: paid, void, uncollectible. JWT secret rotation has 2 states nothing leaves: restarted_api_services, failed. One service in Project reaches 33 of 34 areas. On push 95954ab81b: Touched the Project record and its status. Pause failed, Restore failed and Provisioning failed still have no way out — check what a person sees there.

The whole system, in one model

An illustrative payments company as one model: business logic (onboarding, payments, refunds, invoices, partner payouts, closing accounts), the rules and constraints that govern it — each tied to the code and the policy where it is written — the security layers over it, and the AI agents and people who act inside it. The model finds where a rule is not enforced, and traces one refund from a support agent through approval, roles, card data and the audit log.

A global repository of how software works

GitMir Global Mind. 8 real products are modelled in public today: Supabase Studio, OpenAI Codex, cal.com, Atlas, Warpdrive, DroneOps Command, Pronto, Faktorio. 10 more public repositories are being modelled now and 95 are in the queue.