Your competitors' fuel stations, watched four times a day.

Setting tomorrow's price blind.

In a station network, the price is set at night for the following day. Whoever sets it needs three things that, without a system, nobody has:

From the ministry's data to tomorrow's price sheet.

Twelve stations, in production.

We built it for Staroil, who set prices every night for twelve sites: eight in Galicia and four elsewhere. These are the figures from that deployment.

• 01All twelve sites, with roughly ninety competitor stations watched. The reference ones are chosen by the client, site by site.
• 02From one check a day to four, and with a warning inside the report when the official source fails — before, the report just came out incomplete in silence.
• 03No emails, no noisy alerts. The client asked for it: the system is there to be consulted when the price is set, not to interrupt.

Entirely on Cloudflare.

One worker, one database and four scheduled runs. There is no machine to patch, no backup to watch over, and no bill that grows with usage.

• 01Cloudflare Workers, D1 and cron. The configuration lives in the database, not in the code: adding a station or changing a time requires no deployment.
• 02Official source. Prices come from the Spanish ministry's fuel API, the same one that publishes the figures anybody can see.
• 03It replaced an n8n flow of twenty-seven nodes that emailed once a day and stored nothing.