Vercel Cost Optimization
OhChimp reads your Vercel projects and deployments to cut preview-build churn and archive stale projects, with savings verified on your real invoice.
How does OhChimp connect to Vercel?
With a read-only Vercel access token sent as a Bearer credential. OhChimp verifies it against GET /v2/user, and against your team via GET /v2/teams/{team_id} when you set a team ID. It reads project and deployment metadata only and never stores application data, secrets, or workload contents.
Does OhChimp need write access or see my code?
No. The Vercel token is used read-only to list projects and deployment activity. OhChimp reads metadata like project names, frameworks, deployment targets, and timestamps. It never reads your source, environment-variable values, secrets, or workload contents.
What Vercel costs can OhChimp actually reduce?
The build-minute and edge-request churn from projects with high preview-deployment volume, and the sprawl from stale projects (no deployment in 90+ days) that still hold domains, environment variables, and integrations. Vercel does not publish per-build dollars in its public API, so OhChimp reports the activity volumes that drive those costs and the fixes that cut them.
Who applies the changes, and can they be rolled back?
You do. Each fix is a reviewable plan with a confidence score, a risk level, and rollback steps. Nothing changes until you click apply, and you are always the one who clicks. It is never an autopilot.
How are the savings verified, and what does OhChimp cost?
Against your real Vercel invoice. A plan is marked VERIFIED only after 7 or more days, a drop of at least 10%, and 3 consecutive positive checks. Until then it stays flagged "not implemented." Pricing is flat monthly, OhChimp never takes a cut of your savings, and paid plans carry a year-one ROI guarantee: a full refund of subscription fees if it does not pay for itself in the first 12 months.