Golemi Proxy - Edge-Based API Caching
API Caching at the Edge — reduce latency, cut costs, and eliminate complex configurations.
Golemi Proxy is a serverless proxy layer running on a global Edge network, sitting between the client and your origin server. Instead of routing every request all the way back to the origin, Golemi caches JSON responses at locations closest to the user—across over 270 Points of Presence (PoPs) worldwide—delivering results in just a few milliseconds.
Common Challenges
Scaling an API globally presents teams with the same set of problems: expensive infrastructure, the need to build custom caching logic, and origin servers prone to overloading during traffic spikes. Golemi was created so you don't have to worry about any of that.
How Golemi Works
- Client Request — a request sent to your API from anywhere in the world.
- Edge Cache Check — if the data is available (cache hit), the JSON is returned immediately.
- Origin Access Only on Cache Miss — your origin server handles only the remaining fraction of traffic, significantly reducing the load.
As a result, a request that might take 240ms when calling the origin server directly takes only about 20ms when served from the Edge cache.
Key Features
- Edge Caching — JSON responses are cached across more than 270 PoPs globally.
- Isolated Cache Namespaces — separate cache namespaces for each environment (dev/staging/production) to prevent data mixing.
- Instant Cache Invalidation via Webhook — refresh the cache immediately using a standard webhook from your CMS or backend.
- Large Payload Support — easily handles JSON responses up to 2MB in size. - Preserve API authentication — your authentication headers are forwarded and validated as usual.
- Live monitoring — view cache hits, cache misses, and origin server status in real-time directly on the dashboard.
Why Teams Choose Golemi
- Significantly reduce infrastructure costs since the majority of traffic is handled at the Edge cache.
- Lower latency for global users, as everyone is served from the nearest Edge location.
- Protect the origin server from sudden traffic spikes or unusual traffic patterns.
Best Suited For
- Headless WordPress sites using WP-JSON
- Legacy APIs that cannot be upgraded yet but require protection against high traffic volumes
- High-traffic public APIs looking to reduce origin server costs
Pricing
Options range from a free plan (10,000 requests/month, 1 project) to an unlimited Enterprise plan with custom SLAs. Paid plans start at just $9/month and include Starter, Pro, and Enterprise tiers.
12x
Faster response times
270+
Global edge locations
10K
Free monthly requests
2MB
Max payload size
Context
The Challenge
Teams hit this in a few common shapes: headless WordPress / WP-JSON endpoints that can't absorb traffic bursts, legacy APIs that can't be modernized but still need protection from abusive load, and high-traffic public APIs where origin costs scale linearly with usage.
Building a global caching layer in-house means standing up infrastructure across regions, writing cache-invalidation logic by hand, and monitoring origin health around the clock — all before a single line of product code ships.
Tech stack
Pricing
Free: 10K requests/mo. Starter $9/mo, Pro $29/mo, Enterprise custom pricing — see golemi.io/pricing.
Our Approach
The Solution
Edge Caching
Responses are cached at 270+ edge locations worldwide, so repeat requests are served in milliseconds instead of round-tripping to the origin API.
Cache Isolation
Every cache key is scoped per API key, so tenants never see each other's cached responses — safe for multi-tenant and per-customer API proxying.
Webhook Invalidation
Push a webhook when source data changes and Golemi purges the matching cache entries instantly, instead of waiting for a TTL to expire.
Live Logs
A real-time request log shows cache hits, misses, and origin latency as they happen, so debugging a caching rule takes seconds, not guesswork.
Results & Impact
Cost & Performance
- Cut API response times by up to 12x for cached endpoints
- Free tier covers 10K requests/month with no credit card required
- Handles payloads up to 2MB without extra configuration
Reliability & Fit
- 270+ edge locations keep latency low no matter where your users are
- Per-tenant cache isolation keeps the proxy safe for multi-customer and compliance-sensitive workloads
- Drop-in reverse proxy — point your existing API URL at Golemi, no client-side changes needed
Have a similar challenge?
Let's talk about how we can help.
Frequently asked questions
What is Golemi Proxy? ＋
Golemi Proxy is an edge-based API caching solution powered by a global edge network. It sits between your clients and your origin API, caching responses at 270+ edge locations so cached requests are served in milliseconds instead of hitting your backend.
Do I need to change my existing API? ＋
No. Golemi works as a transparent proxy — point your API requests through Golemi, configure your cache rules, and your existing API code doesn't need any modifications.
Is my data secure? ＋
Yes. All traffic is encrypted with TLS 1.3, API keys are hashed with SHA-256 and never stored in plain text, and origin credentials are encrypted at rest. Infrastructure is SOC 2, ISO 27001, and PCI DSS compliant.
Can I purge the cache manually? ＋
Yes. You can purge the cache from the dashboard or via API — by specific URL, by path pattern, or for the entire project.
What happens if I exceed my request limit? ＋
We'll notify you at 80% of your limit. If you go over, requests are still served — you'll just need to upgrade your plan to keep caching at that volume.
Is there a free tier? ＋
Yes. The Free tier includes 10,000 requests/month, 1 project, and community support — perfect for personal projects and testing. Paid plans start at $9/month.