Introducing the new Piloterr website

We have shipped a full rebuild of piloterr.com. If you have been using Piloterr for a while, your API keys, dashboard, and existing integrations keep working exactly as before. What changed is everything around the product: how we explain what we build, how you browse endpoints, and how we document the platform.

This post walks through what is different compared to the previous site, and where we are headed on infrastructure: including active work toward a second owned datacenter.

Why we rebuilt the site

The old website did a solid job as a marketing landing page, but it was harder to navigate as the product grew. Endpoints multiplied, bypass modules became first-class products, and teams asked for clearer paths from “I need LinkedIn data” to the right API call.

The new site is built to match how developers actually use Piloterr today:

• Find an endpoint fast: search the API library, open docs, try the playground.
• Understand the stack: dedicated pages for Scraper APIs, headless browser, AI Web Unblocker, and anti-bot bypass.
• Connect to your workflow: integrations for LangChain, n8n, Zapier, Make, MCP, and more.
• Learn without leaving the site: blog, glossary, and free toolbox.

Under the hood, the site runs on a modern Next.js stack with full EN/FR localization, structured SEO, and faster static delivery.

What changed vs. the previous piloterr.com

Here is a practical comparison if you bookmarked the old site.

API library and documentation

Before: The library was presented as a directory of endpoints with basic listing.

Now: 500 scraping APIs each have their own documentation page with parameters, response schemas, credit cost, and links to related endpoints. Collections group APIs by use case (e-commerce, SERP, social media, and more), so you can browse by job instead of memorizing slugs.

The Website Crawler, Website Rendering, and Website WebUnlocker products are documented side by side. If you are unsure which mode to pick, read our Crawler vs Rendering vs WebUnlocker guide.

Product pages

Before: Products were grouped under a single “Products” narrative with proxy pools and HTML crawlers highlighted on the homepage.

Now: Each major capability has its own page with pricing context, FAQs, and links to the relevant library endpoints:

Developer resources

Before: Free tools, dictionary, and templates lived in a “Resources” dropdown.

Now: They are first-class sections with better search and categorization:

• Web scraping glossary: 320+ terms with cross-links to tools and blog posts.
• Workflow templates: ready-made n8n, Make, and Zapier flows powered by Piloterr APIs.
• Integrations: setup guides for LangChain, LangGraph, LlamaIndex, CrewAI, Pydantic AI, Google Apps Script, Dify, and MCP.

We also publish llms.txt and agents.json so AI agents and coding assistants can discover our docs programmatically.

Datasets, scrapers, and comparisons

• Datasets: ready-to-use data for e-commerce, jobs, companies, and market research, with clearer product pages per dataset.
• Scraper landing pages: dedicated pages for popular targets (Amazon, Google, LinkedIn, Walmart…) linking straight to the matching API.
• Compare: side-by-side views vs ScraperAPI, ScrapingBee, Bright Data, Apify, Zyte, and others.

Pricing and onboarding

Before: Signup advertised 50 free credits.

Now: New accounts receive +500 credits on signup with no credit card required. Pricing pages break down Scraper APIs, headless browser, and Web Unblocker separately. Use the usage estimator to model monthly volume before picking a plan.

Localization

Before: English only on the marketing site.

Now: Full French site at /fr/: product pages, library docs, glossary, toolbox, and blog. Hreflang alternates connect EN and FR versions for SEO.

Trust, legal, and accessibility

• Updated privacy, terms, accessibility statement, and subprocessors pages.
• High-contrast mode and theme toggle built into the header.
• Enterprise and startup program pages for teams scaling beyond self-serve.

What did not change

Your dashboard, API keys, billing, and existing API calls are unchanged. Endpoint URLs and authentication (x-api-key) work the same way. If you integrated via Zapier or n8n before, those flows still apply: we simply documented them better.

Infrastructure: working toward a second datacenter

Piloterr has always run scraping traffic on infrastructure we control: private datacenter pools, our own Chromium stack, and managed proxy rotation rather than resold opaque proxy lists.

Today our platform runs on owned datacenter capacity that powers routing on every API call. We are now in active discussions and planning for a second datacenter: not as a marketing label, but as a concrete capacity and resilience project:

• Geographic redundancy for the toolbox: free developer utilities served from EU and US regions for lower latency.
• Failover headroom: if one site has maintenance or a carrier issue, traffic can shift without you reconfiguring anything.
• Enterprise isolation: dedicated rotation deployments for large accounts that need physically separated routing paths.
• Capacity for growth: our homepage tracks 10B+ requests per month; a second site gives us room to scale bare-metal proxy farms without hitting single-facility limits.

You can read more about our current infrastructure on the owned datacenter and private datacenter pools pages. We will share milestones on this blog as the second site moves from planning to production.

Explore the new site

We built this site for the teams who live in our docs daily. If something is missing or confusing, tell us: the whole point of the rebuild is to make Piloterr easier to adopt, integrate, and scale.

Ready to try it? Create a free account: +500 credits, no credit card required.