Internal tools, described, not built.
Your team says what it needs. An agent writes the tool. A person approves it. Merging ships it.
See it running →How it works
One review gate between an idea and a working tool.
Describe
Say what the tool is for, in plain words. The agent asks what it needs to know.
Build
It writes real code on a branch and opens a pull request. There is no builder to outgrow.
Approve
A person reviews it and tries it on a preview. Nothing reaches production without that.
Ship
Merging deploys it to its own address, with its own database.
Governance
Three colours instead of a policy manual.
Every tool is classed by what it can reach, not by how sensitive it sounds. A tool’s tier can be raised by review, never lowered.
Reads only. Looks things up and shows them.
Exports. Data can leave the tool.
Writes. It changes something outside itself.
Yours to run
Not a service you log into. An instance you own.
Greenlight is set up for one organisation, on its own domain, with the code in its own repository host. Your staff build their own tools inside it, and every one goes through your review.