DENKOPS

Scraper hosting

Host scrapers that run on schedule and remember.

A scraper needs three things a laptop or a short-lived function struggles with: a schedule that fires on time, somewhere to remember what it already saw, and enough time to finish. DenkOps gives every scraper an always-on slot with all three.

Try it free → Read the docs

Free: 1 project, no credit card. 5 project slots €39/month, €5 per extra slot.

Built for scraping jobs

  • Schedules. Declare a cron array in denkops.json and DenkOps triggers your endpoint on time, with run history in the dashboard and over MCP. In Bun you can also use the in-process denkops.cron helper.
  • Memory between runs. Save seen URLs, last prices or snapshots on the durable /persist disk. It survives restarts and redeploys.
  • No time limit. A crawl that takes forty minutes simply runs for forty minutes.
  • Outbound traffic you control. Egress is blocked by default; allow only the domains your scraper should reach. A bug or a prompt-injected agent cannot send data anywhere else, see zero-trust egress for agents.
  • A scraper your agent can drive. Expose the scraper as an MCP tool and ask an assistant to run it or read the results, see a scraper your agent can drive.

Respect the sites you scrape

Check the site's terms and robots rules, identify your client, and keep request rates low. A schedule and a small state file make it easy to fetch only what changed.

Pick your stack

The guides below are complete scrapers in Bun, FastAPI, Flask and Express.

Deploy guides

Bun + Hono

Deploy a Bun + Hono web scraper on DenkOps

Run a Bun fetch-based scraper behind Hono on DenkOps and write crawl results to a durable /persist disk.
FastAPI

Deploy a FastAPI web scraper on DenkOps

Trigger an async FastAPI scraper on DenkOps and persist results to a durable disk between runs.
Flask

Deploy a Flask web scraper on DenkOps

Run a Flask-triggered requests+BeautifulSoup scraper on DenkOps and write results to a durable /persist disk.
Express

Deploy an Express Puppeteer scraper on DenkOps

Run a headless-Chrome Puppeteer scraper behind Express on DenkOps, with results written to a durable disk.

FAQ

Can I run a scraper on a schedule?

Yes. Managed cron in denkops.json triggers your scraper on a cron expression, and every run is visible in the dashboard and through the MCP tools.

Where do scraped results go?

On the durable /persist disk or in the key-value store, which survive restarts and redeploys. You can also send them to your own database.

Is there a limit on how long a scrape can run?

No. A slot is a long-running process, so a job runs until it finishes.

Try it free →

Free: 1 project, no credit card. 5 project slots €39/month, €5 per extra slot.

View service status →Managed EU infrastructure