ComputeFinder

About ComputeFinder

Make compute understandable, accessible and accountable. Find a route to compute, understand what is proposed or built in a place, and follow the evidence behind a claim.

Who is responsible

ComputeFinder is a project run by Marc Winn, who is responsible for its editorial policy. Authorised AI agents help prepare and maintain records under the publication rules. A record's sources, dates and review notes describe the checks actually recorded.

Routine factual changes require source evidence and independent review. Conflicting evidence, consequential contested claims, unresolved material source-rights questions, private information and commercial commitments go to Marc. You can suggest a correction and read the public correction log.

Who it is for

Researchers, start-ups and engineers looking for compute. Communities and councils trying to understand a proposal. Journalists, students and analysts checking a claim. It is built for a quick answer on a phone and for a careful read at a desk.

A place in the conversation

What could this make possible here? What would it ask of the people who live here? We want to help communities explore both questions, from power, water and planning to skills, local access and potential shared benefit.

Concerns deserve a fair hearing. Opportunities deserve a proper look. A proposal, a promise and a delivered benefit are different things. Our aim is a shared, checkable picture that helps people form their own judgement, with unknowns visible and sources open to scrutiny.

Start with the recorded projects, the rules by place or free and funded access routes. If the record is missing something, suggest evidence or a correction.

A useful resource and a sustainable business

ComputeFinder aims to support the people and places shaping the compute infrastructure rollout, and to earn a good living through that work. We are developing ways to earn income that fit the project's values: useful intelligence, human agency, care for communities and honest evidence.

Commercial relationships will be clearly labelled. Paid work and published evidence have distinct terms, and payment must not turn a proposal into a fact or a promise into a delivered benefit. The data's existing licences and source terms continue to apply.

How it is built

Pages are plain text first. Records show source links, recorded check dates and evidence limits. A check date does not confirm present conditions, and a new page or build does not renew the underlying evidence. Gaps are shown as gaps. See the method and the sources.

Contact

Write to hello@computefinder.net. To report a wrong number, use the corrections page.