piezas
better together · piezas + vercel

Vercel runs your app.
Piezas is the backend it calls.

Not a versus. Vercel is the best place to build and ship the app layer — especially now that agents write most of it. Piezas is the managed business backend underneath: the bookings, invoices, documents, and jobs your app calls over plain HTTPS. They compose without an adapter.

Vercel owns

Building and deploying your Next.js / frontend code
Preview deployments, CI/CD, edge delivery
Serverless compute for your app's own routes
The agentic toolchain that writes the app (v0, AI SDK)

Piezas owns

Business records, schemas, and tenant isolation
Bookings & availability, invoicing, forms, documents & e-signature
Background jobs, reminders, transactional email
Third-party OAuth token custody (Google, Zoom, DocuSign…)
Audit logs and the compliance posture under all of it
/ how it fits
01 · build
Generate your app with v0, Claude Code, or Cursor. UI, routes, and glue — the part agents are great at.
02 · wire
npm install @piezas/sdk. Server routes call Piezas services with PIEZAS_API_KEY (server-side only, never in the browser).
03 · deploy
Ship the app to Vercel exactly as you always do. Piezas is just HTTPS — no adapter, no plugin, no lock-in between the two.

Prefer one place for everything? Piezas also hosts apps directly (free plan: two apps, TLS, rollbacks) — a good fit for internal tools. For customer-facing products with a frontend team, Vercel + Piezas is the natural split.

When Vercel alone is enough

If your app has no business backend — a marketing site, a docs site, a pure-frontend tool — you don't need Piezas, full stop. The moment it grows records, bookings, payments-adjacent documents, or scheduled work, that logic has to live somewhere; Piezas is that somewhere, already built.

Keep your Vercel workflow. Add a real backend.
$ npm install @piezas/sdk
Start building