Back to browse
Pulpie – Models for Cleaning the Web

Pulpie – Models for Cleaning the Web

by snyy·Jul 6, 2026·99 points·25 comments

AI Analysis

●●●BangerBig BrainSolve My Problem

Encoder architecture cuts extraction costs 20x versus Dripper while matching quality.

Strengths
  • Encoder labels all blocks in one forward pass vs decoder's token-by-token generation
  • 13.7 pages/sec vs Dripper's 0.68 pages/sec on same NVIDIA L4 hardware
  • Open source on Hugging Face with specific ROUGE-5 benchmarks against competitors
Weaknesses
  • Web extraction is a known category with Trafilatura, Readability, and commercial tools already established
  • Adoption depends on teams migrating existing pipelines to a new model family
Category
Target Audience

ML engineers training LLMs, teams building RAG pipelines, large-scale web scrapers

Similar To

Dripper · Trafilatura · Readability

Post Description

Hey HN, I'm Shreyash, founder of Feyn. We built Pulpie, a family of Pareto optimal models for cleaning the web. Pulpie strips boilerplate (ads, footers, sidebars) from raw HTML and returns just the main content as HTML or Markdown.

We match SOTA extraction quality while being 20x cheaper. Cleaning 1 billion webpages costs $7,900 with Pulpie versus $159,000 with Dripper, the current leading extractor.

The gains come from architecture. Today's leading extractors are decoders that generate output one token at a time. Each step reads the full model from memory to produce a single token. Conversely, Pulpie models are encoders. They run one forward pass over the full input HTML and label each block as boilerplate or content. As a result, Pulpie is compute-bound while decoders are memory-bound. Cheaper GPUs have relatively more compute than memory bandwidth. This makes Pulpie easy to run optimally.

Here's Pulpie and Dripper cleaning the same pages side by side: https://www.youtube.com/watch?v=ibd-tIiQECo. You can try a side-by-side comparison yourself: https://huggingface.co/spaces/feyninc/pulpie

Our motivation for Pulpie came from building a deep research harness. Every search API returns noisy content that contains ads, nav elements, and sidebars. In one instance, an ad for "Gemini on Pixel" slipped into our search results, got passed into LLM context, and ended up in the final answer served to the user. Pretty embarrassing moment for us but it helped us realize how bad data kills model intelligence. We built Pulpie to get clean data for cheap.

All models are open source on Hugging Face. You can read about our training process and how to use Pulpie here: https://usefeyn.com/blog/pulpie-pareto-optimal-models-for-cl...

Happy to answer any questions!

Similar Projects