From first look to first alert — four steps.

1. 01

   Understand

   See what IRIS does — and what you need

   IRIS does not replace your monitoring; it makes sure a human acts on what your monitoring finds. Alerts escalate round by round — up to ~20 rounds — until someone acknowledges, and every step is recorded. To start, you need three things, all of which you almost certainly have already.

   How IRIS works, end to end

   • A work email address — you will be the workspace admin
   • An admin mobile number — critical alerts reach you by SMS and voice, so we verify a real one
   • A system that can call a webhook or send an email on an event — that is the entire integration
2. 02

   Sign up

   Create your workspace — about a minute

   Sign-up is fully self-service and free: 1,000 credits (about 80 SMS alerts, worth €10), no credit card. Three short steps, each verified as you go.

   Start free — 1,000 credits

   • Verify your work email with a 6-digit code
   • Verify your admin mobile with an SMS code (international format, e.g. +358…)
   • Name your workspace, set a password (12+ characters) — your EU workspace is provisioned immediately
3. 03

   Your data

   The DPA, in plain terms

   When you send alerts through IRIS, you stay the controller of the recipient data and alert content you provide; MeshWorks Wireless Oy acts as your processor and touches that data only to deliver the service, on your instructions. The Data Processing Agreement is structured to GDPR Article 28 and is accepted as part of sign-up — one checkbox, no separate paperwork. Your core alerting data lives on EU infrastructure by architecture, and our subprocessors are published openly.

   Read the DPA summary

   • You: controller. MeshWorks: processor, acting on your documented instructions
   • DPA + Privacy Notice accepted in the sign-up flow — no separate signature round
   • EU data residency by architecture; subprocessor list published and maintained
4. 04

   First alert

   Wire it up and send a real test

   Inside your workspace: add the people who should be paged, connect whatever detects your problems, and fire a test. Acknowledging the alert — reply “1” by SMS or press a key on the voice call — stops the escalation and closes the loop.

   The API and email-in trigger

   • Configuration → Receiver groups: who gets paged, in what order
   • Connect your monitoring: one REST call — or an email-in trigger address if your tool can only send email
   • Send a test alert, acknowledge it, and check the audit trail record it leaves behind

This page is a plain-language summary, not the agreement itself. The binding texts are the Terms of Service, the Data Processing Agreement and the Privacy Notice you accept at sign-up.