01The record

Review risky software actions before they run.

Mullu Govern is being built to put a named approver and an evidence record between a proposed action and its execution. Built for software and operations teams.

Not open yet. Try the browser demo today, or ask whether it fits your team.

Try the demo Ask if it fits

Browser demo. Nothing to register.

Approval record · Vendor payment
  1. Request
  2. Plan
  3. Review
  4. Approve
  5. Record
  1. 09:41 Request ops@ asks to queue vendor invoice INV-2041 for payment. Owner named: finance.
  2. 09:44 Plan Proposed action: add INV-2041 to the next payment run. Limits: no execution without a named finance owner and the invoice evidence.
  3. 09:50 Review Two questions. Amount matches purchase order PO-7731. Resolved. Unresolved: vendor bank details changed on 12 Oct, confirmed?
  4. 09:51 Hold Held for approval. One question open. Nothing runs.
  5. 10:03 Approve Approved by a named finance owner. Bank change confirmed with the vendor by phone, 09:58.
  6. 10:04 Record Record written. Rollback: reverse the queue entry. Receipt MGR-2026-0142
Requester ≠ approver · evidence attached · rollback written Recorded
Fig. 1 Illustrative, unsigned record. It runs only in your browser. Read about the product
02Anatomy of the record

Five steps from a request to a record

Every entry in Fig. 1 belongs to one of these. Nothing runs between Review and Approve.

09:41 Request Someone asks for work and names the owner.
09:44 Plan The proposed action is written down with its limits.
09:50 Review A person checks the plan before anything runs.
10:03 Approve A named approver makes the decision.
10:04 Record What was asked, approved and done stays in one record.
03Fit

Who it is for

Risky operational work

Policy changes, finance actions, customer-impacting updates, deployment steps, and work that needs a named reviewer.

Evidence-heavy teams

Groups that need request context, proposed action, approval state, result, and unresolved limits in one record.

Software teams

Release, deployment, and code-change actions that need review and a record before execution.

Operations teams

Money, vendor, support, and internal process actions that need an accountable approval trail.

For the actions that must be reviewed, not every action. The team decides which.

04Check for yourself

Proof you can verify

Check the site, not a badge. No logos, no metrics. Five facts about this site, each one a click from its source.

FactValueWhere to check
Authored dependenciesSite scripts and fonts are self-hosted. Hosting can add markup; see the security page.self-hostedRead the security page
Content Security Policydefault-src 'self'; no inline styles; one hashed structured-data block.same-originSee the header response
HSTSStrict-Transport-Security with includeSubDomains and preload.with preload directiveSee the header response
security.txtContact, policy and preferred languages: en, am.publishedOpen security.txt
Last reviewedHeaders and this list were checked on that date.Open status.json

The site runs on static pages. The demo runs in your browser. These checks cover the website, not hosted-product enforcement or customer outcomes.

05Changelog and company

  1. Product and demo copy now explain unsigned local records, docs add a browser walkthrough and mobile navigation, and status pages distinguish source dates from publication evidence.

  2. Demo results are easier to find on phones, risk choices fit narrow screens, and product wording separates decisions from records.

  3. Homepage rebuilt around the review record.

Full changelog
Who makes this

Built and maintained by Tamirat Lulie Wubie.

Independent and self-funded.

Support the work →
07Next step

Try it in the browser, then talk to us

Try the demo Ask if it fits

Browser demo. Nothing to register.