Security boundary

A public demo should be isolated by design.

This page describes the required operating boundary for the pre-launch pilot—not a claim of certification, enterprise SSO, multi-tenant isolation or a contractual SLA.

Public site boundary

No product API connection

The marketing site does not require direct access to customer, quotation or administration APIs.

No contact submission backend

This static site has no intake form, submission endpoint or customer data store.

No embedded third parties

The site ships without external fonts, media CDNs or analytics scripts.

Controls required for sandbox access

Synthetic data

No real customer, personal or confidential company data is used for the general demo.

Restricted access

A session receives only the permissions required for the agreed demonstration.

Rate and cost limits

Request volume and variable-cost capabilities are bounded before exposure.

Reset and logging

The environment returns to a known state and operational events remain reviewable.

Enterprise capabilities are scoped, not assumed

Identity provider integration, tenant architecture, retention policy, regional hosting, audit requirements and service commitments must be validated during commercial discovery. They are not advertised here as delivered features.

PILOT / NEXT STEP

Evaluate the workflow with a controlled scope.

Prepare a pilot brief