This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Gridstate
Grid capacity evidence for large load sites
Answering "can this site take 120 MW" means reading a tariff PDF, an ISO queue spreadsheet, a transmission plan, and a state docket that disagree on what the utility is even called. Gridstate normalizes them into an API where every field cites its source document and page. Facts are bitemporal, so you can ask what a tariff said on a date and separately what we knew on a date. Capacity comes back as utility confirmed, published, indicative, or unknown. Most sites are unknown.
Hi PH,
Answering "can this site take 120 MW" currently means fifteen browser tabs: a utility tariff PDF, an ISO queue spreadsheet, a transmission plan, a state docket. They disagree on what the utility is even called, and the answer expires in a few weeks.
Gridstate turns that into an API where every field cites its source document and page. Facts are bitemporal, so you can ask what a tariff said on a date and separately what we knew on that date.
It won't output available megawatts. Capacity comes back as utility confirmed, published, indicative, or unknown, and most sites are unknown. Deriving a number from queue data would be easy and wrong: queues measure development interest, not load-serving capacity.
There's an MCP server over the same API. Happy to answer questions about coverage.
About Gridstate on Product Hunt
“Grid capacity evidence for large load sites”
Gridstate was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #77 on the daily leaderboard. Answering "can this site take 120 MW" means reading a tariff PDF, an ISO queue spreadsheet, a transmission plan, and a state docket that disagree on what the utility is even called. Gridstate normalizes them into an API where every field cites its source document and page. Facts are bitemporal, so you can ask what a tariff said on a date and separately what we knew on a date. Capacity comes back as utility confirmed, published, indicative, or unknown. Most sites are unknown.
On the analytics side, Gridstate competes within API, Developer Tools and Artificial Intelligence — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how Gridstate performed against the three products that launched closest to it on the same day.
Who hunted Gridstate?
Gridstate was hunted by Tyler Gibbs. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Gridstate including community comment highlights and product details, visit the product overview.
Tyler Gibbs