Everyone has tried to build this. Nobody has kept one running.
- Every city has a dozen event calendars, and not one of them is complete.
- Building one means scraping fifty sites. Keeping one means scraping those fifty sites forever, as they break, redesign, and move.
- We do the second part. That's the whole product.
How it works
-
Tell us about your city
Where it is, and what people there actually want to know about.
-
The agent goes and finds it
It discovers the venues and orgs publishing events, then implements each source.
-
Your calendar goes live
At yourcity.finds.events, refreshed on whatever schedule you choose.
What you get
-
Source discovery, not a source form
You don't hand us a list of URLs. The agent goes looking for the venues, promoters and orgs in your city, then evaluates each one and writes the integration itself.
-
Self-healing sources
Venue sites get redesigned constantly. When one breaks, a fix run repairs the integration — the part that usually kills a community calendar is the part we automated first.
-
Nothing ships empty
A source that returns no events cannot go live. That gate is inside the pipeline, not a note in a prompt, so a silently-broken scraper never quietly empties your calendar.
-
Calendar subscriptions
Every tag is an .ics feed. Your readers subscribe once to the music, or the kids' events, or the free stuff, and it shows up in their calendar forever.
All 11 features, 7 more
-
Events, enriched
Cost, venue and location, photos, indoors or out — filled in automatically, with the same show listed three different ways collapsed into one.
-
A real site, fast
Static, tagged, searchable, and yours at yourcity.finds.events — a page that loads instantly on a phone on a bus, not a spinner over an API.
-
Immutable builds, one-click rollback
Every publish is a versioned snapshot. A bad one is undone by pointing back at the last good build — no re-running, no waiting on us.
-
A dashboard that shows the bill
Every run states what it cost, in credits, against your balance. No invisible meter, no surprise at the end of the month.
-
Talk to your city's agent
Ask it to add a source, ask why an event looks wrong, ask what changed this week.
-
Told when something breaks
A source that stops returning events raises a notification — you hear it from us before a reader emails you.
-
Your own domain
Serve the calendar on a domain you own instead of the subdomain we give you.
See it running
Cleveland runs on this platform today. Both halves of it are open.
Example week, for illustration. The live calendar is one click away.
The calendar
What residents see
Every event in Cleveland, tagged and searchable, with an .ics feed for
every tag. Refreshed on the city's own schedule.
Example runs, for illustration. The demo shows Cleveland's real ones.
The dashboard
What you would run it from
The sources, the runs, the candidates the agent found, the chat transcripts, the bill. Read-only, no login — it is the real thing.
Seattle's 206.events runs on this platform, on the engine it has used for years.
Pricing
You're not buying a seat, you're buying work. Credits pay for the agent's runs, and the plans differ only in how many you get each month — every feature is on every plan.
Free
A neighborhood, or a city you're trying out.
$0
XX credits a month
- Every feature
- One free refresh a week
- One free city per account
Standard
A city calendar people actually rely on.
$XX / month
XX credits a month
- Every feature
- One free refresh a week
- Refresh as often as you like
- Top up any time
Pro
A big metro, or a lot of sources.
$XX / month
XX credits a month
- Every feature
- One free refresh a week
- Refresh as often as you like
- Top up any time
Prices are still being finalized — ask us and we'll talk through what your city would actually use.
Every city is onboarded by hand right now. There's no signup form: tell us about your city and we'll set it up with you. Free tier included.
How credits work
You can't fall off the map
Every city gets one free refresh every week, outside the credit system entirely. Your calendar is never more than a week stale — at a zero balance, on the free plan, no matter what. And your site stays served, always.
One currency
Credits pay for work: refreshing your sources, fixing a broken one, a discovery run, adding a source. Bigger cities use more per run, so you pay for the size of the job.
You decide the spend
How often to refresh, whether to hunt for new sources, whether broken sources get fixed automatically. Your settings, your budget.
No debt, ever
Run out mid-month and work pauses rather than piles up. Top up, or wait for next month's credits — nothing queues up a bill behind your back.
Questions
How do I sign up?
You email us. Every city is onboarded by hand right now — we'd rather set yours up with you than drop you into an empty dashboard. The Free tier is included in that.
Can I see the dashboard before I email you?
Yes. Try the dashboard on a real city before you email us — the “Browse the demo dashboard” button opens Cleveland's dashboard in read-only demo mode. There is no login, and nothing you do there can start a run.
Do I need to be technical?
No. If you can describe what your city cares about, that's the input. The agent handles the scraping, the fixing, and the publishing.
Where do the events come from?
Venues, promoters, libraries, parks departments, community orgs — the places already publishing their own events. We read their sites and feeds; we don't invent listings.
What happens if I run out of credits?
Your site stays up, and your weekly refresh keeps running — it sits outside the credit system entirely. Broken sources wait for attention instead of being fixed automatically until you top up or the next month's credits land.
Who owns the calendar?
You do. It's your city's data and your subdomain, and you can take an export of it whenever you want.
Start your city
Tell us where you are and what you'd want on it. We'll take it from there.
Or write to hello@finds.events
A person reads every request.