Kerkis exists for one situation: you are responsible for a lot of premises, the duties differ site by site, and one day someone will ask you to justify a decision made years earlier by somebody who has since left.
The Terrorism (Protection of Premises) Act 2025 puts a duty on a named responsible person. For a single venue that is manageable with the free templates the Home Office and ProtectUK already publish, and if that is your situation you should use them.
It stops being manageable at scale. Forty premises means forty capacity figures, each one determining a different tier, each tier carrying different duties, each procedure ageing at a different rate, and staff turnover quietly eroding the one thing you thought was settled. The failure is rarely that nobody wrote anything down. It is that nobody can find the version that was current on the day it mattered.
That is a record-keeping problem before it is a security problem, and record-keeping is what software is genuinely good at.
Neither staff training nor drills are required by the Act, standard tier premises submit nothing beyond a notification, and there is no documentation duty below 800. A vendor that lets you believe otherwise sells more. We would rather you bought the thing you actually need.
Every tier determination records the occupancy figure, where it came from, which areas were counted and who signed it off. A judgement made in 2026 has to still hold when it is questioned in 2029, and it only holds if you can see how it was reached.
Sites that fall out of scope cost nothing. That removes any incentive to nudge a borderline site upward, and it is what makes the free scope check safe to be honest with you.
Every table is protected by database-level row security, and a test suite seeds two organisations and asserts that neither can see a single row belonging to the other. It runs on every change, and it fails the build if a policy is ever dropped.
A kerkis is the wedge of seating between the stairways of a Greek theatre. The stairways are why the wedge is that shape: they are how a full house gets out. Every seat in it was placed knowing where the crowd would go.
That is the argument of this product in one word. The number of people you expect is the number that decides everything, and planning for them leaving safely is not an afterthought bolted onto the building. It is what determines the shape of it.
Customer data on the paid platform will be held in the United Kingdom. Every third party that touches anything is named on our sub-processors page, with what they see, where they are, and the basis for it. Behind it sits the rest of the pack - records of processing, a response to all fourteen NCSC cloud security principles, the security update commitment, the incident response process and a DPIA support pack. Written already rather than assembled once someone asks, and sent to anyone running a supplier review.
Kerkis is a record-keeping tool. Responsibility for meeting the duties rests with the responsible person, and nothing here is legal advice.