Mocha portfolio rescue, not a demo

Seventy apps need a rescue queue.

rescue.site is built for portfolio-scale app salvage: upload Mocha exports one by one, triage every app, generate a real preview, lock payment until approval, then hand off a portable package and dashboard.

70Mocha apps supported
48hPreview window
0Zip before payment
1Paid package
Portfolio mode

Every app gets a record, not a screenshot.

The system now treats each upload as a tracked rescue job with status, preview URL, payment lock, package path, dashboard, and expiration.

What happens for each Mocha app

  • Export is stored and inspected.
  • Mocha code, D1 dump, assets, users, and secrets are mapped.
  • Rescue package is generated server-side.
  • Local hosted preview is launched at a rescue.site URL.
  • Payment unlocks dashboard and rescue.zip only after preview works.

How the 70-app backlog should run

  • Process apps in priority order: revenue, customers, data risk.
  • Upload the next export through the intake flow.
  • Use the preview URL as the acceptance checkpoint.
  • Paid packages move to dashboard and handoff.
  • Failed previews stay blocked and visible until fixed.
Real pipeline

Built to show work step by step.

No timer theater. The tracker reflects the current intake record and background job state.

01

Inspect

Detect Mocha exports and read what the package proves before asking questions.

02

Package

Create portable source, SQLite handoff, asset manifest, auth transfer, and deploy notes.

03

Preview

Run the rescued app behind a rescue.site URL with module proxying and 48-hour expiration.

04

Gate

Checkout remains locked until a working preview exists. The zip never leaks before payment.

05

Dashboard

Paid customers get a rescue dashboard with preview, package download, and handoff state.

06

Handoff

Railway remains the final target. The current preview runner keeps sales moving while Railway automation is hardened.

What is real today

The first app is not the product. The queue is.

RealPainFinder proved the path: upload, inspect, package, preview, payment lock, dashboard unlock. The next step is running the remaining Mocha exports through the same queue and hardening the ops around it.

Start the portfolio rescue.

Upload the next Mocha export. We will triage it, preview it, and keep payment locked until the app can be seen.