I first thought about building getrequest in 2023, while I was at a startup. When our traffic spiked or something went down, API requests to our system could fail or disappear and recovery was painful. I kept wishing if there was a simple layer that I could put in front of our APIs to handle the traffic. I wanted to build it then, but a rapidly growing startup meant I never really had the time.
A couple of years later, after co-founded another company in a different space, the journey made something increasingly clear: I kept thinking about this particular problem again and again. So, last month, I decided to stop keeping getrequest as an idea. I quit everything and started building it day and night. Here I am with the first version: "the" layer that sits in front of your backend so traffic spikes, downtime, or failed deployments never result in lost API requests.
Founder here,
I first thought about building getrequest in 2023, while I was at a startup. When our traffic spiked or something went down, API requests to our system could fail or disappear and recovery was painful. I kept wishing if there was a simple layer that I could put in front of our APIs to handle the traffic. I wanted to build it then, but a rapidly growing startup meant I never really had the time.
A couple of years later, after co-founded another company in a different space, the journey made something increasingly clear: I kept thinking about this particular problem again and again. So, last month, I decided to stop keeping getrequest as an idea. I quit everything and started building it day and night. Here I am with the first version: "the" layer that sits in front of your backend so traffic spikes, downtime, or failed deployments never result in lost API requests.