Plan 01Start here
Free
For evaluation, side projects, and kicking the tires.
$0/ forever
Get Started Free- 1,000 scrapes / month
- REST API + built-in MCP Server
- JavaScript rendering
- Structured extraction (BYO LLM key)
- Community support (GitHub Issues)
Pricing / Managed or yours
Simple enough to read in one pass.
01 / Plans
Choose the amount of operation you want.
Start with the hosted service, or run the open-source core yourself. Upgrade only when your workload needs the managed allowance and support.
Plan 02Managed
Pro
Predictable monthly bill for steady recurring workloads.
$29/ per month
- 50,000 scrapes / month
- 10 concurrent requests
- REST API + built-in MCP Server
- Structured extraction (BYO LLM key)
- Priority email support
- Early access to new features
02 / Compare
Two plans. One product.
The comparison below reflects the plans available today. Roadmap ideas stay off the price sheet until they ship.
Capability
Free
Pro
Monthly scrapes
1,000
50,000
Concurrent requests
2
10
REST API
Yes
Yes
MCP Server
Yes
Yes
JavaScript rendering
Yes
Yes
Structured extraction (BYO LLM)
Yes
Yes
Priority support
—
Yes
Self-host (Apache 2.0)
Yes
Yes
Prefer your own infrastructure?
Purify's Apache 2.0 core can run on your environment. You control deployment, capacity, and the data path.
View source03 / Notes
The useful fine print.
01What counts as one request?
Each URL submitted to a Purify endpoint counts against the plan allowance. Structured extraction also uses the LLM provider key you supply.
02Can I self-host Purify?
Yes. The core is available under Apache 2.0, so you can run it on infrastructure you control and operate it within your own data boundary.
03Does Pro use a different extraction engine?
No. Free, Pro, and self-hosted deployments use the same Purify product surface. Pro adds a larger hosted allowance and priority support.
04How do I cancel Pro?
Cancel from the dashboard. Your paid access continues through the current billing period; Paddle remains the merchant of record.
05Do JavaScript-heavy pages work?
Purify uses an HTTP-first path and can fall back to browser rendering when a page needs it. Results still depend on the target site and its access rules.
A workload that does not fit?
Tell us the source mix, volume, and deployment constraints. We will say plainly whether Purify is a fit.
Contact us