Documents and notes decision
Scite
Do not mistake the interface for the product. Scite's durable value is data, import reliability, which a solo one-shot build cannot reproduce responsibly. The prompt therefore builds only the closest honest personal consolation tool.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off40 h to build
$0/mo4 h/mo upkeep
No published price to break even against.
The code exists. It is not what you are paying for.
This project is real, published, and does the core job — and this page still says keep paying. What the subscription buys is proprietary data, and none of that ships in a repository. Fork it anyway if you want to. Go in knowing what it does not carry. What stays hard ↓ · All Scite alternatives, with the arithmetic →
What a replacement has to do
- Build a private citation intelligence workspace that imports user-supplied URLs or files, extracts metadata, supports notes, and searches the local corpus.
What it still won’t have
- licensed scholarly metadata
- publisher-specific import reliability
- citation graph scale
- team libraries and institutional access
What remains hard
- Proprietary data
First-year cost
The build hours below are a category default, not an estimate for this product. Change them to your own numbers and the comparison follows.
No published price
Scite does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build the closest honest consolation tool inspired by Scite; do not claim to replace its structural moat. Use exactly this stack: Next.js 15 + TypeScript + SQLite + Playwright. Primary job: Build a private citation intelligence workspace that imports user-supplied URLs or files, extracts metadata, supports notes, and searches the local corpus. Start from an empty folder and create the complete working project. Make the default mode single-user and private. Store user data locally unless the core job requires the declared self-hosted database. Do not add analytics, telemetry, ads, or third-party accounts. Put every secret and external credential in .env and provide .env.example. Use realistic sample data that is clearly labelled and easy to delete. Implement the smallest polished interface that completes the core loop end to end. Include clear empty, loading, validation, success, and failure states. Add import and export so the user is not trapped in the app. Use accessible keyboard navigation, labels, focus states, and sensible contrast. Validate untrusted input and never log secrets or private file contents. Deliberately exclude these paid-product advantages: licensed scholarly metadata; publisher-specific import reliability; citation graph scale. Do not fake integrations, network effects, proprietary data, model quality, compliance, or security claims. Where an external API is optional, keep the app useful without it and explain the degraded mode. Write focused unit tests for the data model and the most important workflow. Add one end-to-end smoke test that proves the core loop works. Create a README with setup, permissions, architecture, data location, backup, and limitations. Add scripts for install, development, test, build, and a production-style local run. Run the tests and build before finishing, then fix errors rather than merely describing them.
