NEES Core V3 — Governance Platform
Govern AI agent actions with a free developer workspace
Start new thread

NEES Core V2 Developer Preview - Govern AI agents before supported actions execute

by•
NEES Core V2 has evolved from response governance into a broader runtime governance system for AI agents. This launch introduces the Python SDK developer preview, Governance Lab, controlled API access, and broader support for authority, scope, approvals, requalification, evidence, and bounded governed actions.

Add a comment

Replies

Best
Maker
📌
Hi Product Hunt 👋 I’m Piyush, founder of Nainacore Emotional Tech. The first version of NEES focused mainly on governing AI behavior before a model response. Since then, the system has evolved significantly. NEES Core V2 is now designed around a broader question: If an AI system can take action, where does its authority stop? The Core now includes supported mechanisms around authority and delegation, resource scope, approvals, state-aware requalification, execution qualification, evidence lineage, and bounded governed action execution. With this launch, we’re also opening the first direct developer entry point through the NEES Python SDK, while the Governance Lab gives a broader public view of selected governed behavior and linked evidence. The SDK is intentionally narrow today. I’d rather expose stable public contracts gradually than turn every internal capability into an API before it is ready. I’d especially love feedback from developers building agents or workflow automation: What governance capability would you want exposed next — action authorization, approvals, evidence lookup, or authority/scope?
Vercel
Vercel Day
Which Vercel product did you use? What new capability did it give your team, and how did that shape the product you launched?
Maker
We use Vercel for our Next.js web platform and server-side routes powering nees.cloud, including the public Governance Lab, developer-facing pages, and our developer access workflow. Vercel gave us the ability to ship product and documentation changes quickly while keeping the public experience and backend-facing web flows in one deployment workflow. That mattered while NEES was evolving rapidly: we could move from internal governance work to a live Governance Lab, Python SDK onboarding, and request-access flow without building a separate web infrastructure stack. It shaped this launch by letting us focus our engineering effort on the NEES governance runtime itself while still presenting developers with a polished, continuously updated public product experience.