Aditya Chempakasseril
Software Engineer, Italic
GA_ID: "GTM-ORHNK2"NEXT_STATIC_PORTAL_ID: "23423498"API_ENDPOINT:"https://acme.com/graphql""https://acme.stellate.sh"ORBIT_AUTH_KEY: "ob_23ksdklsadfk"
Users rightfully expect fast and reliable services. Protect your business with GraphQL Edge Caching. Reduce your serverload by up to 99% and never worry about downtime again.
20.5%
Less API traffic
“The requests our origin has to handle dropped by more than 50% — we don't even notice traffic spikes anymore!”
Ivan Vanderbyl
CPO & Co-Founder, Airheart
Get ~40ms response times worldwide. Get your users the speed they deserve.
Add caching to any GraphQL API. Just like you're used to with REST APIs.
Protect your API from traffic spikes and downtime. Allow your users to rely on you, always.
Reduce your origin load by up to 95%. Handle any traffic spike, avoid downtime and save costs.
Resolve stability issues with auto retries and stale-while-revalidate. Steady wins the race.
With no configuration, get real-time observability for your GraphQL APIs usage, performance and errors.
Understand the traffic on all queries, types and operations. Get granular insights and always know what's going on.
Track and understand all HTTP & GraphQL errors. Get insights, build on facts and iterate with confidence.
Check the origin response times for each query and mutation. Know where to optimize your API.
Learn about speed drops and errors the second your users do. Define who gets notified about what.
Protect your GraphQL API from scrapers, traffic spikes, exploding infrastructure costs, and broken SLA terms.
Malicious actors, misconfigured clients, and traffic spikes can cause slowdowns or downtime for your GraphQL API.
While serverless infrastructure allows you to scale quickly, it can also get very costly.
Ensure your customers with Service Level Agreements (SLAs) that require them to stay within their traffic allowance.
If you have valuable data, you can bet that somebody will attempt to scrape it for their own use.
It’s the product the team wished for while creating the leading GraphQL open source projects.
30.6%
Faster p50 API response time
“For 80% of our queries, performance went up significantly: Our GraphQL API’s overall p95 response time has decreased by over 10 seconds!”
Matt MacGillivray
Founder, InnerSpace
Run the command below, point your GraphQL client at the gateway URL, and witness the fitness.
npx stellate serve --backend-port 4000Copy the command and add your api endpoint port. That’s it.Getting dependencies...Creating local dev environmentA Stellate service for your local GraphQL API
is now running at http://localhost:5800!
Enter your own API endpoint, have it up and running in 5min.
“Caching responses has always been a pain for us but with Stellate’s GraphQL Edge Caching we had it set up in minutes.”
Eliezer Steinbock
Founder, Draft Fantasy
“The main feature in our release was live collaboration, but we actually received more praise for the performance improvements from using Stellate’s GraphQL Edge Caching!”
Vincent Battaglia
CTO, Ludus
“We are seeing a major difference in server load and response times for our users. I would highly recommend Stellate’s GraphQL Edge Caching to everyone with a GraphQL API!”
Corjen Moll
Co-founder, Reversed Digital
It takes less than 5 minutes to set up a fully functional CDN for your GraphQL API.