Roughly 900 dispensaries across two states, each one running on one of nine menu platforms. Every platform has its own shape, its own quirks, and its own dedicated scraper.
Adult-use and medical menus, full coverage.
Every active Ohio dispensary tracked on a rolling 25-minute pipeline. Scrapes route through a secondary WAN to keep upstream load even.
Adult-use menus, the larger half of the footprint.
Same pipeline, same reports, same matching rules across state lines. Side-by-side comparisons fall out of the data naturally.
No generic HTML scraper, no shared parser. Each platform has API-shaped or storefront-shaped quirks that only get clean data with a dedicated implementation. We pay that tax once, you get the upside every cycle.
API + storefront + detail scrape
Algolia + API + storefront
API + storefront
API + storefront
API + storefront
API + storefront
API + storefront
API
Six containers run the operation: a scraper pipeline, three reports services, an API, an email gateway, plus Postgres and Redis. A controller container watches everything and exposes an operator CLI.
You never see any of that. You see the email.
