Skip to main content

Hosted

PreviewHosted planhosted

The hosted plan adds managed delivery for Slate portals: a Release Center that promotes builds between environments and rolls them back, and four policy surfaces for the edge in front of them — Cache, Security, Edge functions and Insights. Releases and Insights are in the suite dropdown with a Preview chip; Cache, Security and Edge are reached from the authoring navigation.

PageDescription in the product
Releases"Previews, production, promotion and rollback"
Cache"Presets, expert rules, trace and scoped purge"
Security"WAF, bot and rate presets, custom rules and security events"
Edge"Functions, capabilities, egress and safe personalization"
Insights"Delivery, security and cost signals, residency and budgets"

Recorded policy​

In this preview the four policy surfaces record policy on the deployment control plane, and every one of them says, at the top of the page, that no delivery tier, runtime or collector is attached to the environment yet. What is real on each page is the policy itself, the trace or simulation of it against a sample request, the impact sheet before a change, and the audit trail. A cache purge evicts nothing, a security rule blocks nothing, a function runs nothing, and the Insights figures are modelled from policy rather than measured from traffic — each page says so.

The expert gate​

Cache rules, WAF groups and custom security rules, edge functions and their grants, and Insights' retention, residency, exports, budgets and live tail are reserved to a Platform operator role; without it the page explains what remains open ("Presets, trace and purge remain available."). No installation grants that role today, so expect the operator-only sections to be read-only.

Where the data lives​

These pages talk to the Apiome REST API's slate control plane rather than to the authoring service: releases, environments, domains, cache, security, function and insights policies, and their audit entries. When the control plane is not part of a build, each page shows a worked example derived from the catalog and says so; confirming an action then records a failed attempt rather than changing anything.