Until today, every request to api.ssimplifi.com — whether it came from Bangalore, London, or San Francisco — had to physically reach an EC2 instance in Mumbai before anything happened. For our Indian customers that's invisible: under 20 milliseconds of network time before Prism does its first byte of useful work. For a developer in San Francisco, it was a different story: roughly 250 milliseconds each way before we'd even classified the request, before we'd checked the cache, before we'd called the AI provider. We could be the fastest proxy in the world internally and the customer in California would still see half a second they shouldn't have to.
v1.6 fixes the half-second. The way it fixes it is the part that took some thinking.
The simple version
api.ssimplifi.com is now fronted by a Cloudflare Worker. Cloudflare runs that worker in 300+ cities around the world. A request from San Francisco hits the Cloudflare datacenter in San Francisco; a request from London hits London; a request from Bangalore hits Bangalore. The worker does three things at that local datacenter:
Parses the Authorization header, hashes the API key, and checks whether it's valid. If it's malformed or unknown, it returns a 401 right there — never round-trips to Mumbai. That's about 250 milliseconds saved for every bad request, every opportunistic scan, every developer who pasted the wrong key into their code.
