□ saas-rebuild
Evidence-driven system identification

Prove what your SaaS actually does.
Keep every byte of your data.
Rebuild only what you need.

Most companies pay for all of a SaaS product, use a fraction, and can't say which fraction. SaaS Rebuild gives every feature an evidence-cited KEEP / SIMPLIFY / DROP / DEFER verdict, exports and checksums everything you can reach whether or not you keep it, and validates any replacement by replaying your own history. This workspace runs the open protocol in your browser, guided by Claude, with your own API key.

Open the workspace Browse extraction recipes

01Bring your own key

The app is fully static. Your Anthropic API key is stored in your browser's localStorage and sent only to api.anthropic.com — there is no backend, and the key never touches any other server.

02Feed it evidence

Paste exports, audit-log samples, contract line items, interview notes, and screenshots-as-text. The protocol classifies every feature KEEP / SIMPLIFY / DROP / DEFER with typed citations — configuration alone never proves use.

03Take the artifacts

The assistant emits teardown.json, feature-inventory.json, usage analysis, preservation manifests, and a rebuild plan as downloadable files that follow the project's published JSON schemas. The browser cannot run the validator; check the downloads with the one in the repository.

Authorized use only. Run this only against software and data you own or administer. The protocol's first guardrail is confirming tenant ownership; it prefers official exports and documented APIs, never captures credentials, and treats extraction legality as a checklist, not a vibe. See the responsible-use notes.
Heavy LLM usage. A full teardown is a long, multi-phase conversation with a large protocol prompt. The workspace enables prompt caching and lets you pick the model; expect real API spend on a serious engagement. Claude Opus 5 is the default; switch to Sonnet 5 or Haiku 4.5 for lighter passes.
Loaded the SaaS Rebuild protocol. Start by telling the assistant which application you want to tear down and whether you have live tenant access or an engagement-document archive. It will open with the Phase 0 scoping questions.
ready

Extraction-recipe corpus

Schema-validated, vendor-document-derived extraction recipes covering documented export rights, API/export routes, role and SKU gates, retention clues, and preservation concerns. A recipe is a route hypothesis, not proof about a tenant — re-verify against current documentation and the live account before use.