Investors
The operating system for teams that protect their own.
A working product in the hands of real operators, in a category no European company serves, sold to organisations that already spend on protection and have nothing that coordinates it. This page is the short version; the memorandum is available on request below.
Why now
Protection became a standing function, and the money followed.
The threat has not reverted
Across Europe, communities and institutions that treated security as an event-day matter now run it every day: rosters, posts, briefings, incident logs. The recorded incident numbers are a multiple of three years ago, and under-reporting means they understate it.
Public funding flows through umbrella bodies
National protective-security schemes in the UK, Denmark, Sweden and elsewhere fund staff on duty as well as cameras and fencing, and they pay through the organisations that are Reyia's buyers. One contract, many sites.
The coordination layer is missing
Grants buy guards and hardware. They do not buy the system that says who is on duty where, gets the brief to the door, and records last night in a form anyone can review. That is still group chats and spreadsheets.
The gap
Nobody serves the whole job.
Guard-workforce tools do not hold intelligence or procedures. Community-management systems do not run security operations. Panic apps cover one moment. Enterprise security platforms are built for a control room, not for a team of twelve with phones. The nearest category is American and church-centric; in Europe, this work is done in-house, without software.
Reyia enters at the hardest segment first: organisations with several sites in several countries, a professional security function and the most sensitive data. A reference there carries into every adjacent one: institutions, campuses, venues, close-protection teams, and the mutual-aid networks between them.
Pricing scales with sites and seats under a contract floor. Expansion is built in: Reyia was designed from the first day for many organisations, many cities, and no client's name anywhere in it.
What exists
A product operators use, not a prototype.
Every claim on this site is about something a team can use today. What is coming is in the memorandum, labelled as coming.
In the hand
The operator's app
Shifts, presence, the brief, incidents, emergency, voice and an assistant, in one app that feels like equipment.
Behind it
A platform of our own
Built and run by the company in Europe, independent of any client and of any outside vendor for the parts that matter.
Around it
Oversight for the organisation
Administration, verification, roles, the activity log and a dashboard for the people who oversee several sites.
Proven
With a design partner
Built with and used by a multi-site organisation with a professional security function; the pilot's terms and timeline are in the memorandum.
Risks, named
What we watch, and what we do about it.
Key-person risk
The largest single risk, addressed directly: documented ways of working, a second engineer sharing responsibility for the running service, and a continuity commitment in every client contract.
Procurement cycles
Umbrella bodies buy slowly and carefully. The answer is a paid pilot with written success criteria, references in the segment, and pricing that fits a grant line.
Regulation
Incident reports, presence and watch lists each carry specific legal obligations. We treat them as design constraints with counsel engaged, and they penalise improvised tools more than a product built for the data.
Direct
A note on claims
Figures on this site are those the company has stated and can stand behind. Where a number is not shown it is because it is not yet measured, not because it is hidden. Ask; we will say which.