Typeroll Extensions · Production references

Three ways to build beyond the CMS

Compare a provider-owned SaaS flow, a bespoke native lead tool backed by Typeroll Forms, and an isolated iframe portal with its own backend.

Try the bespoke lead tool Open the iframe portal

Reference architectures

Choose the boundary that matches the product

All three run on the same Typeroll site. The external producer owns its runtime; Typeroll only provides the declared frontend and Forms or signed API bridges.

file-check

SaaS · native block

A recipient-specific quote. Provider API and data stay in the SaaS runtime; the token survives internal navigation.

Open quote demo →

blocks

Bespoke · native Forms

A customer-specific planner with unique JavaScript and CSS. Leads land in the ordinary Typeroll Forms inbox.

Open lead demo →

panel-top

SaaS · sandboxed iframe

A multi-screen customer portal with provider storage, signed installation API and an optional Forms support bridge.

Open portal demo →

Same native runtime

Verify the declarative HTML-mode mount

The HTML page uses an inert <x-extension> authoring reference that is replaced with the same initial state at build time.

Open HTML-mode demo Read the block-mode demo