MessyAI built your app. MessyProof tells you what it actually built.
Connect your project and understand its architecture, dependencies, integrations, changes and production-readiness signals in plain English — with the evidence behind every statement.
MessyProof reads your repository. It never builds, edits or deploys your application.
The problem
AI can ship a working product in an afternoon. It rarely leaves you with an understanding of it.
You own software you cannot explain
You can demo it. You cannot say which services it depends on, or what breaks if one changes.
Changes arrive invisibly
A prompt rewrote your auth logic last Tuesday. Nothing told you, and nothing recorded it.
Readiness is guesswork
"Is this safe to launch?" gets answered by vibes, not by a list of checks with evidence.
How MessyProof works
Connect your repository
Authorise GitHub and pick a repository. MessyProof reads it — it never builds or modifies your application.
Run a Proof Scan
Every check is named, run against real repository evidence, and recorded with its result and score contribution.
Read your App Passport
A living document of what your app is made of: stack, data, auth, integrations, deployment and discoverability.
Watch what changes
Each new scan is compared with the previous one, so you can see exactly what moved since last time.
A Proof Score you can audit
One number from 0 to 100 across ten categories — Architecture, Security, Authentication, Database, Dependencies, Integrations, Deployment, Monitoring, Reliability and SEO / discoverability.
Click any category and you see every check that ran, whether it passed, the evidence used, and exactly how many points it contributed. Nothing is an opaque AI opinion.
The Proof Score reflects detectable configuration and implementation signals. It is not a guarantee of security or production readiness, and findings should always be reviewed.
Example figures from a demo project.
The App Passport
A living document of what your application actually is — regenerated on every scan.
- Project nameorchard-storefrontDetected
- Repositorydemo-org/orchard-storefrontDetected
- Primary languageTypeScriptDetected
Environment variables appear by name only. MessyProof never reads or stores secret values.
Architecture Map
Frontend → API and server functions → authentication → database → external services, drawn from repository evidence. Click any component to see what it does, what depends on it, and the exact evidence used to detect it.
Change Intelligence
Each scan is stored as a snapshot and compared with the one before it.
What changed?
12 files changed since your previous scan. 1 authentication-related change, 2 database-related changes, 1 new dependency, 0 critical findings introduced.
Proof This Change
Ask “What happens if I replace Supabase Auth with Clerk?” and get the estimated change surface across authentication, database, API and billing — based on detected relationships in your project, not a guarantee.
Ask Messy
An assistant that only answers from your stored analysis, citing the file, dependency, configuration or finding behind each statement. If the evidence does not cover your question, it says so.
- What database am I using?
- How does authentication work?
- Which external services does my app depend on?
- Explain this repository like I'm not a developer.
Security
- Provider requests run server-side. GitHub tokens never reach the browser.
- Connection credentials are encrypted before storage.
- Row-level security isolates every account's repositories, scans and findings.
- Repository contents are treated as untrusted data. No repository code or script is ever executed.
- Environment variables are recorded by name only — never by value.
Pricing
Pro
$19/month
- · 5 projects
- · Continuous scans
- · Full App Passport
- · Change Intelligence
- · Proof This Change
- · Metered Ask Messy
- · Advanced findings
Paid plans are not yet accepting payments. Checkout activates once payments are configured.
Team
$49/month
- · 15 projects
- · Team members and shared projects
- · Advanced monitoring
- · Audit history
- · Team permissions
Paid plans are not yet accepting payments. Checkout activates once payments are configured.