Teams
Manage team ownership, roles, invitations, alert delivery and plan limits.
Every account is a team, including a team of one. The team owns the projects, the monitors and their history, not the person who created them. This is why any member can work on any monitor, and why alerts go to every member.
Roles
| Role | Shown as | Can |
|---|---|---|
admin | Admin | Everything, including team settings, billing, and inviting or removing members. |
member | User | Work with projects and monitors. |
The role belongs to the membership, not the person.
The team's owner is always an admin, and cannot be demoted or removed. Billing belongs to them.
Inviting people
Invite by email address from the team settings. The invitation is a link; accepting it joins that team.
One account belongs to one team. An email address that already has a Rippler account cannot be invited into another team. The invitation is refused with a message saying so. Someone who needs to move teams needs a different address, or their existing account removed first.
Alert emails are personal
Whether a person receives alert emails is a setting on their own profile. An admin cannot set it for them. Switching it off stops their delivery and changes nothing about what the team alerts on.
The members list shows who has alerts off.
API tokens
Tokens are personal, and created under Account → API. A token resolves to the team the person belongs to, so no API path carries a team id. Anything a member can do in the app, their token can do through the HTTP API.
Removing a person from the team revokes their token.
Plans and allowances
| Plan | Monitors | Price |
|---|---|---|
| Indie | 10 | Free |
| Business | 100 | $25 a month |
The allowance limits how many monitors you can create. Only an admin can change the plan. Everyone on the team can see which one you are on.
How long logs are kept
| Plan | Cron monitor log | Website monitor log |
|---|---|---|
| Indie | the last 100 pings, per monitor | the last 7 days |
| Business | 6 months | 6 months |
Indie counts pings rather than days for a cron monitor because a fixed number of days would leave a monthly job with an empty log. A count of 100 covers your last hundred pings whether that is a day or two years. A website is checked every few minutes, where a hundred checks would be a few hours, so it keeps a week instead.
Uptime history and status history are not affected. The uptime bars go back 90 days on every plan.
If a subscription ends
Nothing stops immediately, and nothing stops without warning.
For 30 days everything runs as before: every monitor is watched and every alert is sent. You cannot create a new monitor while you are above the free allowance. We email the team's admins when the plan ends and again as the date gets closer, and the app shows a banner throughout.
After 30 days, monitors above the free allowance are paused, newest first, so the ones you have had longest keep running. If you have 43 monitors, the 10 oldest keep running and the 33 newest pause.
Your logs are not cut back to the free window when a subscription ends. We keep storing 6 months and stop showing you past the free window, so resubscribing brings the whole log back.
A paused monitor is not deleted. It keeps its name, its history and its settings, but it is no longer watched and does not alert. Resubscribing resumes all of them at once. They cannot be resumed one at a time on the free plan.
Monitors you paused yourself are not affected, and stay paused after you resubscribe.