Your Situation Room, on your terms.
For institutions, large observer networks and campaign situation rooms that need their own deployment, their own brand, and EIRIS connected to the systems they already run.
A tenant-branded Situation Room. Example organization, demo data.
Three ways to run EIRIS.
The product is the same in each. What changes is who shares the infrastructure and who holds the keys. Enterprise and Private deployments are scoped with each organization.
Shared infrastructure, isolated data.
Many organizations on one EIRIS platform, each kept apart by tenant isolation. The quickest way to start.
Suited to
- Observer groups and NGOs
- Media monitoring desks
- Small and medium institutions
EIRIS Cloud · shared
Your name on the door.
Your agents sign in to your organization. Your partners receive reports with your header. EIRIS stays underneath, as the product that runs it.
Organization branding
- Logo
- YO logo.svg
- Primary colour
- #0F766E
- Domain
- monitor.organization.org
- Email sender
- situation-room@organization.org
Your Organization
Situation Room sign-in
Sign inPowered by EIRIS
Situation report
Governorship · Bauchi LGA · demo data
Your Organization · Prepared with EIRIS · Page 1 of 4
- Logo and name
- Primary and secondary colour
- Custom domain
- Sign-in screen
- Situation Room
- Report headers and footers
- Email sender
- SMS sender
Connect EIRIS to the systems you run.
Pull incidents, results and reports into your own tools, or have EIRIS tell your systems the moment something changes. Every key and every delivery is scoped to your organization and recorded.
POST /hooks/eiris HTTP/1.1Host: ops.organization.orgContent-Type: application/jsonEIRIS-Event: incident.escalatedEIRIS-Delivery: dlv_8c1f20e4EIRIS-Signature: t=1803138127,v1=5d0b6c1e9a…a94f{ "event": "incident.escalated", "organization": "org_a1f", "election": "gov-demo", "occurred_at": "2027-02-20T16:42:07+01:00", "data": { "incident": "INC-0412", "severity": "high", "category": "Materials not delivered", "polling_unit": "05/02/06/014", "ward": "Kangere", "lga": "Bauchi", "escalated_to": "lga_coordinator", "evidence": [{ "type": "photo", "sha256": "9f2c41e0…7b12" }] }}
Delivery log
- 16:42:07503retry in 30s
- 16:42:38503retry in 2m
- 16:44:39200delivered
API keys
- read:incidents
- read:results
- read:reports
- read:analytics
- write:reports
Keys are stored hashed, scoped to one organization, revocable at any time, set to expire where possible, and every use is audited. Creating one is a confirmed, high-risk action.
- incident.created
- incident.escalated
- result.submitted
- result.verified
- agent.checked_in
- report.created
Capacity that follows the calendar.
An election is quiet for weeks, then intense for a day. EIRIS adds capacity before election day and removes it after, so you are not paying for election day all year.
- Load-tested on staging before each election
- One database stays the source of truth
- Evidence storage does not shrink after the day
App / API × 4
Jobs × 3
Election day. Burst capacity for check-ins, incidents, uploads and results.
illustrativePractise the whole day before it counts.
Separate environments let your Situation Room rehearse with synthetic data and your agents practise on their own phones. None of it can reach live election records.
Production
Real agents, real evidence, real results. Protected, backed up, and restore-tested before the day.
Election rehearsal
Simulate check-ins, incidents, uploads, results and messages. The Situation Room runs the day end to end. A permanent banner says it is not live.
Agent training
Agents practise sign-in, check-in, incidents, photos, offline mode and results. Reset before the election.
Help that leaves a trail.
Sometimes the fastest fix is to see what a coordinator sees. When support views EIRIS as one of your users, it is with your permission, for a stated reason, for a limited time, and on the record.
- Explicit permission from your organization
- A banner visible on every screen
- A written reason
- A session that expires on its own
- Every action recorded in the audit log
Reason
Coordinator cannot see two newly assigned polling units.
Approved by
Election admin, 16:02 WAT
- 16:04:12support.session.startedreason recorded
- 16:05:40assignment.viewedDawaki · 2 units
- 16:07:03assignment.updatedPU 05/02/04/018 added
- 16:07:30support.session.endedby support
Tell us about your election. We'll scope the rest together.
Your geography, your reporting structure, your timeline and your hosting requirements. Commercial terms are set per engagement once we understand what you need.