Why this policy exists
silyring is designed for meaningful, event-driven notifications — a deploy failed, a server went down, your pizza arrived. This policy ensures the service remains fast and reliable for everyone.
Acceptable use
silyring is intended for:
- CI/CD pipeline alerts (build failures, deploy completions)
- Server monitoring and uptime alerts
- Cron job notifications
- Personal reminders and automations
- IoT and smart home triggers
- Any legitimate event-driven notification use case
Rate limits
Calls30 per hour
Push notifications120 per hour
Daily maximum (calls)200 per day
Daily maximum (push)1,000 per day
Requests exceeding these limits will receive a 429 Too Many Requests response. Limits reset on a rolling window.
Prohibited use
The following are not allowed:
- Spamming — Sending excessive, repetitive, or meaningless notifications
- Harassment — Using someone else's webhook URL to send unwanted calls or messages
- Automated abuse — Tight loops, stress testing, or intentionally overwhelming the service
- Commercial bulk messaging — Using silyring as a mass notification platform for end users
- Reselling — Reselling access to silyring's API or service
- Circumvention — Creating multiple accounts or devices to bypass rate limits or trial periods
Enforcement
If we detect usage patterns that violate this policy:
- First notice — We'll temporarily rate-limit your webhook and attempt to notify you
- Continued violation — Your webhook URL may be suspended
- Severe abuse — Your device may be permanently banned from the service
We'll always try to reach out before taking action. Most violations are accidental (a runaway script, a misconfigured cron) and easily fixed.
Paid plans
Higher rate limits will be available on paid plans in the future. If your use case requires more than the free-tier limits, reach out — we're happy to work with you.