Learning and careers decision

Papernity

A single technical user can build a useful source‑grounded editor and PDF assistant, but reproducing Papernity's large indexed corpus, full connector coverage and polished workflows (the vendor's claimed 200M+ indexed works and integrations) is impractical, so building replaces part of the product but not the complete offering.

Visit website
You pay

$49/mo

$588/yr

Read off the official pricing page.

You’d pay instead

$100one-off120 h to build

$100/mo6 h/mo upkeep

On cash alone, building overtakes the subscription at 3 seats.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • Upload PDFs and references → retrieve supporting passages and external literature → generate source-grounded thesis/article sections in an editor → attach verifiable citations and export bibliography.

What it still won’t have

  • The vendor's indexed 200M+ academic works and built-in literature coverage
  • Tight connectors to CrossRef / OpenAlex / PubMed / Semantic Scholar as packaged
  • Polished, integrated UX for thesis-to-article workflows (Journal Finder, formatting)
  • Brand trust, existing user reviews and usage data

What remains hard

  • Proprietary dataYour draft is checked against 200M+ indexed academic works.
  • Integration maintenanceCrossRef · OpenAlex · PubMed · Semantic Scholar
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 3 seats.

Paid seatsseats

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

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

Not run yet
Build a minimal self-hosted academic writing workspace using Next.js + PostgreSQL + Celery (or Bull) for background jobs, a file store (S3-compatible), and an LLM provider (OpenAI or Anthropic). Core features in scope: PDF upload and passage extraction (pdfminer/textract + passage indexing), simple ingestion connectors to CrossRef/OpenAlex and metadata fetch, local embedding index (weaviate or pgvector) and semantic search, a rich-text editor that can insert inline citations, a Retrieval-Augmented-Generation endpoint that returns generated text plus source snippets, credit metering per action, and APA/MLA/IEEE export. Out of scope: indexing a 200M+ corpus, journal finder, multi-tenant billing dashboard. Include authentication, error handling, unit and integration tests for ingestion, retrieval, and citation export, and deployment scripts (Docker + Kubernetes or managed cloud).
How we checked3 sources · 3/3 runs agreed · evidence score 59

How the score was reached

  • Partly verdict base52
  • 3 cited sources+3
  • Price verified on pricing page+3
  • 3/3 assessment runs agreed+4
  • Hard moats found in the evidence-3
  • Evidence score59

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 2 moats quoted from the page