Cloud storage decision

Zotero Storage

A small team can implement a usable personal storage + sync service for PDFs and metadata, but reproducing Zotero’s integrations, citation-style breadth, and polished PDF UX is substantially more work and not covered by a minimal DIY replacement.

Visit website

SubscriptionCustom pricing

Initial build80 hours

Monthly upkeep8 hours + $5

Evidence2/3 runs agree

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.

cloudreve/cloudreve28,483GPL-3.0Self-hosted file management and sharing web app with user accounts and multiple storage backends.Open on GitHub haiwen/seafile15,075licence unclearFile syncing and sharing server with web UI, client sync, previews, and library-based document storage.Open on GitHub

Code Zotero Storage publishes itself

Not a way out of the subscription — these are the vendor’s own repositories. Worth a look for how they build, and for anything you would have to integrate with.

What a replacement has to do

Host a service that accepts bibliographic metadata and file uploads, stores metadata and files, and serves them to a web UI and a sync API.

What it still won’t have

Zotero’s Word/LibreOffice/Google Docs integrations and 9,000 citation styles
Built-in PDF reader and related UX
Groups/collaboration features integrated with Zotero accounts
Open-source community contributions and nonprofit governance

What remains hard

Product polish and ongoing maintenance

Read the build prompt

First-year cost

No published price

Zotero Storage 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

Keep paying

—

Subscription price × seats × 12

Build it

—

AI build —APIs + hosting —

Time you would spend

—

What you would spend

Your monthly price$/moAI to build it$ onceAPIs + hosting$/mo

What we assumed

Initial buildhrsMonthly upkeephrsYour rate$/hr

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet

Build a minimal Zotero-like storage service using PostgreSQL, an S3-compatible bucket, Node.js (Express) backend, and a React frontend. In scope: user signup/login, per-user metadata CRUD (title/authors/date/attachments), file upload to S3 with server-side virus-scan placeholder, a REST sync endpoint returning change lists, web UI to browse/search records and view PDFs, background worker to extract PDF metadata and thumbnails, per-user storage quota enforcement, and tests for API endpoints. Out of scope: Word/Google Docs plugins, mobile apps, citation-style library import. Include error handling, logging, and automated tests; provide a Docker Compose dev setup and deployment instructions for a single small VPS and S3 bucket.

How we checked5 sources · 2/3 runs agreed · evidence score 60

How the score was reached

Partly verdict base52
An open-source build was found+5
5 cited sources+3
Evidence score60

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 · 5

Every page the run actually retrieved.

official productZotero | Your personal research assistant
official pricingZotero Plans
official docsZotero Documentation
open sourcecloudreve/cloudreve
open sourcehaiwen/seafile

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded