Provisore
Provisore knows the server is down. Acciti is what wakes you.
Provisore deploys your servers, watches them, renews their certificates and backs them up. It can already tell Slack, Discord, email or a webhook when something happens. Add Acciti as a channel and the things that cannot wait until morning make a noise on your phone, while the ones that can stay quiet.
How do you connect Provisore to Acciti?
Make a Provisore connector in Acciti, copy the ingest URL and the signing secret it shows once, and add an Acciti notification channel in Provisore with those two values. That is the whole of it: no translation layer, no field mapping, no rules to write first.
Provisore signs the exact bytes of every event with the secret, in an X-Provisore-Signature header, so a correct signature proves both that Provisore sent it and that nothing changed on the way. A delivery id travels with it, so a retried event is recognised as the same event rather than ringing twice.
Which Provisore events wake you, and which do not?
The mapping ships with the connector and is one question asked four ways. Is somebody's service down right now. Is something broken that will take it down. Is something going to break. Or did something simply work.
EmergencyRepeats until somebody acknowledges it on one of their devices, and climbs an on-call ladder if nobody does.
monitor.down- An uptime monitor is confirmed down.
deployment.failed- A deploy failed.
restore.failed- A restore from a backup failed.
HighBreaks through a Focus mode and through the recipient's quiet hours.
certificate.renewal_failed- A certificate did not renew before its danger window.
backup.failed- A scheduled or manual backup failed.
rollback.failed- A rollback to an earlier release failed.
server.failed- Provisioning a server failed.
alert.triggered- A server metric alert crossed its threshold.
NormalA banner and the sound the sender named. The default.
certificate.expiring- A certificate is inside its expiry warning window.
QuietA banner without a sound.
deployment.succeeded- A deploy finished. Off by default.
server.provisioned- A server finished provisioning. Off by default.
monitor.up- An uptime monitor recovered.
alert.resolved- A metric alert cleared.
What does a Provisore alert look like when it arrives?
The rule fills a title and a body from the event, so the notification names the server rather than the event type. A monitor going down at emergency priority repeats until somebody acknowledges it, and can carry an escalation policy so it climbs to whoever is on call when nobody does.
{ "event": "monitor.down", "status": "confirmed", "resource": "api.acme.com", "resourceId": "mon_7f2c", "timestamp": "2026-09-18T02:14:03Z", "url": "https://provisore.example/monitors/mon_7f2c"}- Deploys that worked stay quiet
- A successful deploy and a provisioned server are in the catalogue and switched off. Turn them on if you want them; nothing does by default.
- One sender, one sound
- Every Provisore event arrives from the sender you named, so it is distinguishable from your own scripts before you look at the screen.
- Both sides are first-party
- Provisore ships an Acciti channel and Acciti ships a Provisore kind. Neither is a generic webhook that happens to fit.
- Nothing is lost when the plan lapses
- Connectors are paused rather than deleted. Events still arrive and are still logged; they stop notifying, and start again when the plan comes back.
One channel, and a phone that knows.
Make the connector, paste the URL and the secret into Provisore, and the next monitor that goes down reaches you. Every other connector works the same way.
Connect Provisore