DEV.co
Open-Source DevOps · wasi-master

13ft

13ft is a self-hosted Python web server that bypasses paywalls and ad-blocking on news sites by impersonating Google's web crawler to retrieve full article content. It works with sites like Medium and The New York Times where standard paywall-bypass tools fail.

Source: GitHub — github.com/wasi-master/13ft
4.2k
GitHub stars
225
Forks
Python
Primary language
MIT
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositorywasi-master/13ft
Ownerwasi-master
Primary languagePython
LicenseMIT — OSI-approved
Stars4.2k
Forks225
Open issues5
Latest releasev0.4.0 (2026-05-11)
Last updated2026-05-14
Sourcehttps://github.com/wasi-master/13ft

What 13ft is

Flask-based Python application that proxies HTTP requests through a GoogleBot user-agent spoof and applies multiple fallback bypass methods to circumvent paywall detection. Deployable via Docker, systemd, or direct Python execution with optional reverse-proxy integration.

Quickstart

Get the 13ft source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/wasi-master/13ft.gitcd 13ft# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Personal Research & One-Off Articles

Ideal for individual users who need to read paywalled articles occasionally without maintaining subscriptions. Self-hosted setup keeps usage private and eliminates third-party service dependencies.

Institutional or Team Access

Organizations can deploy a single 13ft instance internally to provide consistent, cached access to paywalled research content across multiple users without licensing each subscription separately.

Archive & Preservation

Useful for research institutions or archivists who need to preserve full-text copies of online articles for historical or academic purposes where rights exist.

Implementation considerations

  • Verify applicable copyright law and publisher terms of service before deployment; paywall bypass legality varies by jurisdiction and use case.
  • Plan fallback strategy if target sites update detection logic; the project does not publish compatibility matrix or maintenance schedule for known paywalls.
  • Configure reverse proxy and TLS termination (examples provided for Apache); direct Flask exposure on internet is not recommended.
  • Monitor HTTP headers and response payloads for site-specific changes; no automated alert system documented.
  • Isolate instance network access; GoogleBot spoofing on public internet may attract blocking or abuse reports from publishers.

When to avoid it — and what to weigh

  • Legal Compliance Priority — Paywall circumvention may violate terms of service or copyright law in some jurisdictions. Organizations requiring strict IP/ToS compliance should not deploy this without legal review.
  • Mission-Critical Reliability Required — Only 4,226 stars and 225 forks suggest limited enterprise adoption. Relying on this for production-critical workflows exposes you to unmaintained fallback methods and potential upstream site changes breaking functionality.
  • High-Volume or Commercial Use — No built-in rate limiting, caching invalidation strategy, or audit logging documented. Using at scale risks overwhelming target sites and creating legal liability.
  • Sites with Advanced Bot Detection — While it spoof GoogleBot, modern sites employ sophisticated fingerprinting. Success rate is not benchmarked; the 'multiple fallback methods' offer no SLA or success guarantee.

License & commercial use

MIT License. Permits use, modification, and distribution for commercial or private purposes with no warranty. Licensee is responsible for legal compliance with paywall-circumvention applicable law.

MIT is a permissive OSI license allowing commercial use. However, commercial deployment of paywall-bypass tools carries legal risk. Terms of service violation is likely on most publisher sites. Requires explicit legal review before any commercial offering or SaaS monetization.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationAdequate
License clarityClear
Deployment complexityLow
DEV.co fitPossible
Assessment confidenceMedium
Security considerations

Impersonates GoogleBot via user-agent header; risks IP blocking or legal escalation if detected. No built-in authentication, rate limiting, or request logging for audit trails. Flask default development settings may be used if not explicitly overridden. Running on internet-facing port without TLS is unsafe; reverse proxy with HTTPS required. No input validation or sanitization details provided for URL parameters; XSS or injection vectors unknown without code review.

Alternatives to consider

12ft.io (SaaS)

Hosted service, no maintenance or deployment overhead, but centralized third-party dependency, no privacy guarantee, and subject to publisher legal action.

Unpaywall / Open Access Search

Legal, publisher-approved tool for finding freely available peer-reviewed articles; works only for academic content, not news paywalls.

Browser Extensions (e.g., Bypass Paywalls Clean)

Client-side, no server infrastructure, but less reliable against modern detection, limited to specific paywalls, potential malware risk if sourced from unofficial repos.

Software development agency

Build on 13ft with DEV.co software developers

13ft offers a straightforward self-hosted alternative to centralized paywall-bypass services, but carries legal and operational risks. Before deployment, confirm legal compliance, test site compatibility, and secure infrastructure with TLS and access controls. Contact our team for custom integration or compliance guidance.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

13ft FAQ

Does 13ft work on all paywalled sites?
No. It is designed for sites that respect GoogleBot crawlers (Medium, NYT historically). Sites with advanced bot detection or JavaScript paywalls may not be bypassed. Success is not guaranteed and changes with each site update.
Is self-hosting 13ft legal?
Uncertain. Copyright and computer fraud law vary by jurisdiction. Self-hosted, private use for personal research may be defensible, but public or commercial deployment is higher legal risk. Consult local counsel before production use.
What happens if a publisher detects my 13ft instance?
IP blocking, legal notice, or cease-and-desist are possible. No incident-response or escalation procedures are documented. Users assume all legal and operational liability.
Can I run 13ft on shared hosting or a VPS?
Yes, Docker and Python venv deployments work on standard Linux VPS. Reverse proxy examples provide TLS and load-balancing guidance. Note: using a residential or datacenter IP risks publisher blocklists.

Software development & web development with DEV.co

Need help beyond evaluating 13ft? DEV.co is a software development agency offering software development services and web development for teams of every size. Our software developers and web developers build custom software, web applications, APIs, and open-source devops integrations — and maintain them long-term.

Evaluate 13ft for Your Use Case

13ft offers a straightforward self-hosted alternative to centralized paywall-bypass services, but carries legal and operational risks. Before deployment, confirm legal compliance, test site compatibility, and secure infrastructure with TLS and access controls. Contact our team for custom integration or compliance guidance.