About
SOFTWARE, NOT AN ARCHIVE.
Muns Development · Bavaria, Germany
ReportLog is the software. An archive running it is somebody else's, and the difference matters to everyone who files a report, so it is stated plainly everywhere rather than left to be worked out.
The software
ReportLog is maintained by Muns Development. The source lives at Codeberg under AGPL-3.0-or-later.
An archive
An operator runs an instance and is responsible for it: their data, their moderators, their decisions.
The separation
We do not hold any operator's reports, cannot read them, and cannot alter them. Nor can they, quietly.
Where this comes from
AboutWhy it exists
BackgroundThe first instance was built for an election incident archive, where the question every organization asked first was not what the software could do but who could change what it held. Every constraint in ReportLog is an answer to that question.
The software was pulled out of that one deployment so that anyone can run their own, for elections or anything else that needs a record people can check rather than trust.
Who makes it
PeopleBuilt by Muns Development, a one-person software practice in Bavaria, Germany. Outside contributions are wanted from the day the repository opens.
What we will not do
CommitmentNo feature that lets an operator edit or delete an entry without it showing. No auto-publish path. No release of observer identity outside the narrow, logged route it already has. If any of those ever change, it will be said plainly and loudly, not shipped quietly.
Known limitations, precisely
NoteReportLog is in development and has not been through an outside security review. The public repository is not open yet. Nothing on this site can currently be verified by reading the source.
Questions about running an instance?