Status pages and badges
Publish a public status page and embed SVG badges.
Pages
Every monitor is on a page, and every account starts with one. Pages group monitors on your Monitors screen, where each has a section, and each one becomes a public status page of its own as soon as a monitor on it is public. The new monitor form asks which page a monitor goes on, and can make a new page for it. Paid plans can have more than one page, so a public page for customers can sit beside a private one for internal jobs.
Status page
Tick Public on a monitor's form. That is the only switch: a page with at least one public monitor has a status page at https://vivere.dev/s/<account>/<page>, showing each of its public monitors' status, last seen time and 30-day uptime, and an overall banner. Monitors that are not public never appear there, and a page with none has no status page. A page's settings in Pages say how many of its monitors are public, and can make them all private at once. Your account's own address, https://vivere.dev/s/<account>, goes to its first page when that page is public.
Sharing a page
On a paid plan, open a page's settings in Pages and share it by email with anyone who has a Vivere login. It appears on their own Monitors and Pages screens, labelled with your account's name; nobody has to leave their account to see it. Sharing does not make anything public, and a page does not need public monitors to be shared: whoever you share it with sees all of its monitors, public or not, while the public sees only the public ones. Every account you share with takes one seat, viewer or editor: 5 on Pro, 100 on Team.
- A viewer sees the status and history of the page's monitors, and nothing else: no monitor ids or ping URLs, no targets, no badges, no changes.
- An editor can add, change, pause and delete the page's monitors and send their alerts to their own channels as well as yours.
Teams
On the Team plan, put the people you work with into teams under Teams in your account menu, and share a page with a team from the page's settings instead of with each person. Everyone in the team gets the team's role on that page, viewer or editor, and so does anyone you add to the team later; take someone out and they lose what only the team gave them. Somebody reached both directly and through a team, or through two teams, gets the strongest of those roles and still takes one seat. Teams are yours alone: their members see your pages as tabs, never the team. If your plan leaves Team, team shares stop working until you come back, while direct shares carry on as your new plan allows.
What a share allows is decided each time it is used. If your plan drops to Free, shared pages stop appearing for everyone you shared them with until you upgrade again, and their channels are taken off your monitors. If you have more shares than seats, the most recent ones stop seeing the page until a seat frees up. Removing someone takes their channels off the page's monitors too.
Badges
Public monitors also get an SVG badge that you can embed in a README or dashboard. Copy its address from the monitor's page, under Badge:
<img src="https://vivere.dev/b/<badge-key>.svg?label=nightly%20backup" alt="status">The badge key is the badge's own and does nothing else, so a badge in a public README is safe. It is not the monitor's id, which for a heartbeat monitor is its ping URL.
Badges are cached for a minute. The label query parameter overrides the left-hand text.
Uptime maths
Uptime is the share of the window the monitor was not Down. Late, Paused and New time counts as up; a monitor created inside the window is measured from its creation.