Should you build your own Lex?
Write and revise long-form documents with comments, version history, and AI actions
The core loop is small enough for a capable coding agent to produce a useful local version in one sitting. For Lex, write and revise long-form documents with comments, version history, and AI actions. The hard boundary is collaborative editor polish, sync, and embedded model access, plus workflow, data, and model tuning.
ENOriginal research content in English. Original prompt preserved in English.
Build a personal replacement for Lex in an empty repository.
Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and the OpenAI Responses API; do not offer alternative stacks.
The core loop is: take a brief, gather user-supplied source material, generate and revise a structured long-form draft with comments and AI actions, and keep citations and version history attached to each section.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Build a brief form with audience, objective, tone, source URLs, and prohibited claims.
Store imported source text locally and chunk it for retrieval with SQLite FTS5.
Generate an outline first and require approval before drafting sections.
Attach source references to generated paragraphs and flag unsupported claims.
Provide rewrite controls for shorten, clarify, change tone, and add evidence.
Export clean Markdown plus a JSON research bundle.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out live search-engine rank data.
Deliberately leave out automatic publishing to third-party CMSs.
Deliberately leave out multi-user approvals and brand governance.
Finish by running the tests and listing the exact commands used.The prompt opens pre-filled in your agent. Review it before running. · this prompt is generated from the build plan · improve it via PR
What would building your own look like?
Take a brief, gather user-supplied source material, generate and revise a structured long-form draft with comments and AI actions, and keep citations and version history attached to each section.
What you will need
- OpenAI API key
- Node.js 22
- local or self-hosted deployment
- user-supplied sources
People still pay for Lex because the subscription bundles a refined workflow, proprietary signals, templates, and predictable output quality for a team. The recurring cost buys prompt maintenance, retrieval quality, source handling, provider changes, and editorial QA, not just the visible interface.
xcollaborative editor polish, sync, and embedded model access
xproprietary ranking data
xbrand-trained models
xteam workflows
xlarge template libraries
Prefer something ready-made?
AppFlowyA local-first collaborative document workspace with comments, history, and free Ollama-backed AI; Notion-shaped, but it can replace Lex.Open source↗License, setup, and limitations for each alternative.
How much does Lex cost?
- Monthly billing
- $12/mo$12/mo
- Per year
- $144/yr$144/yr
- On a Brazilian card, with 3.5% IOF
- R$62.71/moR$753/yr
Saved to My list. You will see a notice on this site when the price changes.
You complete the purchase on Lex’s site. Vibe Radar does not handle payments.
Is it cheaper to build or buy Lex?
Adjust the numbers: hours to build, your hourly rate, running costs and the subscription price.
Over 24 months, subscribing is cheaper.
Starting hours estimated from the analysis (multi-day). Does not price what you give up (support, integrations, security).
Can I rebuild Lex?
Yes. A competent AI coding agent (Claude Code, Codex, Cursor) can build a usable personal Lex replacement in one session with the prompt on this page. It runs on your own machine or server with no subscription.
How much does Lex cost?
Lex costs about $12/mo (Pro, checked 07/31/2026), which is $144 per year. That’s what you save by replacing it with one prompt.
What do I lose by replacing Lex?
Honestly: collaborative editor polish, sync, and embedded model access; proprietary ranking data; brand-trained models; team workflows; large template libraries. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Lex?
Yes: AppFlowy (A local-first collaborative document workspace with comments, history, and free Ollama-backed AI; Notion-shaped, but it can replace Lex.) The prompt is for when you want it exactly your way.