In an emergency, Krisis coordinates the help from the population – who needs what, who has what, who is on the way.
When a district is under water, the power has been out for two days or a street is being evacuated, people organise immediately – in chat groups that only reach those already inside. Krisis gives the area one shared, temporary place: what is missing, what is there, who is already on the way, what is done. Alongside the professional responders, never instead of them. And when it is over, it is over.
The app is not in the stores yet; the waitlist writes exactly once, when it exists. Double opt-in, the address is deleted afterwards. No newsletter.
Three properties, in this order
- 01Coordination in the acute crisis
One shared, temporary place for the region: needed, offered, who is on the way, what is done. One conversation per crisis, join and leave – nothing global.
- 02Reach beyond the affected area
The reach of a crisis is deliberately set wider than the damage. The person two towns over with the trailer, the pump or the spare room finds out.
- 03Silent until it counts
No feed, no groups, no reason to open the app on a quiet Tuesday. Krisis speaks up only when something happens nearby.
What Krisis is not
The limits are not small print; they are the reason to trust the system. krisis.cloudwerks.de states them second, before it explains how it works.
- Not an emergency call
Krisis does not replace professional responders. It organises the people alongside them.
- Not an authority, no seal
Official warnings are cited, never badged. Krisis does not act in any authority's name.
- Not a social network
No feed, no followers, no permanent groups.
- Not a location tracker
A coarse area is stored, never an address, no continuous GPS.
- Not an advertising surface, no business model
No ads, no profiling, no third-party trackers, no data sharing.
What Krisis demonstrates technically
- Three surfaces, one build
Android (Kotlin, Compose), backend (Kotlin, Spring Boot, PostgreSQL) and web (Angular, server-side rendered) run in a single Gradle build. The API contract is the coupling point, not a shared framework.
- Crisis types are data, not code
A flood needs sandbags and pumps, a drought needs water logistics. The server defines the request types with their field schema; a new type is a configuration change, not a release.
- Privacy as a data model
Registration without e-mail, phone number or name – the account is a recovery code shown once. A coarse area instead of a location history; precise positions belong to individual events, not to the account.
- Designed for offline
Messages written without a connection are sent automatically when the network returns. Reports are stored as separate observations with their arrival path, not as a counter.