What is planned
Where rev-local stands today, why nothing further is scheduled, and the things it is deliberately not going to do.
Where it stands
The v1 scope is complete and closed.
Discovery, review, the engine adapters, per-engine token accounting, the publish and audit paths, a live-engine acceptance suite, the security review of the publish and secrets paths, and installer builds for macOS, Windows and Linux are all done, and the tracker holds no open work. It is not yet distributed — nothing here is downloadable today.
Planned work
Nothing new is scheduled
Rev-Local was built to a written specification and that specification is now fully implemented, down to the config keys named in its prose. There is no queued feature work, and none is being invented to fill this page. What comes next will be shaped by the first people to run it, which is a conversation rather than a release date — write if you want to be one of them.
Out of scope
Not on the roadmap
Said plainly, because the alternative is a sales conversation that ends in disappointment. If one of these is the thing you need, rev-local is not the product for it.
-
Uploading your repository
The entire premise. Rev-Local reviews code on hardware you control; a cloud path would make it a different product with a different threat model.
-
Being a CI service
It reviews changes it discovers locally. It does not host your pipeline.
-
Fixing what it finds
It reports. Applying the change is a decision with your name on it.
How this is maintained
Every item above corresponds to work tracked in our own issue tracker, and this page is rewritten from that tracker rather than kept by hand. What is not shown: unfixed defects and security work, which belong in the tracker until they are closed, not on a product page.
Want the detail behind a line on this page, or a view of where something sits? Write to dmoore@dwmmholdings.com and ask.
Next
Put rev-local in your pipeline
Ask about integrating it with the repositories and agents you already run.