ipinternalpage
CompareUpdated

Vercel protects deployments. internalpage publishes private artifacts.

Use Vercel Deployment Protection when the thing you operate is a preview or production web deployment. Use internalpage when the deliverable is one generated HTML, Markdown, or OpenAPI file that needs a stable private viewer URL.

Vercel: protection for deployed applications
internalpage: protection plus artifact rendering
Team membership, password, or named Google audience
Choose by runtime and viewer lifecycle

Choose Vercel for an application deployment

Vercel Deployment Protection is designed around deployments. Its documented controls include password protection and Vercel Authentication for eligible team plans, making it a natural fit for preview applications and production projects already hosted on Vercel.

  • Preview and production deployment workflows
  • Protection configured at the project or deployment layer
  • Vercel team authentication for team-bound review
  • A full frontend runtime and asset deployment

Choose internalpage for a generated file

internalpage does not require a web application project for each report. Publish a supported file, choose the audience, and keep one viewer URL while later versions replace the page.

  • HTML report, Markdown runbook, or OpenAPI spec
  • Workspace or selected-email Google access
  • No frontend build or deployment project required
  • One stable slug from local scripts or CI

Shared password and named identity solve different problems

A shared password is fast for a review group but can be forwarded and is not an individual identity. Team authentication identifies Vercel team members. internalpage instead centers page access on Google Workspace or selected Google email identities.

  • Shared password: low setup, shared accountability
  • Vercel Authentication: Vercel team boundary
  • Selected-email access: named Google viewer boundary
  • Choose the identity system your audience already uses

Compare the CI unit

A Vercel workflow deploys an application or static build. An internalpage workflow publishes the generated file itself. Both work from CI, but they leave different operational footprints.

Publish one private artifact
npx @internalpage/cli publish ./report.html --slug reviews/release

Use Vercel when the page behaves like software

Choose an application platform when you need routing, server functions, framework builds, large asset graphs, preview comments, or runtime state. internalpage is strongest for finished, mostly read-only artifacts.

A private report viewer should not be stretched into a general application host.

Decision checklist

If the review target is a deployed application, protect that deployment. If it is a generated file that people should revisit, publish the artifact behind the intended viewer identity.

  • Preview frontend application: Vercel
  • Private generated report: internalpage
  • Vercel team-only review: Vercel Authentication
  • Google Workspace or selected emails: internalpage
FAQ

Common questions

Does internalpage replace Vercel?

No. Vercel is an application deployment platform. internalpage is a narrower publishing service for private browser-viewable artifacts.

Can I protect a Vercel preview with internalpage?

Not as a reverse proxy. Publish the finished report file to internalpage, or use Vercel Deployment Protection for the deployed preview application.

Which is better for external reviewers?

It depends on identity. Vercel protection fits Vercel team or password-based review. internalpage fits named Google accounts and workspace audiences.

Can both update from CI?

Yes. Vercel deploys a build; internalpage publishes a supported file to a stable slug.