reader is a free, open source data extraction & web scraping project written in TypeScript and released under Apache-2.0. It has 560 GitHub stars, 40 forks and 0 open issues, and was last pushed 29 days ago. On this registry it ranks #45 of 45 tracked projects in Data Extraction & Web Scraping, with 5 head-to-head comparisons available.

What is reader?

Reader is an Apache-2.0 TypeScript library and hosted service that scrapes, crawls, and drives stealth headless browsers to deliver clean Markdown to AI agents, built for developers who need production-grade web access without assembling Puppeteer, stealth plugins, and proxy infrastructure by hand.

What it is

Reader is a production-grade web scraping engine built on top of Playwright, with stealth and anti-detection baked in from the ground up. It ships as a TypeScript package published to npm under the @vakra-dev scope, and it exposes exactly three primitives: scrape() for turning URLs into clean Markdown, crawl() for breadth-first link discovery and page scraping, and browser() for a full stealthed Chrome session that Playwright or Puppeteer can drive over CDP. The project is licensed under Apache-2.0 and lives at reader.dev, with a cloud console at console.reader.dev.

The concrete problem it solves is the layer underneath rendering. Production scraping is not a matter of loading a page and converting HTML to Markdown; as the README puts it, the hard parts are browser architecture at scale, anti-bot bypass against Cloudflare, Turnstile and JavaScript challenges, TLS fingerprinting, proxy rotation with sticky sessions, browser pooling and memory limits, and the reliability work of rate limiting, retries, timeouts, and caching. Reader replaces the hand-rolled stack of Puppeteer plus stealth plugins plus ad hoc proxy handling that tends to break in production, and it does so in the Node.js ecosystem where most agent tooling already lives.

Key capabilities

  • Browser sessions that launch stealthed Chrome and expose a CDP endpoint via session.wsEndpoint, so chromium.connectOverCDP(session.wsEndpoint) works with Playwright or Puppeteer.
  • Anti-bot bypass covering TLS fingerprinting, navigator spoofing, WebRTC masking, and webdriver=false.
  • Clean output as Markdown or HTML with automatic main-content extraction, plus smart content cleaning that strips navigation, headers, footers, popups, and cookie banners.
  • BFS website crawling with depth and page limits, exposed through reader.crawl({ url, depth, scrape: true }).
  • Browser pool with auto-recycling, health monitoring, and tiered proxy pools held separately as standard and premium tiers with health tracking.
  • Concurrent scraping of URL lists with progress tracking, driven by reader.scrape({ urls: [...] }).
  • Both a CLI and a programmatic API, so the same engine can be used from a terminal or embedded in an agent.

Who uses it and how

  • Agent developers who need web access as a tool call and want Markdown rather than raw HTML to feed into a model context.
  • Teams running self-hosted scraping on their own infrastructure, where the engine installs as @vakra-dev/reader and runs against local browser instances.
  • Applications that need full browser control, such as authenticated flows or complex interaction, using the browser() primitive as a stealthed Chrome that existing Playwright code can attach to.
  • Cloud users who prefer not to operate browsers or proxies at all, calling reader.read({ url }) against the hosted API with a READER_API_KEY.
  • Operators of larger scraping workloads who rely on the browser pool and tiered proxy pools to keep memory bounded and sessions healthy.

Getting started

Self-hosting starts with npm install @vakra-dev/reader on Node.js 18 or later, followed by npx playwright install chromium for the first run. The cloud path instead uses npm install @vakra-dev/reader-js with an API key obtained from console.reader.dev.

How it compares

The project tags itself firecrawl-alternative, placing it directly against Firecrawl as a drop-in option for teams already evaluating hosted scraping APIs. The distinguishing axis stated in the facts is deployment: Reader is Apache-2.0 and can be run entirely on the user's own infrastructure through the @vakra-dev/reader engine, while the hosted offering under @vakra-dev/reader-js is a separate, optional path for those who would rather buy the operation than run it.

When to use it — and when not to

A self-hoster takes on real operational weight: Node.js 18 or later, a Playwright-managed Chromium build, and proxy pools that are tiered into standard and premium, with the anti-bot and fingerprinting work happening inside the engine rather than in user code. Teams unwilling to run browsers or manage proxies should use the cloud client instead of the self-hosted engine. The README excerpt is also truncated mid-example, so anyone evaluating the project should expect to lean on the separate documentation site for the full API before committing.

project readme (upstream, from github) — read inline

Reader

Open source web infrastructure for AI.

Access the web without the complexity.

License: Apache 2.0 npm version GitHub stars

Docs · Examples · Discord

The Problem

Building agents that need web access is frustrating. You piece together Puppeteer, add stealth plugins, fight Cloudflare, manage proxies and it still breaks in production.

Because production grade web scraping isn't about rendering a page and converting HTML to markdown. It's about everything underneath:

Layer What it actually takes
Browser architecture Managing browser instances at scale, not one-off scripts
Anti-bot bypass Cloudflare, Turnstile, JS challenges, they all block naive scrapers
TLS fingerprinting Real browsers have fingerprints. Puppeteer doesn't. Sites know.
Proxy infrastructure Standard vs premium, rotation strategies, sticky sessions
Resource management Browser pooling, memory limits, graceful recycling
Reliability Rate limiting, retries, timeouts, caching, graceful degradation

I built Reader, a production-grade web scraping engine on top of Playwright, with stealth and anti-detection built in from the ground up.

The Solution

Three primitives. That's it.

import { ReaderClient } from "@vakra-dev/reader";
import { chromium } from "playwright-core";

const reader = new ReaderClient();

// 1. Scrape URLs → clean markdown
const result = await reader.scrape({ urls: ["https://example.com"] });
console.log(result.data[0].markdown);

// 2. Crawl a site → discover + scrape pages
const pages = await reader.crawl({
  url: "https://example.com",
  depth: 2,
  scrape: true,
});
console.log(`Found ${pages.urls.length} pages`);

// 3. Browser session → full Playwright/Puppeteer control with stealth
const session = await reader.browser();
const browser = await chromium.connectOverCDP(session.wsEndpoint);
const page = browser.contexts()[0].pages()[0];
await page.goto("https://example.com");
console.log(await page.title());
await session.close();

All the hard stuff (browser pooling, anti-bot bypass, proxy rotation, retries) happens under the hood. You get clean markdown. Your agents get the web. And when you need full browser control, browser() gives you a stealthed Chrome that Playwright or Puppeteer can drive.

[!TIP] If Reader is useful to you, a star on GitHub helps others discover the project.

Features

  • Browser Sessions - Launch stealthed Chrome, connect Playwright/Puppeteer via CDP
  • Anti-Bot Bypass - TLS fingerprinting, navigator spoofing, WebRTC masking, webdriver=false
  • Clean Output - Markdown and HTML with automatic main content extraction
  • Smart Content Cleaning - Removes nav, headers, footers, popups, cookie banners
  • CLI & API - Use from command line or programmatically
  • Browser Pool - Auto-recycling, health monitoring, tiered proxy pools
  • Concurrent Scraping - Parallel URL processing with progress tracking
  • Website Crawling - BFS link discovery with depth/page limits
  • Tiered Proxies - Standard and premium proxy pools with health tracking

Installation

npm install @vakra-dev/reader

Requirements: Node.js >= 18

First run: Playwright bundles Chromium for all platforms. Install it with:

npx playwright install chromium

Quick Start

Cloud (Fastest)

Get an API key at console.reader.dev and start scraping immediately:

import { ReaderClient } from "@vakra-dev/reader-js";

const reader = new ReaderClient({ apiKey: process.env.READER_API_KEY });

const result = await reader.read({ url: "https://example.com" });
if (result.kind === "scrape") {
  console.log(result.data.markdown);
}
npm install @vakra-dev/reader-js

See the cloud docs for the full API reference.

Self-Hosted

Install the reader engine and run scraping on your own infrastructure:

Basic Scrape

import { ReaderClient } from "@vakra-dev/reader";

const reader = new ReaderClient();

const result = await reader.scrape({
  urls: ["https://example.com"],
  formats: ["markdown", "html"],
});

console.log(result.data[0].markdown);
console.log(result.data[0].html);

await reader.close();

Batch Scraping with Concurrency

import { ReaderClient } from "@vakra-dev/reader";

const reader = new ReaderClient();

const result = await reader.scrape({
  urls: ["https://example.com", "https://example.org", "https://example.net"],
  formats: ["markdown"],
  batchConcurrency: 3,
  onProgress: (progress) => {
    console.log(`${progress.completed}/${progress.total}: ${progress.currentUrl}`);
  },
});

console.log(`Scraped ${result.batchMetadata.successfulUrls} URLs`);

await reader.close();

Crawling

import { ReaderClient } from "@vakra-dev/reader";

const reader = new ReaderClient();

const result = await reader.crawl({
  url: "https://example.com",
  depth: 2,
  maxPages: 20,
  scrape: true,
});

console.log(`Discovered ${result.urls.length} URLs`);
console.log(`Scraped ${result.scraped?.batchMetadata.successfulUrls} pages`);

await reader.close();

Browser Session

Launch a stealthed Chrome and control it with Playwright or Puppeteer. The browser has anti-bot stealth active (webdriver=false, navigator spoofing, WebRTC masking). Your existing scripts just work.

import { ReaderClient } from "@vakra-dev/reader";
import { chromium } from "playwright-core";

const reader = new ReaderClient();

// Create a browser session - returns a CDP WebSocket URL
const session = await reader.browser();

// Connect Playwright (one-line change from a local script)
const browser = await chromium.connectOverCDP(session.wsEndpoint);
const context = await browser.newContext();
const page = await context.newPage();

// Use Playwright normally - full stealth active
await page.goto("https://news.ycombinator.com/");
console.log(await page.title());

await browser.close();
await session.close();
await reader.close();

Also works with Puppeteer:

import { connect } from "puppeteer-core";

const browser = await connect({ browserWSEndpoint: session.wsEndpoint });

With Proxy

import { ReaderClient } from "@vakra-dev/reader";

const reader = new ReaderClient();

const result = await reader.scrape({
  urls: ["https://example.com"],
  formats: ["markdown"],
  proxy: {
    type: "premium",
    host: "proxy.example.com",
    port: 8080,
    username: "username",
    password: "password",
    country: "us",
  },
});

await reader.close();

With Tiered Proxy Pools

Configure standard (datacenter, fast) and premium (residential, anti-bot) proxy tiers:

import { ReaderClient } from "@vakra-dev/reader";

const reader = new ReaderClient({
  proxyPools: {
    standard: [
      { url: "http://user:pass@dc-proxy1:8080" },
      { url: "http://user:pass@dc-proxy2:8080" },
    ],
    premium: [{ url: "http://user:pass@res-proxy1:8080" }],
  },
});

const result = await reader.scrape({
  urls: ["https://example.com"],
  proxyMode: "standard", // or "premium" for anti-bot sites
});

await reader.close();

Or via environment variables:

PROXY_STANDARD=http://user:pass@dc1:8080,http://user:pass@dc2:8080
PROXY_PREMIUM=http://user:pass@res1:8080

With Browser Pool Configuration

import { ReaderClient } from "@vakra-dev/reader";

const reader = new ReaderClient({
  browserPool: {
    size: 5, // 5 browser instances
    retireAfterPages: 50, // Recycle after 50 pages
    retireAfterMinutes: 15, // Recycle after 15 minutes
  },
  verbose: true,
});

const result = await reader.scrape({
  urls: manyUrls,
  batchConcurrency: 5,
});

awai

readme truncated — read the full docs on github

Frequently asked questions

Is reader free to use?

reader is open source under the Apache-2.0 licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does reader do?

Open source web infrastructure for AI. Scrape, crawl, and automate the web, clean markdown, browser sessions, ready for your agents.

What is reader written in?

reader is primarily written in TypeScript. Its source is publicly available at https://github.com/vakra-dev/reader, and it has 560 GitHub stars.