Executive Summary

Amp wins overall.
Claude leads maintainability.

Based on the current code, Amp is the stronger overall implementation. Claude remains the cleaner engineering baseline for long-term ownership.

Current Overall Score
72.8 / 100

Balanced toward current app strength, security, product completeness, and operational practicality.

Maintainability Lens
74.4 / 100

Weighted toward architecture, code quality, observability, testability, and refactor safety.

Best Current App Amp is the stronger app to demo, pilot, or compare as a product.
Best Code Shape Claude is the easier codebase to reason about, refactor, and hand to another engineer.
Security Read Amp edges ahead because Claude ships a hardcoded API key and weaker runtime defaults.
CVE Read `pip-audit` found no known vulnerabilities in either Python requirements file.
Why Amp Leads

Why Amp Ranks First

TLS verification bypass is opt-in behind `ALLOW_INSECURE_MODEL_DOWNLOADS=1`.
CORS is configured from `ALLOWED_ORIGINS` instead of relying on a wildcard default.
Published-entry deletion enforces ownership checks.
Frontend modules use same-origin relative URLs instead of hardcoded remote backends.

What Keeps Claude Competitive

Cleaner architecture Claude has the smaller, clearer server and shared frontend layers.
Better observability style Claude uses structured logging instead of mostly `print(...)`-based diagnostics.
But critical security debt remains `run.bat` contains a hardcoded OpenAI API key, blank `APP_PASSWORD`, and the server keeps weaker CORS/auth defaults.
Amp guarded TLS Amp CORS Amp delete checks Claude hardcoded key
Scorecard

Balanced Lens

Answers: which implementation is stronger overall?

Maintainability Lens

Answers: which codebase is healthier to evolve?

Executive Read

Amp wins because its richer product scope outweighs the remaining security and structural debt.
Claude leads on engineering shape and maintainability.
This is a current-product winner versus long-term-structure winner split.
Visuals

Current Total Scores

Balanced score chooses Amp. Maintainability score chooses Claude.

Key Tradeoff Pattern

Amp dominates product-facing criteria. Claude dominates code-health criteria.

Amp
Claude
Recommendation

Management Recommendation

For demo, pilot, or product comparison Choose Amp. It is the stronger current implementation.
For long-term code stewardship Use Claude as the model for how the code should eventually be organized.
Immediate action Remove Claude's hardcoded API key and weak launcher defaults if that version remains in use.
Next engineering action Reduce Amp's structural debt by splitting `server/server.py` and `static/common.js`, then add a small regression suite.

Artifacts

The report, markdown findings, and both presentation decks reflect the same comparison.
Detailed deck remains available for technical review.
Markdown findings match the same verdict and rationale.
Report Findings Detailed deck Executive deck
Bottom line: Amp is the stronger product today. Claude is the stronger long-term code organization pattern.
1 / 5
← Swipe to navigate →