The theory of change and the logframe, the same rows, shown two ways.

What Bukti is

Bukti is the Indonesian and Malay word for evidence: the proof behind a claim. It is a monitoring, evaluation and learning platform that runs on a server the program controls. OpenImpact Studio built it for programs that report to funders and want to keep their records in their own hands.

Most programs keep a theory of change in one document and a logframe in another, written at different times by different people. Within a year the two no longer match. In Bukti they are one model. Open it as a map of causes and effects, or open it as a table. The rows underneath are the same, so the two cannot drift apart.

What it does

A program can take an indicator from the SDGs, IRIS+, the OECD-DAC criteria, the Washington Group Short Set or the Core Humanitarian Standard, or write its own. Either way the indicator belongs to the program. Bukti records which framework it maps to, so when a funder asks for results in their own terms, the report comes out that way and nobody rewrites the indicator.

Sex, disability and age band are built into how Bukti stores a measurement, so a breakdown is ready when a funder asks for one. When a measurement misses its target, Bukti asks for a note on what happened. In the shipped demo program, one indicator sits at 78 per cent against an 80 per cent target, and the finding recorded against it reads as plainly as any other result in the report. Each measurement can carry its evidence, a file, a link or a Kobo submission reference, kept behind the number for anyone who wants to check it.

Who it's for

NGOs, social enterprises and government agencies running funded programs that have to report to a funder and would rather not pay a subscription for software hosted offshore, with their data outside their control. A field team records measurements against a results framework the program owns. A program lead then produces the report in one sitting, as a print-ready PDF or a formatted Excel workbook, generated straight from the records already in the system.

How it's held

Bukti runs as one ASP.NET Core binary and one SQLite file on a server the program controls. Like Kora, Suara, Selo and Aprende, it is built so the program holds its own data on its own infrastructure. The audit log records what changed in the data, never who read a report. Records are kept for as long as the program decides and deleted on the schedule it sets. There is no telemetry package, no analytics SDK and no call to an outside service while it runs.

OpenImpact Studio is tenant zero. The studio runs its own program reporting on Bukti before offering it to anyone else.

Enquire

Bukti's first release is complete and runs as OpenImpact Studio's own reporting system. There is no public instance to try yet. If your program reports to funders and wants to keep its data on its own server, tell us what you're working on and we will be in touch.