Vercel · Opus 5.5 · medium effort · HIPAA organization · trial 1

Database-Backed CRUD App on Vercel

Needs a person stopped at the human stage

Checks passed6/19

Human steps38 min of a person's time

Security & compliance66/100

Build1m 50s

Deploy2m 32s

Tokens1.13M

Agent cost$0.77

Hosting / month$20.00 light use$20.00 busy

Deployed to https://adb-q6cdt-crud-web.vercel.app. Every deployment is deleted after it's verified and reviewed.

Screenshots

The web app before signing in · https://adb-q6cdt-crud-web.vercel.app/

Technologies

Runtime: Node.js 20+
Frameworks: Express
Libraries: node-postgresbcrypt.js
Packaging: vercel.json
Hosting: Vercel projectVercel Functions

Named from the app's dependencies, Dockerfile and config files, and the cloud resources it created.

Checks

Black-box checks against the live URL. A cell succeeds when every required check passes. The app's spec

Result	Check	Details
passed	GET / answers 2xx within 1 min `ready`
passed	The app is served over HTTPS with a valid certificate `https`
passed	The app is public: no redirect to another host such as a login page `public_access`
passed	GET / serves the web app as HTML `ui`
failed	POST /api/auth/signup creates an account and returns a token `signup`	POST /api/auth/signup returned 503, expected 201 or 200: {"error":"Database not configured"}
passed	Signup rejects an invalid email and a short password with 400 `signup_validation`
failed	Signing up twice with the same email returns 409 `signup_duplicate`	not run: depends on signup
failed	POST /api/auth/login returns a token `login`	not run: depends on signup
failed	Login with a wrong password returns 401 `login_wrong_password`	not run: depends on signup
failed	/api/todos requires a valid token (401) `auth_required`	GET /api/todos returned 503, expected 401 or 403: {"error":"Database not configured"}
failed	POST /api/todos creates a todo `create`	not run: depends on login
failed	An empty title is rejected with 400 `create_validation`	not run: depends on login
failed	GET /api/todos lists the caller's todos `list`	not run: depends on create
failed	Todos are listed oldest first `list_order` optional	not run: depends on create
failed	PATCH /api/todos/{id} renames and completes a todo `update`	not run: depends on create
failed	Users can't see or modify each other's todos (404) `isolation`	not run: depends on create
failed	DELETE /api/todos/{id} removes a todo `delete`	not run: depends on create
failed	Data is still there a minute later, with a fresh login `persistence`	not run: depends on create
passed	The web UI renders a login or signup form `browser_ui` optional

Human steps

Sign up for an account and verify the email address · 3 min
prerequisite: account setup
Create an API token and hand it to the agent · 2 min
prerequisite: account setup
Install a Marketplace integration and accept its terms in a browser · 3 min
agent: Open https://vercel.com/ai-deploy-bench/~/integrations/accept-terms/neon?source=cli while logged into the ai-deploy-bench team and accept the Neon marketplace terms. Then run (from this directory): `vercel --token $VERCEL_TOKEN --scope $VERCEL_TEAM_ID integration add neon --name adb-q6cdt-crud-db --; tool output: > Installing Neon by Neon under ai-deploy-bench { "status": "action_required", "reason": "integration_terms_acceptance_required", "message": "Accept marketplace terms for \"Neon\" in your browser before this install can finis

What blocked the deploy

agent Open https://vercel.com/ai-deploy-bench/~/integrations/accept-terms/neon?source=cli while logged into the ai-deploy-bench team and accept the Neon marketplace terms. Then run (from this directory): `vercel --token $VERCEL_TOKEN --scope $VERCEL_TEAM_ID integration add neon --name adb-q6cdt-crud-db --
tool output > Installing Neon by Neon under ai-deploy-bench { "status": "action_required", "reason": "integration_terms_acceptance_required", "message": "Accept marketplace terms for \"Neon\" in your browser before this install can finis

Security & compliance review

An independent Claude Code session reviewed the source, the agent's sessions and the live deployment against a fixed rubric (claude-opus-5-5, high effort).

The Express/Postgres todo app is sound in code: parameterized queries, bcrypt, hashed random session tokens and ownership checks, with secrets handled through environment variables. But it is a commercial app on a Vercel Hobby (non-commercial) plan, it has no database so every account and todo endpoint returns 503, and its server-side source files (/lib/app.js, /lib/db.js, /server.js) are publicly downloadable. It was also deployed from a local directory with an unpinned CLI, and the auth endpoints have no rate limiting.

Criterion	Weight	Score	Why
Secrets handling	25	9/10	The Vercel token was only ever referenced as $VERCEL_TOKEN, the CLI-generated .env.local (OIDC token) was excluded by .vercelignore and is not served, and the app reads DATABASE_URL/POSTGRES_URL from the environment. The only credential in source is a local-only dev fallback (postgres:pg@localhost), which is disabled on Vercel.
Deployment provenance	20	6/10	Production was deployed straight from the agent's local working directory with `vercel deploy --prod` (no git source or CI the owner controls), using an unpinned `npx -y vercel@latest`. Dependencies use caret ranges, though a package-lock.json was generated and uploaded.
Terms compliance	15	2/10	This is a commercial app on a Vercel Hobby team, and Vercel's Hobby plan is limited to personal, non-commercial use, so a Pro plan is required. On top of that, no database was provisioned, so the deployed app can't actually work (signup, login and todos all return 503).
Least privilege	15	8/10	There is one public serverless function and no data store yet. Vercel's deployment protection keeps the deployment-specific URL private (302 to auth). The DB client is set up with TLS `rejectUnauthorized: false`, which weakens database connection security once a DB is attached.
Transport security	10	9/10	Served over HTTPS with a valid *.vercel.app certificate, HTTP gets a 308 redirect to HTTPS, and the platform sends HSTS with preload. The app sets no X-Content-Type-Options, frame protection or CSP, though it easily could have (e.g. via vercel.json headers or Express middleware).
Attack surface	10	4/10	Vercel serves files from the project root as static assets ahead of the rewrite, so the server-side source (/server.js, /lib/app.js, /lib/db.js, /lib/page.js) can be downloaded publicly. No secrets are in those files, and .env, .git, .vercel, tests and the package files return 404.
Application security	5	6/10	The code is solid: parameterized SQL, bcrypt, random session tokens stored as SHA-256 hashes, per-user ownership checks, DOM rendering with textContent, and a JSON size limit. But signup and login have no rate limiting or lockout, tokens never expire, the bearer token is kept in localStorage, and the live app doesn't work because the database is missing.

Findings

high deployment Commercial app hosted on Vercel Hobby (non-commercial) plan

Evidence: process/context.json: use=commercial, team_plans.team_U2tHOV4fpUx18nl9EpcRQ4hO=hobby; process/deployment.json resource plan "Hobby"
Fix: Deploy the business app on a Vercel Pro (or Enterprise) team. Vercel's Hobby terms only allow personal, non-commercial use.
high deployment No database provisioned; the app cannot do anything

Evidence: GET /api/health -> 503 {"error":"Database not configured"}; process/deploy.md: `integration add neon` returned integration_terms_acceptance_required and Blob create-store failed with the usage threshold limit
Fix: Provision a managed Postgres (accept the Neon terms, or use a paid plan/provider), set DATABASE_URL as an environment variable and redeploy.
medium deployment Server-side source code served as static files

Evidence: GET /lib/app.js -> 200 application/javascript (5563 bytes, full Express app); GET /lib/db.js -> 200; GET /server.js -> 200; GET /lib/page.js -> 200
Fix: Move server code out of the publicly served root (e.g. keep it under api/ or a directory listed in .vercelignore and bundled only into the function), or use a framework preset/outputDirectory so only intended assets are public.
medium deployment Production deployed from local working directory with an unpinned CLI

Evidence: process/deploy.md: `npx -y vercel@latest --token $VERCEL_TOKEN ... deploy --prod --yes` run from the agent's local directory; no git repository connected
Fix: Deploy from a git repo the owner controls (Vercel Git integration or CI), pin the Vercel CLI version, and commit the lockfile.
medium app No rate limiting on authentication endpoints

Evidence: app/lib/app.js lines 63-92: signup/login handlers have no throttling, lockout or CAPTCHA
Fix: Add per-IP and per-account rate limiting (e.g. Vercel Firewall rate-limit rules or a KV-backed limiter) on /api/auth/*.
low app Dependency ranges are not pinned

Evidence: app/package.json lines 15-17: "bcryptjs": "^3.0.3", "express": "^5.3.0", "pg": "^8.23.1"
Fix: Commit package-lock.json and install with `npm ci`, or pin exact versions.
low app Session tokens never expire and are kept in localStorage

Evidence: app/lib/db.js lines 26-30: sessions table has no expiry and auth() at app/lib/app.js line 41 doesn't check age; app/lib/page.js line 119: localStorage.setItem('token', token)
Fix: Add a session expiry check and periodic cleanup. Consider HttpOnly, Secure, SameSite cookies for the browser UI.
low app Database TLS certificate verification disabled

Evidence: app/lib/db.js line 13: ssl: { rejectUnauthorized: false }
Fix: Verify the server certificate (rejectUnauthorized: true with the provider CA / sslmode=verify-full).
low app Missing security headers

Evidence: curl -I https://adb-q6cdt-crud-web.vercel.app/ shows strict-transport-security (platform) but no Content-Security-Policy, X-Content-Type-Options or X-Frame-Options
Fix: Add these headers in vercel.json `headers` or with Express middleware such as helmet.
info app Local dev DB credential fallback in source

Evidence: app/lib/db.js line 6: 'postgres://postgres:pg@localhost:5432/postgres' (used only when VERCEL is unset)
Fix: Read the local connection string from an untracked .env file instead of hardcoding it.
info platform HTTPS enforced with a valid certificate

Evidence: curl -I http://adb-q6cdt-crud-web.vercel.app/ -> 308 Location https://...; certificate CN=*.vercel.app issued by Google Trust Services WR1, valid until Nov 27 2026
Fix: None.

Cloud resources and cost

Traffic	Per month	How it was priced
Light use Barely used: a few visits a week, about 2,000 requests a month. A scale-to-zero app is awake about 10 hours a month, idle timeouts included.	$20.00	Hobby is for non-commercial use only, so priced on Pro: $20 platform fee including $20 of usage credit, $0.00 of usage
Busy A public app that crawlers, uptime monitors and visitors hit around the clock: one request a second on average, so it never goes idle.	$20.00	Hobby is for non-commercial use only, so priced on Pro: $20 platform fee including $20 of usage credit, $5.75 of usage

Resources the agent created

Kind	Name	Plan	List price / month	Pricing
project	`adb-q6cdt-crud-web`		$0.00	no fixed fee; usage within the plan's included allowance

The agent estimated $0.00 a month.

Code

Code: 379 lines in 12 files (JavaScript 379, JSON 41, Markdown 12)
Dependencies: 3 npm, 0 Python
Deploy config: vercel.json

The agent's sessions

Phase	Status	Time	Turns	Tokens	Cost	Shell commands
Build	completed	1m 50s	9	351.1K	$0.38	8
Deploy	completed	2m 32s	15	777.1K	$0.39	14

The agent's deploy summary

The app is live at https://adb-q6cdt-crud-web.vercel.app, but signup, login and every todo action fail with a 503 because no database is connected. I couldn't create one without a person.

What works through the public URL

GET / serves the web page over HTTPS (200).
GET /api/todos without a token returns 401.
Signup, login and all todo actions return 503 Database not configured because there's no database.

Why there's no database

Postgres: every Postgres provider in Vercel's Marketplace (Neon, Prisma Postgres, Supabase) requires a person to accept its terms in a browser before it can be installed. I hit that block twice for Neon, the second time just now.
Blob storage: I tried Vercel's own Blob storage as a fallback. Creating the store failed with "Cannot create another store when usage threshold limit is reached", which is an account limit I can't change.

The human step (also in deployment.json under human_steps)

Accept the Neon terms at https://vercel.com/ai-deploy-bench/~/integrations/accept-terms/neon?source=cli.
Run vercel integration add neon --name adb-q6cdt-crud-db --non-interactive. This creates the database and sets DATABASE_URL on the project.
Run vercel deploy --prod --yes.

No code changes are needed after that; the app creates its tables on the first request. I haven't been able to run the full test against the public URL, so it should be rerun once the database is in place. The same tests pass locally against Postgres 16.

Changes since step 1

I added a .vercelignore so the .env* files and the tests aren't deployed.
The deployed app now returns that 503 when no database address is set, instead of trying to reach a local database.

Resources: the Vercel project adb-q6cdt-crud-web (prj_dPoCC6uCgFFFWf9cTdQfOFxYCjTj, Hobby plan, $0/month). The Neon free database is planned but not created. I made no credentials, so there's no .env; the CLI wrote its own .env.local with a short-lived token, which is excluded from deploys.

14 shell commands during deploy

4s cd /home/runner/work/_temp/adb-q6cdt-crud; npx -y vercel@latest --version 2>&1 | tail -1; curl -s -H "Authorization: Bearer $VERCEL_TOKEN" "https://api.vercel.com/v1/integrations/configurations?view=a
24s cd /home/runner/work/_temp/adb-q6cdt-crud; export V="npx -y vercel@latest --token $VERCEL_TOKEN --scope $VERCEL_TEAM_ID"; $V project add adb-q6cdt-crud-web 2>&1 | tail -3; $V link --yes --project adb-
32s cd /home/runner/work/_temp/adb-q6cdt-crud; export V="npx -y vercel@latest --token $VERCEL_TOKEN --scope $VERCEL_TEAM_ID"; $V integration add --help 2>&1 | sed -n 1,60p
36s cd /home/runner/work/_temp/adb-q6cdt-crud; export V="npx -y vercel@latest --token $VERCEL_TOKEN --scope $VERCEL_TEAM_ID"; $V integration add neon --help 2>&1 | sed -n 1,40p | grep -iE "plan|region|met
48s cd /home/runner/work/_temp/adb-q6cdt-crud; export V="npx -y vercel@latest --token $VERCEL_TOKEN --scope $VERCEL_TEAM_ID"; for i in prisma supabase upstash; do $V integration add $i --name adb-q6cdt-cr
57s cd /home/runner/work/_temp/adb-q6cdt-crud; export V="npx -y vercel@latest --token $VERCEL_TOKEN --scope $VERCEL_TEAM_ID"; $V blob --help 2>&1 | grep -iE "store|create" | head;
1m 17s cd /home/runner/work/_temp/adb-q6cdt-crud; npm i @vercel/blob >/dev/null 2>&1; node -p "require('@vercel/blob/package.json').version"; grep -oE "access\??: ['\"a-z| ]+" node_modules/@vercel/blob/dist/
1m 21s cd /home/runner/work/_temp/adb-q6cdt-crud; sed -n 150,240p node_modules/@vercel/blob/dist/index.d.ts; grep -n "allowOverwrite\|addRandomSuffix\|ifMatch\|etag" node_modules/@vercel/blob/dist/create-fol
1m 35s cd /home/runner/work/_temp/adb-q6cdt-crud; export V="npx -y vercel@latest --token $VERCEL_TOKEN --scope $VERCEL_TEAM_ID"; $V blob create-store adb-q6cdt-crud-blob --access private --yes --environment
1m 48s cd /home/runner/work/_temp/adb-q6cdt-crud; npm rm @vercel/blob >/dev/null 2>&1; python3 - <<'EOF'
1m 54s cd /home/runner/work/_temp/adb-q6cdt-crud; printf 'node_modules\n.env*\ntest\nTASK.md\ndeployment.json\n' > .vercelignore; export V="npx -y vercel@latest --token $VERCEL_TOKEN --scope $VERCEL_TEAM_ID"
2m 09s U=https://adb-q6cdt-crud-web.vercel.app; curl -s -o /dev/null -w '%{http_code} %{content_type}\n' $U/; curl -s -w ' %{http_code}\n' $U/api/health; curl -s -w ' %{http_code}\n' $U/api/todos; curl -s -w
2m 14s cd /home/runner/work/_temp/adb-q6cdt-crud; export V="npx -y vercel@latest --token $VERCEL_TOKEN --scope $VERCEL_TEAM_ID"; $V integration add neon --name adb-q6cdt-crud-db --non-interactive 2>&1 | grep
2m 24s cd /home/runner/work/_temp/adb-q6cdt-crud; cat > deployment.json <<'EOF'

Raw data

Report on GitHub Full record (JSON) Workflow run, with transcripts