# Build brief — a focused alternative to Rephrasy

> **Verdict:** Not faithfully · **Buildability:** 31/100 · **Category:** AI Writing
> **Source:** https://www.canitbevibecoded.com/rephrasy
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Rephrasy. Verify current pricing and capabilities before acting.

## Context

**Rephrasy** — Humanize AI text so it reads naturally and passes AI detectors like GPTZero, Turnitin, and Copyleaks. It currently costs $18.99/mo.

You can one-shot a rewriting wrapper that makes text sound less robotic, and for that job the DIY build is genuinely fine. What you cannot one-shot is the actual product: custom fine-tuned models plus a continuous evaluation loop against detectors (GPTZero, Turnitin, Copyleaks, Pangram) that retrain specifically on LLM-rewritten text. A prompted rewrite moves detector scores inconsistently, and detectors drift monthly, so a static prompt that works today quietly stops working. If your bar is 'reads naturally', build it; if your bar is 'passes detectors reliably', the moat is the model and the eval treadmill, not the text box.

This brief describes a focused, single-operator replacement for the part of Rephrasy that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Paste text, rewrite it with an LLM prompt tuned to cut AI tells and vary sentence rhythm, diff the result, and iterate until it reads naturally.

- Wrap a model API in a focused drafting, revision, and export workflow.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Data and integrations

- OpenAI/Anthropic API key.

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build me a local AI-text humanizer workbench. This is the honest consolation build: it makes AI text read naturally, it does NOT promise to beat AI detectors.

Stack: Node 22 + Express, vanilla JS frontend, SQLite via better-sqlite3. No build step.

- One page on localhost:5180: input textarea left, output pane right, a Humanize button, and a strength select (light touch / standard / heavy rewrite).
- Humanize calls an LLM (Anthropic or OpenAI, key in .env) with a fixed system prompt per strength level that: varies sentence length and rhythm, cuts hedging and filler ('delve', 'moreover', 'it's important to note'), swaps uniform paragraph shapes for uneven ones, and keeps meaning, facts, names, and numbers intact. Stream the output.
- A word-level diff view between input and output (the `diff` npm package) so I can see exactly what changed.
- A Re-roll button that re-humanizes the current output with a different seed phrase in the prompt, keeping the last 5 attempts switchable via tabs.
- Every run saved to SQLite: timestamp, strength, input, output. History page with the last 100 runs and copy buttons.
- Cmd+Enter runs humanize.
- .env.example with the key name; README states clearly: output is for readability, no detector-bypass guarantee, and text leaves the machine only for the LLM call.
- Out of scope, deliberately: detector score checking, browser extension, accounts, multi-language tuning, API access.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Fine-tuned models trained specifically to survive AI detectors.
- Continuous re-testing as GPTZero/Turnitin/Copyleaks/Pangram update.
- Built-in detector scoring to verify output before you use it.
- 50+ language support and custom writing styles.
- Chrome extension and REST API.

## What you still own after launch

- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.

## Risk

**Manageable.** A personal version is realistic if you test the critical journey and keep reliable backups.

Editorial confidence in this assessment: medium. No reviewed project implementation is linked yet.

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/rephrasy