I built an AI governance layer and opened a developer preview
Most AI apps today directly call an LLM and return the response.
That is fine for demos, but production AI needs more control: policy, identity consistency, memory boundaries, traceability, and runtime governance.
So I built NEES Core Engine — a governance layer that sits between an AI app and the model provider.
Flow:
User → App → NEES Core Engine → Model Provider → Governed Response
I just opened a public developer preview repo with docs and quickstart examples:
https://github.com/NEES-Anna/nees-core-developer-preview
It includes Python, Node.js, cURL examples, API reference, governance flow docs, and templates for API key requests and developer feedback.
I’m looking for honest feedback from AI builders:
Would this be useful in your AI app?
Is the API approach clear?
Would trace IDs and governance metadata help you trust/debug AI responses?
What would you expect before using something like this in production?
This is still early, but the core engine is live and I’m using the repo to collect real builder feedback.
Would love your thoughts.
Most AI infra products stop at orchestration.
The harder layer is making model behavior auditable once AI starts touching real users, real decisions, and real risk.
That’s the right layer to build.
The product feels heavier than the name though.
NEES Core Engine explains what it is, but not what category it owns.
It reads more like an internal system name than the control layer teams build around.
If this keeps moving toward policy enforcement, traceability, and runtime governance for production AI, the naming should probably carry more infrastructure weight than “Core Engine.”
Vroth.com would fit that direction much better.