Turn a repository into reviewable AWS migration evidence
Upload one repository ZIP or supported source file. The $299 evidence report returns the exact files and lines that matched, a severity-and-reach-ranked remediation order, and a configured rule or package reference for each matched finding. It is a static source scan—not a live AWS inventory.
Don't take our word for it.▶ Run the free scan
Check representative files locally before paying. The paid report adds archive-wide scanning of supported text files, exact line evidence, a severity-and-reach-ranked remediation order, and an evidence fingerprint.
What you get
Exact file:line evidence and observed match counts—no invented resource counts
A roll-forward order based on finding severity and observed reach
The configured rule or package reference for each finding; dependency floors are conservative triage baselines that still require target-specific verification
Explicit scope and limitations: what was scanned, skipped, and not inferred
Input SHA-256 plus a deterministic evidence fingerprint verifiable at /verify/
ZIP archive or one supported source file · one fixed price
A target date may be included as planning context. It never changes the price or scan results.
What this buys: a reviewable change-approval artifact your team can check against the uploaded repository and the linked rule or package references. No speculative downtime-dollar estimate is included.
30-day refund policy
When checkout is open, request a full refund within 30 days. Email from the purchase address with the Stripe receipt or Checkout Session identifier; no explanation is required.
If fulfillment permanently fails after retries, the system queues a full refund. Any refund that cannot be confirmed is surfaced for operator review.
Why you can trust the report (without trusting the brand)
Evidence, not estimates
Each match includes the observed file, line, and text.
Checkable references
Each finding links its configured rule or package reference; conservative dependency floors still require release and target verification.
Repeatable findings
The evidence fingerprint covers the input hash, rule-pack version, and canonical findings.
Bounded scope
The report says plainly that it does not query AWS or prove a complete inventory.
Upload a repository ZIP or a supported SAM / CDK / Terraform / Serverless / cloud-init source file (10 MiB compressed maximum)
We safely inspect supported text files without extracting the archive to disk
Get a PDF by email after automated processing; delays and retries are possible
Verify the evidence metadata at /verify/ during its retention window of up to 30 days
When the readiness gate opens: Stripe checkout · automated delivery with durable retries · 30-day money-back guarantee
Checkout safety check: waiting for the v2 fulfillment backend. Checkout stays closed unless the live API confirms report engine 2.0.
Found a relevant issue in a real project?
Checkout is paused while fulfillment is verified. If this exact one-repository
report would be worth $299 to you, record a public, no-obligation demand signal.
It is not an order, reservation, waitlist, or promise of a reply.
GitHub publishes your username and submission. Do not include repository names, filenames, code, secrets, security details, company information, or personal data.
Questions
Why pay when the CLI is free?
The CLI is the right choice for hands-on engineers. The paid product packages supported-file evidence across the uploaded archive, line locations, prioritization, limitations, and references into a shareable PDF.
Is my code safe?
Uploads travel over TLS, are used only for report generation, and are deleted after successful delivery. Unchecked uploads normally expire within 24 hours; checkout-bound uploads are retained for no more than 48 hours so retries can finish. Generated reports expire within 30 days. Prefer no upload? Use the free local tools.
How can I trust the results?
Check the exact file/line evidence and the configured rule or package reference for each finding. Dependency floors are conservative triage baselines, not guarantees of target compatibility. The report carries an input hash and evidence fingerprint. It does not claim to be a digitally signed PDF.
How fast is it?
Processing is automated, but delivery time depends on queue, runner, and email-provider availability. Failed jobs retry and unresolved failures surface for refund review.
What if it's wrong, or I'm just not happy?
Email us within 30 days for a full refund. No questions asked.