We started GridGate after discovering that the interconnection process is shaped more by political and regulatory decisions than by grid engineering — and that nobody was building tools for that reality.
GridGate originally set out to predict interconnection upgrade costs — the fees that developers pay to improve the electrical grid so their projects can connect. We thought better cost estimates would be the biggest unlock for energy developers.
We were wrong. Or rather, we were solving the wrong problem.
Through conversations with transmission owners, interconnection leads, and project developers at companies across the industry, we kept hearing the same thing: cost modeling is important, but it's not what keeps them up at night.
What keeps them up at night is the regulatory and political uncertainty. A state commissioner who changes their stance on renewable interconnection. A county board that votes to block a solar project. A policy shift that rewrites the rules mid-process. These are the risks that actually kill projects — and there's no software tracking any of it.
We redirected the entire company toward building the political and regulatory intelligence layer that the interconnection market is missing. Instead of replicating what Nira Energy and similar platforms already do well on the engineering side, we focused on the gap they can't fill: the human, political, and social dynamics that determine whether a project lives or dies.
These aren't abstract values — they're the specific beliefs that shape our product decisions and how we work with customers.
The interconnection crisis isn't just about grid capacity or staffing shortages at grid operators. It's about developers making massive financial commitments without the information they need. We believe better intelligence leads to better decisions and less waste.
The energy industry treats political and regulatory risk as something to manage through lobbying and relationships. We believe it should be tracked, modeled, and analyzed with the same rigor as engineering constraints.
Every feature we build is driven by direct customer feedback and validated willingness to pay. We don't build technology looking for a problem. We find the problems first, then build the minimum viable solution.
We're a small, focused team that combines energy market knowledge with software engineering. Everyone works on the product.
Kiran leads strategy, customer development, and product direction. He built GridGate's go-to-market approach through direct conversations with developers, transmission owners, and interconnection leads at energy companies including Savion Energy.
His background is in energy market analysis and business operations. He's responsible for identifying GridGate's pivot from cost prediction to political intelligence — a decision driven entirely by what customers said they'd actually pay for.
Magnus leads GridGate's technical architecture and engineering team. He's responsible for the platform's data infrastructure, including the scraping pipelines, natural language processing systems, and predictive models that power the intelligence layer.
Jay works on data infrastructure and the regulatory data pipeline — building the systems that ingest, clean, and structure information from thousands of public sources across multiple jurisdictions.
Daniel works on the frontend and data visualization layers, building the interfaces that translate complex political and regulatory data into actionable views for developers.
Daigo works on the natural language processing and sentiment analysis systems that power GridGate's community intelligence module.
Started with a focus on predicting interconnection upgrade costs for energy developers. Began building the initial data infrastructure and scraping pipelines.
Conducted extensive customer discovery with transmission owners and energy developers. Discovered that political and regulatory intelligence — not cost modeling — was the unaddressed need. Pivoted the entire product direction.
Defined the three-module platform: political and regulatory tracking, community sentiment analysis, and queue dropout prediction. Redirected the engineering team to build for the MISO region first.
Onboarding early design partners — mid-size developers in the MISO queue who want intelligence that goes beyond grid engineering. Actively building toward the first paid deployments.
Whether you're an energy developer, an investor, or just someone who cares about fixing the interconnection process — we'd like to hear from you.