Acciti
Start free

Provisore alerts on your iPhoneHear it the moment a server goes down.

Provisore deploys, monitors and backs up your servers. Add Acciti as a channel and outages, failed deploys and failed backups ring your phone. Successful deploys stay quiet.

Connect ProvisoreRead the docs

How do you connect Provisore to Acciti?

Provisore ships an Acciti channel and Acciti ships a Provisore connector, so there's no field mapping and no rule to write first.

1

Create a Provisore connector

In Acciti, add a connector and choose Provisore. Copy the ingest URL and the signing secret. The secret is shown once.
2

Add an Acciti channel in Provisore

Paste the URL and the secret. Provisore signs every event with it in an X-Provisore-Signature header.
3

Get alerts

Rules for every Provisore event come with the connector, so the next monitor that goes down reaches you.

Which Provisore events wake you, and which don't?

Each event arrives at the priority that fits it. A service that's down right now rings until someone acknowledges it. Something that will break soon waits for a normal notification. A deploy that worked makes no sound.

2Emergency

Repeats until someone acknowledges it, then escalates to the next person on call.

  • monitor.downAn uptime monitor is confirmed down.
  • deployment.failedA deploy failed.
  • restore.failedA restore from a backup failed.

1High

Breaks through Focus and quiet hours.

  • certificate.renewal_failedA certificate did not renew before its danger window.
  • backup.failedA scheduled or manual backup failed.
  • rollback.failedA rollback to an earlier release failed.
  • server.failedProvisioning a server failed.
  • alert.triggeredA server metric alert crossed its threshold.

0Normal

A banner and the sender's sound. The default.

  • certificate.expiringA certificate is inside its expiry warning window.

-1Quiet

A banner without a sound.

  • deployment.succeededA deploy finished.Off
  • server.provisionedA server finished provisioning.Off
  • monitor.upAn uptime monitor recovered.
  • alert.resolvedA metric alert cleared.

Every alert names the server.

The rule fills the title and body from what Provisore sends. A monitor going down arrives at priority 2, repeats until someone acknowledges it, and can escalate to whoever is on call.

What Provisore posts
{  "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"}

api.acme.com is down

now

Provisore's monitor for api.acme.com is down.

Provisore · alarm

Quiet when things work

Successful deploys and new servers are in the catalogue and off by default. Turn them on if you want them.

A sound of its own

Provisore events arrive from the sender you choose, with its own sound, so you can tell them from your scripts without looking.

A retry never rings twice

Every event carries a delivery ID, so a redelivered event is recognised as one you've already had.

Paused, never deleted

If your plan lapses, the connector keeps logging events and stops notifying. It picks up again when the plan comes back.

The next outage rings your phone.

Create the connector and paste two values into Provisore. Every other connector works the same way.

Connect ProvisoreSee pricing