Skip to content
ADVISORY RECONCILIATION · STRIPE ↔ ENTITLEMENTSRun the browser-only CSV audit

ABOUT

A small instrument for
an expensive blind spot.

SubSync Guard exists because billing systems and product access systems drift apart quietly. The drift produces refunds, support load, and access-control risk, but it rarely produces a clean error message. This product makes the drift reviewable.

THE PREMISE

Two systems can both be
right and still disagree.

Stripe can correctly record a paid subscription while the application correctly records a free account. Neither system is broken. The integration between them is.

The usual response is a one-off SQL query, a spreadsheet, or a support ticket. Each works for a moment. None produces a durable record of what was compared, when, under which policy, and what a reviewer decided.

SubSync Guard turns that ad hoc investigation into a small, repeatable control: capture both snapshots, apply an explicit policy, produce evidence-rich findings, and route them to the people who can act.

The product is deliberately not a “revenue recovery” platform. Recovered revenue is a claim about causality and value. A reconciliation tool can show a disagreement and its evidence. It cannot honestly promise a dollar outcome without knowing the price, the access window, and the customer’s intent.

That restraint is the product. It is also why the security page, pricing page, and documentation spend time describing what is absent.

PRINCIPLES

The rules we use to
say no.

These principles constrain design, copy, and scope. They are not aspirational values on a wall; they decide what ships.

Legibility over impression

A finding should explain itself without a sales call. A capability should state its requirements. A limitation should be visible before a customer discovers it in production.

Advisory over automatic

Billing and access are consequential systems. The product produces evidence and a recommendation; a human decides whether to change a subscription, restore access, or record an exception.

No borrowed trust

No compliance badge we have not earned. No customer logo we do not have permission to use. No recovery total without a verified price and time window. No uptime number without measurement.

Narrow scope, explicit edges

SubSync Guard reads billing, receives signed snapshots, and compares them. It does not become a billing system, an identity provider, or an automatic remediation engine.

WHAT THIS IS

An independent product,
not a certification.

Independent

SubSync Guard is not affiliated with Stripe or Supabase. Product names are used only to describe integrations.

Staging today

The current release is a staging build with test-mode billing. Commercial pricing, live payments, and a support SLA are not active.

Open to inspection

The repository, migration, connector example, and release notes are available so a technical reviewer can check the claims.

Contactable

Support and security channels are real GitHub destinations. There is no invented support email and no fake office address.

THE HONEST POSITION

If the workflow does not fit, do not force it.

Start with the free audit. If your data is too incomplete to support a defensible finding, the product will say so rather than manufacture confidence.