Writing and content decision
Genei
A capable developer can recreate the core summarisation, storage and QA features in about a week plus ongoing light maintenance; Genei's main durable advantage is brand recognition rather than proprietary technical barriers.
Visit website↗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. All Genei alternatives, with the arithmetic →
What a replacement has to do
- Ingest PDFs/webpages, extract text, call an LLM to produce summaries/keywords, store documents & summaries, provide search and question-answering over documents.
What it still won’t have
- Priority server access / SLA
- Polished UX and walkthroughs
- Any proprietary models or vendor optimizations
- Integrated chrome extension and cross-device polish
What remains hard
- Brand trust
Genei is part of Y-Combinator, a US startup accelerator with over 2000 companies including Stripe, Airbnb, Reddit and Twitch.
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 14 seats.
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 a minimal self-hosted Genei-like app using FastAPI (Python), Postgres, React, and FAISS. In scope: user file upload (PDF/URL), robust text extraction (pdfminer + Tesseract OCR fallback, HTML scraper), persist raw text and metadata to Postgres, generate embeddings and summarisation via OpenAI/other LLM API, implement vector search and a QA endpoint that composes context + LLM prompt, and a simple React UI to upload files, view stored docs and summaries, and ask questions. Out of scope: multi-tenant billing, analytics dashboard, browser extension, and enterprise SLAs. Include error handling, retries for API calls, basic unit tests for extraction and API endpoints, and a README with deployment steps (Docker Compose).
How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 3 cited sources+3
- Price verified on pricing page+3
- Evidence score89
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.
- official productgenei | AI-powered summarisation & research tool
- official pricinggenei - Pricing
- open sourcemiso-belica/sumy
Integrity checks
What held up, and what did not.
