Source: Utah Tech Calendar "Discover" page

Summary

The Utah Tech Calendar's explanation of how its index is built. This is the substantive page on the site: it names the upstream sources, describes a four-stage pipeline from scraping to publication, and — unusually for an aggregator — publishes its inclusion policy with worked examples of what it rejects.

It is the source for the site's own operating statistics and for the editorial judgment behind them.

Useful Claims

• Stated operating figures: 72 sources watched, 9 curated verticals, 4 delivery channels, 0 accounts required.
• Named upstream sources include Meetup, Luma, Silicon Slopes, Eventbrite, 47G, BioUtah, Substack, and direct submissions — so coverage extends past software into aerospace and life sciences.
• The pipeline runs in four stages: sources; refinement (removing certification spam and non-tech craft events, deduplicating, flagging webinars, sunsetting past placeholders); ontology (one schema, verticals tagged, regions placed, formats labeled); and a single schedule.
• The inclusion policy is published with examples. Rejected: "PMP 4 Days Classroom Training" (certification spam), "Woodturning: Intro to Lathe Basics" (craft, not tech), and a "Cyber Security 1-Day Workshop" cross-posted across six cities (cross-post spam). Accepted: a UtahJS meetup, a Wilson Sonsini medical-device conference, and a recurring AI Power Hour at Silicon Slopes.
• The nine verticals each have their own page: AI, fintech, healthtech, biotech, edtech, aerospace and defense, game dev, cybersecurity, and founders.
• Four ways to follow it: iCal subscription (updating as the scraper runs), a weekly email digest filtered to chosen tags, RSS, and a shareable filter URL requiring no signup on the recipient's end.
• The site states it runs no accounts, no tracking pixels or behavioral profiling, and no tracking cookies.
• It claims "+ 170 MORE THIS SEASON" beyond the sample week shown.

Verbatim

An index of the in-person Utah tech and tech-adjacent scene. Founders, designers, scientists, operators, anyone building here. One page, no signup. — "Discover Utah Tech", lede

Many shapes in, one ontology out. — "How the index gets built", Figure 1

Calendars, listing sites, organizer pages, the inbox. Scattered shapes, scattered schemas, scattered signal. — Pipeline, "01 · Sources"

One schema across thirteen sources. Verticals tagged, regions placed, formats labeled. So every event is queryable in the same vocabulary. — Pipeline, "03 · Ontology"

Scannable in one read. "What's the AI thing in Lehi on Thursday?" answers itself. — Pipeline, "04 · One schedule"

iCal subscription. Updates live as we scrape. — "Four ways to stay on it", Calendar

Reliability Notes

Self-reported tier, and written in a product-marketing register — the statistics are displayed as selling points and none of them can be checked from outside.

Two internal inconsistencies are worth recording rather than smoothing over:

• "72 sources watched" and "One schema across thirteen sources" appear on the same page. Nothing reconciles them. The likely reading is that 72 counts individual watched calendars and feeds while thirteen counts source types or platforms, but the page does not say so, and neither figure should be quoted as authoritative without that caveat.
• The "+170 more this season" figure has no defined period. "Season" is undefined, and the homepage's 149-entry August count is a different measure over a different window.

The inclusion policy is the most valuable content here and the most carefully hedged. It is a statement of intent illustrated by six chosen examples, not an audit: the examples were selected by the operator to show the rule working. What it does establish is that filtering is deliberate and opinionated — certification mills and non-technical craft classes are excluded on purpose — which is a real editorial position and materially different from an unfiltered feed.

The privacy claims ("no pixels, no behavioral profile") are the site's assertions about its own behavior and were not verified against what the page actually loads.

Related Pages

• Utah Tech Calendar
• Source: Utah Tech Calendar homepage
• Source: Utah Tech Calendar submission page