PeakPeeker started because I wanted a better way to plan these trips myself.

I wanted to hike routes like Half Dome and the Enchantments, kept running into lotteries and narrow permit windows, and eventually ended up in the same loop a lot of people do: too many tabs open, too much guesswork, and not much confidence that the tools were helping in a sensible way.

The thing that bothered me most wasn't just the permits. It was how clunky the whole experience felt around them. Planning the route, understanding the trailheads, figuring out what was actually worth tracking, and then paying too much for basic alerts all felt like they belonged to different products.

PeakPeeker is my attempt to make that feel more normal: better route context, more useful trackers, and pricing that feels like a practical tool rather than an expensive edge case.

My background is in frontend engineering and product quality, with more than six years at Amazon. That mostly means I care a lot about the small things feeling right: pages loading quickly, the route context being clear, and the product not getting in your way when you're trying to make a plan.

I honestly built this because I wanted to use it myself. It started as a tool for my own trips, and I figured that if it was useful for me, it was probably useful for other people trying to piece together the same kinds of routes and permits.

The goal is simple: build the thing I wish existed when I was the one refreshing permit pages, losing lotteries, and trying to piece together a trip plan from scattered information.