[Sprinno Website](https://sprinno.dev)
[Connect your agent (MCP)](https://sprinno.dev/docs/mcp)
[How We Score (Methodology)](https://sprinno.dev/methodology)
[Pricing](https://sprinno.dev/pricing)
[Use Cases](https://sprinno.dev/usecases)
[Startup Beta Program](https://sprinno.dev/startups)
[Contact / Request Access](https://sprinno.dev/contact)
[Twitter / X](https://x.com/sprinnoxyz)
[LinkedIn](https://www.linkedin.com/company/trysprinno)
---
# Homepage
---
title: The SAT Score for Your Codebase | Sprinno
meta-description: Know if your codebase is actually healthy. Connect Sprinno to GitHub Copilot, Lovable, v0, Replit, Claude Code or Cursor and every project gets a deterministic quality score.
---
## The SAT score for your codebase
Know if your codebase is actually in good shape, or just looks fine. Connect Sprinno to your coding agent and every project you build gets scored, tracked and explained in one dashboard.
Primary CTA: Connect your agent — https://sprinno.dev/docs/mcp (MCP server URL: https://api.sprinno.xyz/mcp)
[BOOK A DEMO](https://cal.com/sprinno)
### Trust Signals
| Signal | Description |
|---|---|
| Nothing kept | Source is deleted right after the scan; only scores and finding locations stay |
| Nothing to fake | Every signal is computed on our servers by a deterministic engine, no AI |
| Nothing to install | Connect the MCP server once in the agent you already use |
### Supported Languages
TypeScript, Python, Go, Rust, Java, Ruby, C# (.NET), PHP, and more.
[Connect docs](https://sprinno.dev/docs/mcp)
### Where it runs
GitHub Copilot in VS Code, Copilot CLI, the GitHub Copilot app, Lovable, v0, Replit, Claude Code, Cursor, Codex, and any MCP client that supports remote servers with OAuth. GitHub-hosted Copilot coding agent does not yet support remote OAuth MCP servers.
### How It Works
Your agent → Sprinno Engine → Quality Score
| Step | Component | What Happens |
|---|---|---|
| 1 | Your agent | Uploads the project files with a SHA-256 manifest through the Sprinno MCP server |
| 2 | Sprinno Engine | Checks every file against the manifest, scans it deterministically across 5 pillars, deletes the source |
| 3 | Quality Score | Returns a composite score (0-100) with a measurement error, pillar breakdown, and findings with file and line |
The agent only transports files. It never computes or reports a signal or a score.
### Key Metrics
| Metric | Value |
|---|---|
| Engineering pillars scored | 5 |
| Companies in reference benchmark | 200+ |
| AI calls in the scoring path | 0 |
| Source code kept after a scan | None |
| Verified score | Link the GitHub repo; Sprinno scans it on every push |
### Features
- Verdict-First Quality Score: Get one score you can defend — and five buckets underneath it, so anyone who asks "why?" gets a real answer, down to test coverage, linting, and CI health.
- Flagged Anomalies: Surfaces the sharpest risk signal per scan. No noise.
- Cohort Benchmarking: Know if you're ahead of or behind teams at the same stage and sector — percentile rank against peers, not arbitrary thresholds. Requires a verified (GitHub-linked) project.
- Agent fixes: Your agent reads every finding with its file, line, and fix, then re-scores to confirm the change.
- Visual Presets: Same graph, four lenses — Diligence, Investor, Signal Flow, or Blueprint.
- Guided Chapters: A story your team can walk through, not a chart they have to decode — five deterministic chapters, generated straight from the scan.
- Historical Trends: Track every version of every project across all pillars.
- Shareable Score Card: SVG card for READMEs, pitch decks, board reports.
### Who builds with Sprinno?
| Segment | Use Case |
|---|---|
| Builders on Lovable, v0, Replit | Know whether the app your agent built is production-grade, and track it as it grows. |
| Developers & Engineering Teams | Honest picture of codebase quality. Find weak spots, track improvement, benchmark against peers. |
| Investors (Solo GPs, Micro-funds, Angels, VCs) | Deterministic technical risk scoring before writing a check. Replace $50K consulting engagements. |
| Startups & Founders | Improve engineering readiness score before fundraising. Show investors your engineering is strong. |
| Due Diligence Firms | Objective, reproducible assessments during fundraises and M&A. White-label reports with enterprise. |
| CTOs & Engineering Leaders | Track team quality over time, surface risks, demonstrate excellence to the board. |
### FAQ
Q: What is Sprinno?
A: Sprinno tells you, in one number, how your codebase actually stacks up — and shows you exactly what's dragging your score down. Think of it as the SAT score for your codebase.
Q: What's public and what isn't?
A: What we measure is public: the full list of metrics and how each one is detected is in our open quality ontology. The weights that combine them into a score are calibrated from data across hundreds of repos and kept private.
Q: How do I get started?
A: Add the Sprinno MCP server (https://api.sprinno.xyz/mcp) to GitHub Copilot in VS Code, Copilot CLI, the GitHub Copilot app, Lovable, v0, Replit, Claude Code, Cursor or Codex, and sign in once. Then ask your agent to score the project. GitHub-hosted Copilot coding agent does not yet support remote OAuth MCP servers. Setup for each supported platform: https://sprinno.dev/docs/mcp
Q: How does the scoring work?
A: We use Latent Capability Scoring (LCS) — our proprietary calibration algorithm that determines which metrics actually distinguish strong engineering from weak engineering. LCS assesses your code across five pillars and empirically weights each metric based on its discrimination power. Your score is contextual to your stage.
Q: Is my code safe?
A: Your agent uploads the project over an encrypted connection. It is unpacked in an isolated workspace on our servers, scanned by a deterministic engine, and deleted as soon as the scan finishes, whether it succeeds or fails. We keep scores, file hashes, and the file paths and line numbers behind each finding, never your source code. No AI model sees your code during scoring.
Q: Who is Sprinno for?
A: Developers and engineering teams who want an honest picture of their codebase quality, including people building with Lovable, v0 and Replit. Investors and due-diligence firms also use Sprinno for objective assessments during fundraises and M&A.
Q: How is this different from static analysis tools?
A: Static analysis tools check code against fixed rule thresholds — deterministic but shallow. Sprinno assesses process maturity, architecture quality, resilience, and documentation. Weights are empirically derived from data across hundreds of repos, not arbitrary thresholds.
Q: What's the difference between an agent score and a verified score?
A: When your agent uploads a project, you get a private score you can track against your own history. Link the project's GitHub repo — including the repo Lovable, v0 or Replit syncs to — and Sprinno scans that repo itself on every push. That scan becomes the verified score of record, and agent uploads become quick previews.
Q: Can teams game the score?
A: Not easily. The agent only sends files; every signal is computed on our servers. Files that don't match their declared hashes are rejected, inline suppressions don't change the score, and a project swapped for different code starts a new history line instead of showing as an improvement.
Q: What tech stacks do you support?
A: Metrics are stack-agnostic at the pillar level. Whether you write Python, TypeScript, Go, Rust, Java, or anything else, we measure the same underlying engineering behaviors.
Q: How often does the model update?
A: The reference cohort grows with every new assessment. Parameters are recalibrated on a regular cycle. Scores become more accurate over time.
---
# Methodology
---
title: The Sprinno Methodology: The SAT for Code
meta-description: Sprinno applies Latent Capability Scoring, the same mathematical framework behind the SAT, GRE, and GMAT, to produce the first objective, reproducible standard for measuring software engineering quality.
---
## The Problem with Current Approaches
| Approach | Cost | Time | Consistency |
|---|---|---|---|
| Expert consultants | $30-80K | 2-4 weeks | Low, varies by assessor |
| Static analysis (SonarQube) | Low | Fast | High, but shallow |
| Equal-weight scorecards | Low | Fast | Misses what matters |
| Sprinno (LCS) | From $0 | Minutes | Deterministic, empirically weighted |
## Latent Capability Scoring (LCS)
The same class of mathematics used by the SAT, GRE, and GMAT to determine which questions genuinely distinguish strong students from weak ones. Applied to software engineering:
- Measure: Collect raw metrics from a reference cohort of repositories.
- Calibrate: Discover which metrics actually discriminate high-quality engineering from low-quality.
- Validate: Confirm metrics predict real-world outcomes (successful exits, failed startups, acqui-hires).
- Weight: Assign influence proportional to discrimination power.
Every new assessment grows the reference cohort, which recalibrates parameters, which improves discrimination.
> "What actually separates high-quality engineering teams from the rest, according to data?"
> — The question behind the Sprinno methodology
## The Five Pillars
Each pillar contains multiple sub-metrics weighted by empirical discrimination power.
### 01 — Code Health
The structural integrity of the code itself.
Metrics: Security posture · Test sophistication · Complexity indices · Dependency health
### 02 — Process Maturity
How disciplined the team's engineering workflow is.
Metrics: CI/CD depth · Review rigor · Commit discipline · Development velocity
### 03 — Architecture
Structural quality of the system design.
Metrics: Separation of concerns · Scalability patterns · API quality · IaC maturity
### 04 — Resilience
How well the system withstands and recovers from failure.
Metrics: Error handling · Health checks · Rate limiting · Monitoring
### 05 — Documentation
How well knowledge is written down.
Metrics: README quality · Architecture docs and ADRs · Onboarding setup · API docs
## Stage-Aware Expectations
| Stage | Prioritizes |
|---|---|
| Pre-seed | Velocity, security basics, architecture foundations |
| Series A | Process maturity, testing discipline, scalability readiness |
| Series B+ | All pillars, incident response, team resilience |
## Scoring
| Score Range | Rating | Meaning |
|---|---|---|
| 90-100 | Exceptional | Top-tier engineering across all pillars |
| 75-89 | Good | Strong fundamentals with minor gaps |
| 60-74 | Fair | Functional but meaningful weaknesses exist |
| 40-59 | Concerning | Significant risk areas that need attention |
| 0-39 | Critical | Fundamental engineering issues present |
Percentile output: Your final score is a percentile rank against the reference cohort at your stage.
- P90 (Top 10%): Exceptional engineering for your stage
- P50 (Average): Typical for companies at this stage and sector
- <P25 (Concerns): Below peers — action required
## Bias Mitigation
| Factor | How It's Handled |
|---|---|
| Stack neutrality | Metrics normalized across languages and frameworks |
| Team size | Solo founders aren't penalized for low bus factor |
| Repo age | Young repos aren't punished for limited commit history |
| Context aware | Open source vs. private repos get different baselines |
## Ensuring Accuracy
- Deterministic pipeline: Same codebase, same score. Always. No human judgment, no sampling variation, no assessor bias.
- Empirical weights only: If a metric doesn't discriminate in practice, it gets minimal weight.
- Continuous self-improvement: Every new assessment grows the reference cohort and improves discrimination.
## Transparency
Same model as FICO, SAT, and every other trusted standard: you know exactly what is measured. The exact parameters stay proprietary.
Public (You Know):
- The five pillars and their sub-metrics
- The calibration approach (LCS)
- Scoring structure (percentile, stage-aware)
- Bias mitigation strategies
Proprietary (We Keep):
- Model architecture and parameter values
- Per-metric discrimination & difficulty
- Reference cohort composition
- Stage-specific weight matrices
## Comparison
| Dimension | Sprinno | Expert Consultants | Static Tools |
|---|---|---|---|
| Method | Latent Capability Scoring | Subjective assessment | Rule thresholds |
| Consistency | Deterministic | Assessor-dependent | Deterministic, shallow |
| Scope | 5 pillars, 20+ metrics | Varies | Code-level only |
| Calibration | Empirical, data-driven | Expert opinion | Fixed rules |
| Stage-aware | Yes | Sometimes | No |
| Improves over time | With every assessment | No | Manual updates |
| Cost | From $0 | $30K-$80K/engagement | Varies |
| Time to result | Minutes | 2-4 weeks | Minutes |
| Continuous monitoring | Yes (re-scores on merge) | No (point-in-time) | Partial |
Think SAT for academic readiness. FICO for creditworthiness. Sprinno for engineering quality.
---
# Connect your agent (MCP)
---
title: Connect Sprinno to your coding agent
meta-description: Add the Sprinno MCP server to GitHub Copilot, Lovable, v0, Replit, Claude Code, Cursor or Codex. Your agent uploads the project, our deterministic engine scores it, and every project lands in one dashboard.
---
## Server
| Field | Value |
|---|---|
| MCP server URL | https://api.sprinno.xyz/mcp |
| Transport | Streamable HTTP |
| Authentication | OAuth 2.1 with PKCE and dynamic client registration. Your agent opens a Sprinno sign-in page the first time. |
| Scopes | projects:write, snapshots:write, scores:read |
## Tools
| Tool | What it does |
|---|---|
| create_project | Creates (or returns) the project handle. Save project_key to .sprinno/project.json. |
| request_upload | Sends the file manifest (paths, SHA-256, sizes) and opens an upload. |
| upload_files | Sends file contents through MCP, for hosts without a shell. |
| score_project | Checks the upload against the manifest, scans it on our servers, returns scores. |
| get_report | Findings with file, line, why it matters, and how to fix it. |
| compare | Compares two versions; only calls a change real when it exceeds the measurement error. |
| get_verification_link | A link that connects the project's GitHub repo for a verified score. |
| list_projects | Recovers project keys. |
## Setup per platform
- Claude Code: claude mcp add --transport http sprinno https://api.sprinno.xyz/mcp
- Cursor: add { "mcpServers": { "sprinno": { "url": "https://api.sprinno.xyz/mcp" } } } to .cursor/mcp.json
- Codex: add [mcp_servers.sprinno] url = "https://api.sprinno.xyz/mcp" to ~/.codex/config.toml
- GitHub Copilot in VS Code: use MCP: Add Server, choose HTTP, enter the URL, then choose Global > Copilot Global and sign in when prompted.
- GitHub Copilot CLI: copilot mcp add --transport http sprinno https://api.sprinno.xyz/mcp
- GitHub Copilot app: Customize > MCP > Add custom server, enter the URL, then follow the install and sign-in prompts. Copilot CLI and Copilot Global servers are also available automatically.
- Lovable, v0, Replit: add a custom MCP server with the URL above in the platform's integrations settings, then turn on the platform's GitHub sync and link that repo for a verified score.
- GitHub-hosted Copilot coding agent: not currently supported because it does not support remote MCP servers that use OAuth.
Full instructions: https://sprinno.dev/docs/mcp
## What is kept
Scores, file hashes, and the file paths and line numbers behind each finding. Source code is deleted when the scan finishes.
---
# Pricing
---
title: Pricing
meta-description: Connect your coding agent for free. Upgrade for percentiles, trends, and team dashboards.
---
Connecting your agent is free. Upgrade for trends, percentiles, and team features.
| Plan | Price | Includes |
|---|---|---|
| Free | $0 | Connect your agent, unlimited private self-tracking for your projects, full 5-pillar scan, version comparison. Community support. |
| Pulse | $7/month | Every-scan calibration, unlimited cloud history, up to 10 repos, unlimited fix, trend sparkline, recommendations, score projections, live badge. Email support. |
| Pro | $15/member/month (4 members minimum) | Everything in Pulse plus Company Score, team dashboard, cross-repo analysis, unlimited repos & share links, investor PDF reports. Dedicated support. |
| Enterprise | Custom | Unlimited everything, SSO, white-label reports, dedicated support. For due-diligence firms, VCs, large orgs. |
## Feature Comparison
### Scanning & Calibration
| Feature | Free | Pulse | Pro |
|---|---|---|---|
| Quality scan (5 pillars) | ✓ | ✓ | ✓ |
| Self-comparison deltas | ✓ | ✓ | ✓ |
| Cohort calibration | Monthly | Every scan | Every scan |
| Cloud history | — | Unlimited | Unlimited |
### Intelligence
| Feature | Free | Pulse | Pro |
|---|---|---|---|
| Trend sparkline | — | ✓ | ✓ |
| Targeted recommendations | — | ✓ | ✓ |
| Score projections | — | ✓ | ✓ |
| Live badge URL | — | ✓ | ✓ |
### Company & Multi-Repo
| Feature | Free | Pulse | Pro |
|---|---|---|---|
| Company Score (multi-repo) | — | — | ✓ |
| Repo role assignment | — | — | ✓ |
| Cross-repo anomaly detection | — | — | ✓ |
### Reporting & Sharing
| Feature | Free | Pulse | Pro |
|---|---|---|---|
| Share links | — | 10 | Unlimited |
| Export HTML report | — | — | ✓ |
| Investor PDF reports | — | — | ✓ |
### Team
| Feature | Free | Pulse | Pro |
|---|---|---|---|
| Team dashboard | — | — | ✓ |
### Support
| Feature | Free | Pulse | Pro |
|---|---|---|---|
| Support level | Community | Email | Dedicated |
---
# Use Cases
---
title: Use Cases
meta-description: How investors and startups use Sprinno, the SAT score for your codebase, to measure engineering quality objectively.
---
## The Investor's Blind Spot: Why Code Quality Kills Deals
Most seed investors fly blind on technical risk. A seed-stage investor reviews 200+ companies a year. Of those, maybe 15 get a term sheet. The technical evaluation for those 15? In most cases, it doesn't exist.
Traditional technical due diligence takes 3-6 weeks and costs $25,000-$75,000 per engagement — viable only for Series C+ deals. Sprinno connects to a repository and delivers a scored report within seconds, priced to run on every deal in a seed-stage pipeline.
### What Gets Missed Without Automated Scoring
- Entire product is one engineer's side-project codebase with no tests, no CI, credentials in plain text
- Bus risk: single-engineer knowledge concentration across all critical systems
- Copyleft and AGPL licence exposure creating legal risk
- Hardcoded credentials and exposed API keys
- Architecture that cannot scale past the current user count
- AI companies with no model evaluation methodology or training data provenance
### Pre-Investment Use
Run Sprinno on every deal in the pipeline. Get an objective score before the term sheet. Identify technical risk that pitch decks hide. Replace $50K consulting engagements with continuous, objective scoring.
### Post-Investment / Portfolio Monitoring
Unlike a static PDF report, Sprinno's risk score stays live and re-analyzes on every code change. A new vulnerability introduced on a Tuesday shows up before Wednesday — not at the next commissioned engagement.
---
# Startup Beta Program
---
title: Startup Beta Program
meta-description: Apply for Sprinno's Startup Beta Program. Get your SAT score for code, the first objective standard for measuring engineering quality.
---
Connect your repo. Get your technical readiness score. Show investors your engineering is as strong as your pitch.
## What You Get
| Benefit | Description |
|---|---|
| Technical Readiness Score | A single number that tells investors your code is production-grade. Updated continuously. |
| Investor-Ready Reports | Shareable reports that replace months of manual technical due diligence. |
| Actionable Fixes | Prioritized recommendations so you can resolve technical risk before it kills a deal. |
Status: Now Open — Apply at https://sprinno.dev/startups
---
# Company & Contact
| Field | Value |
|---|---|
| Company | Sprinno |
| Website | https://sprinno.dev |
| Email | contact@sprinno.xyz |
| Twitter / X | https://x.com/sprinnoxyz |
| LinkedIn | https://www.linkedin.com/company/trysprinno |
| Book a Demo | https://cal.com/sprinno |
| Terms of Service | https://sprinno.dev/terms |
| Privacy Policy | https://sprinno.dev/privacy |
| Cookie Policy | https://sprinno.dev/cookies |
---
Sprinno © 2026, All Rights Reserved
<!-- last updated: 2026-10-28 -->