Storefront1 min read

Storefront — Overview

Customer-facing surface. Customize the public storefront, route a custom domain, manage customers, run support, and publish the status page. Twelve pages, three clusters.

Docs  Storefront  Overview

Storefront is the customer-facing half of Aforo. The public storefront sells your offerings; the customer portal lets buyers manage their subscriptions; the support + status surface keeps them informed. This section covers every operator screen that touches an end-customer experience — from theme tokens to incident postmortems.

What Storefront is for#

Anything a customer of your customer will see lives here. That includes the marketing pricing page, the post-purchase portal, the support ticket queue, and the public status page. Internal billing tools live in Pricing Studio; internal observability lives in Operations; this section is purely outward-facing.

Three clusters of work#

Build the surface

Customize Storefront + Domain & Routing. Theme, layout, custom pages, subdomain or vanity domain.

Serve the customer

Customers, Customer Community, Storefront Analytics, Trials & Conversion, Support Tickets, Support & SLA.

Be honest when something breaks

Service Status, Incident Manager, Scheduled Maintenance, API Status. All public-facing.

Pages in this section#

Build the surface, then serve the customer#

New tenants usually take Storefront in this order:

1

Customize Storefront

Pick a brand color, upload a logo, choose template sections (hero, pricing, FAQ), publish a draft.

2

Domain & Routing

Decide between subdomain (instant) or custom domain (DNS verification, TLS provisioning).

3

Customers + Trials & Conversion

Watch the first real signups come through; review the conversion funnel after a week.

4

Support Tickets + Support & SLA

Stand up the support queue, set SLAs, decide who is on rotation.

5

Service Status + Incident Manager

Configure monitors before you need them. The first time you need a status update should not be during an outage.

Public reliability cluster#

Service Status, Incident Manager, Scheduled Maintenance, and API Status share one public surface — the status page customers visit when something looks off. They're grouped under Storefront (not Operations) because the writing, the timing, and the tone are all customer-facing concerns. Operations owns the internal observability (Event Log, Metering Health); this cluster owns what your customer sees.

 INFO

The public status page resolves to your storefront domain by default — typically status.<your-subdomain>.aforo.ai. Custom domains pick this up automatically once DNS verification completes.

Embed Widgets — when customers want to drop pricing + checkout into their own site instead of using your storefront.
Pricing Studio → Offerings — what the storefront pricing page actually renders.
Governance → Privacy Operations — DSR queue + breach incidents that show up on the storefront /privacy page.
Operations → Alerts & Notifications — outbound customer billing alerts that hit their endpoints, not their inbox.