Start saving money. Today.
Your traffic starts routing through Sherpa.sh immediately at our flat rate. Watch your existing provider's usage - and bill - drop in real time.
- Cut your hosting costs by up to 70%
- No waiting for DNS propagation or deployment cycles
- Your fallback provider sees decreasing usage automatically
- Keep SafetyNet active for disaster recovery or until you no longer need it
Zero risk. That's the point.
Keep your existing deployment running. If anything goes wrong, traffic automatically routes back. Your users never know the difference.
- Automatic sub-second failover to your existing provider
- Test in production with real traffic, safely
VPs of Engineering approve migrations faster when there's zero downtime risk. SafetyNet removes the biggest objection to switching platforms you will face internally.
Set up in 5 minutes. No complexity.
Enable SafetyNet from your dashboard. Add your fallback URL. Done.
Deploy to Sherpa.sh
Connect your repo and deploy as usual
Enable SafetyNet
Toggle it on in your app settings
Add fallback URL
Enter your existing deployment URL (e.g., your-app.vercel.app)
Questions about SafetyNet?
Our team is here to help you plan your migration.
Perfect for
- Testing Sherpa.sh with production traffic before committing
- Gradually migrating from Vercel, Netlify, or AWS without risk
- Reducing infrastructure costs immediately
- Keeping disaster recovery in place long-term
Framework-agnostic
Works with all Sherpa.sh supported frameworks and deployment types.
Talk to our team
Get expert guidance on your migration strategy.
Or read the docs to learn more
Frequently asked questions
Does SafetyNet increase my costs?
No. You only pay the Sherpa.sh flat rate. Your fallback provider bills decrease as Sherpa.sh handles more traffic. Most customers see immediate cost savings.
How fast is the fallback?
Typically 50-150ms to reroute to your fallback provider. Users experience minimal delay. Edge routing decisions happen in sub-millisecond timeframes.
Can I use multiple fallback providers?
Currently SafetyNet supports one fallback URL per deployment. Contact us if you need a custom configuration.
Does this work with API routes?
Yes. SafetyNet works for all HTTP requests, including API endpoints, static assets, and server-rendered pages.
What if both Sherpa.sh and my fallback fail?
If both Sherpa.sh and your fallback provider have issues, users see the error from the fallback provider. This is the same behavior as if you were only on the fallback provider.
Can I customize which errors trigger fallback?
The default configuration falls back on all error responses (4xx and 5xx). Contact support for custom edge script configurations.
What happens to cached content?
Responses with appropriate cache-control headers are cached at our CDN edge. Subsequent requests are served from our cache, not your fallback provider - saving you money even during fallback scenarios.
When should I disable SafetyNet?
Disable it when you're confident in your Sherpa.sh deployment. But there's no rush - many customers keep SafetyNet active long-term as disaster recovery.
Still have questions?