Governed Quickpages

Publish fast. Control access. Measure every page.

Quickpage gives publishers the controls they need to share pages confidently and see what happens after launch.

Compare access tiers quickpage deploy ./site launch "Launch" --access dac --root

Security controls built for everyday publishing.

Governance is part of the publishing path, not a separate maze. Choose access, add controls when needed, and keep runtime secrets out of page content.

Public

Use public pages for broad campaigns, announcements, and pages meant to be easy to share.

Unlisted

Use unlisted pages for targeted sharing when the URL should work but the page should stay out of anonymous indexes.

DAC access

Use DAC-only pages when the audience belongs behind organizational access through Easy Auth.

Runtime-safe publishing

Controls that match the page.

Use passwords for limited previews, expiry dates for time-boxed campaigns, and view limits when access should be intentionally constrained.

Quickpage governed publishing flow with tokens, Key Vault, and analytics

Publisher tokens

Controlled publishing flows can use shared admin tokens or scoped publisher tokens for user-prefixed pages.

Key Vault secrets

Runtime secrets belong in Key Vault, not in the page. Campaigns can connect to approved services without exposing credentials.

Built-in analytics

Quickpage analytics endpoints help teams track traffic, compare page performance, and make follow-up decisions with first-party data.

A repeatable path from publisher to insight.

Access tiers, publisher tokens, runtime secrets, page limits, and analytics all live in one service.

Publisher tokenAuthenticates the publish action.
Page controlsPassword, expiry, and view-limit options.
Key VaultStores runtime secrets outside the page.
Quickpage URLServes the page under the selected access tier.
AnalyticsReports page activity after launch.