CompareUpdated Jul 13, 2026

Netlify protects site deploys. internalpage protects individual published artifacts.

Use Netlify when your team owns a static site or deploy preview and wants visitor protection around that deployment. Use internalpage when a generated file needs a stable read-only link for Google Workspace or selected-email viewers.

Start free Read docs

Netlify: visitor access for site deploys

internalpage: page audience for artifacts

Shared password, team login, or named Google identity

Different setup for different deliverables

Choose Netlify for a protected static site

Netlify Password Protection is attached to site deploys. Its current documentation distinguishes basic shared-password protection from team login protection, with SSO depending on the team and organization configuration.

Protect all deploys or preview and branch deploys
Shared password for a broad review group
Team login when reviewers are Netlify team members
Static site build, assets, routes, and deploy lifecycle

Choose internalpage for a private artifact

internalpage starts from the report or reference file rather than a site project. Publish HTML, Markdown, or OpenAPI to a slug and grant a page audience without packaging a full static deployment.

Direct file upload or CLI publishing
Google Workspace and selected-email viewing
Read-only Markdown and OpenAPI rendering
Stable URL across repeat versions

Compare visitor identities

Netlify basic protection uses a shared password. Team login uses Netlify team identities and can integrate with configured SSO. internalpage uses Google identities at the page boundary, including named viewers who do not need repository or deployment access.

Shared password: simple but transferable
Team login: tied to the Netlify team
Selected email: tied to the intended Google account
Workspace access: convenient common company audience

Compare publishing overhead

A Netlify site can carry a complete static frontend and deployment configuration. An internalpage artifact only needs a supported source file and publishing credential.

Publish a protected report artifact

npx @internalpage/cli publish ./weekly-report.html --slug reports/weekly

Know when a site host is required

Use Netlify or another static host for multi-route sites, asset folders, framework output, forms, functions, or preview deployments. Use internalpage for a finished report, reference, runbook, or review page.

A linked asset tree may require a full static host even when the entry file itself is HTML.

Decision checklist

Pick Netlify when the unit being protected is a deployed site. Pick internalpage when the unit is a generated artifact and the viewer policy should follow the page rather than the hosting project.

Static site or deploy preview: Netlify
Private single artifact: internalpage
Shared review password: Netlify basic protection
Named Google viewers: internalpage selected-email access

FAQ

Common questions

Is internalpage a replacement for Netlify?

No. Netlify hosts complete sites and application features. internalpage is narrower and optimized for private, mostly read-only artifacts.

Does internalpage use one shared password?

No. It uses Google-based page access through a workspace audience or selected viewer emails.

Which is better for a multi-page static export?

Use Netlify or another full static host for a multi-page export and asset tree. internalpage is strongest when one supported file is the deliverable.

Can I republish a report without changing the URL?

Yes. Publishing a new version to the same internalpage slug keeps the viewer destination stable.