Defence
Provenance for code that cannot leave the building
Supply chain assurance now has an authorship problem.
Assurance frameworks ask who wrote the code and under what controls. When the answer is partly a commercial model hosted elsewhere, the question does not go away — it just becomes unanswerable. PromptWake answers it locally, with nothing leaving your network.
Nobody asks how AI-written code entered a repository until something goes wrong or somebody audits it — and by then the record either exists or it does not. PromptWake is cheap to run before you need it and impossible to reconstruct afterwards.
Questions this sector asks
Can it run air-gapped?
Yes. Local capture has no outbound dependency, and self-hosting removes the rest.
How do we prove an unapproved tool was not used?
You cannot prove a negative, and the product does not pretend to. What it shows is which tools were observed, on which machines, and which repositories had no recorder running at all.
Does it integrate with our existing audit pipeline?
Reports are produced as JSON as well as HTML and PDF, and verification returns an exit code, so both fit a pipeline without a person in the loop.
Assurance questions arrive with a deadline.
The record either exists by then or it does not. We can have you recording this week.