Deliverd compared with Vercel
Vercel protects the deployment.
For people with a Vercel account.
Vercel is where a great deal of AI-generated front-end ends up, and its deployment protection is real: a lock screen, an allow-list, an identity provider on the top plan. Every one of those answers the question for people who work with you. The client, the auditor and the board member are the people it was not designed for.
Private by default · Unlimited viewers · No card required
Credit where it is due
What Vercel does well
Protection on every plan
Vercel Authentication puts a deployment behind a lock screen that admits people with deployment access, at no extra cost, and can cover production as well as previews.
More ways to lock it down
Password Protection on the paid plans, Trusted IPs and Passport, sign-in through your own OpenID Connect provider, on Enterprise. Requests for access can be approved, declined and revoked from the dashboard.
Sharing previews with outsiders
A Shareable Link opens a protected branch deployment for someone outside the team, and they can comment on it if they sign in with a Vercel account.
The platform underneath
Instant rollbacks, a global edge, and the deployment model everything else on this page is compared against.
The boundary
Where it stops
Deployment access is Vercel identity
The people Vercel Authentication admits are team members, project members, access-group members and Vercel users you have granted. A client's finance director has none of those, and giving her one means a Vercel account of her own, granted access by you.
The outsider's options are a password or a link
Password Protection admits anyone with the one shared password. A Shareable Link admits anyone holding the link. Neither says who opened the deployment, and neither can be revoked for one person.
Your identity provider, on Enterprise
Passport lets visitors sign in through an OpenID Connect provider such as Okta or Auth0, and it is an Enterprise feature. It is also your provider: the reader still needs an identity you control.
It protects an app, not a document
A deployment is a build of a project. The version a client approved, what changed since, and who read which one are questions about a document, and a deployment model does not carry them.
Every point above was read from Vercel's deployment protection documentation on 10 September 2026. Products change; if something here is out of date, tell us and we will correct it.
Where Deliverd fits
What you get instead
Readers who need no account
A named person, a workspace, a directory group, an email domain or a verified guest who confirms a one-time code. They sign in with their own organisation's identity provider, or verify a code sent to their email.
Their identity provider, on Team
SAML and OpenID Connect single sign-on, so a client's people authenticate with the directory they already use. It is their provider, not yours, and it is not an Enterprise feature.
Versions of a document
Publishing again updates the same address and keeps what was there. Compare two versions, roll back, pin the one the client signed off on, and readers are told when it changes.
A record of who opened it
Views, versions, access changes and share links in an audit trail you can export, retained to your policy.
Still your domain, and still your app on Vercel
Serve reports from a hostname you verify. The application stays where it is; the report it produced gets an address of its own, and the app can publish it over the REST API.
Questions.
We host our app on Vercel. Where does this fit?
Beside it. The app keeps running on Vercel; the reports it generates are published to Deliverd over the REST API or the CLI, each to an address the right client can open.
Can a report be embedded back into our app or a client's intranet?
Yes. An administrator allows the origin, and the report can be framed on a page there. It is still served and access-checked by Deliverd.
Is the report still interactive?
Yes. Scripts, styles, charts and tabs keep working. The HTML is served from an isolated origin, separate from the Deliverd control plane, and scanned before it goes live.
What about a genuinely public report?
That works too, if your organisation allows public links. The difference is that it is a decision recorded against the report rather than a property of where the deployment sits.
Everything after “generate the report”.
Free to start. No credit card.