Building Nod With Vercel And Amazon Aurora PostgreSQL

Nod, an approval API for AI agents, scripts, and workflows, was built on Vercel with Amazon Aurora PostgreSQL as its database. The web app's dashboard allows teams to manage approvals, while Aurora ensures data correctness and lifecycle management for approval states. The backend uses AWS Lambda workers for notifications, callbacks, and expiration handling.

Nod is an approval API for AI agents, scripts, and workflows. The idea is simple: We built the web app on Vercel . The dashboard lets teams manage: For the database, we used Amazon Aurora PostgreSQL . Nod needs a strong relational database because approval data must be correct. An approval is not just a UI card. It has a lifecycle. php pending - approved pending - rejected pending - expired pending - canceled Aurora stores the source of truth: The backend runs on AWS with Lambda workers. One worker sends Slack notifications. Another sends signed callbacks. Another expires old approvals. A typical flow looks like this: php App or agent - Nod API - Aurora PostgreSQL - Slack or web approval - Signed callback - App continues Vercel helped us move fast on the user experience. Aurora gave us the reliable data layer needed for real approvals. Together, they helped us build Nod as infrastructure, not just a demo.