Security architecture

Separate the public edge from powerful local tools.

The Builder Admin API remains loopback-only. Commerce runs as a separate service with hardened SQLite/WAL storage, verified webhooks, replay-resistant installation requests, and auditable grants.

Payment boundary

Hosted product checkout prevents card data from entering Reallexi Pages. Raw webhook signatures are verified and events are processed idempotently. Product checkout is not an investment-closing system; strategic capital follows the separate legal-readiness path described on the funding page.

Model and token custody

Model files, datasets, prompts, and Hugging Face tokens remain local. Introspection includes only installation identity and requested capability.

Account and operator access

Passwordless links are short-lived and single-use. Privileged mutations require a server-approved operator, CSRF protection, a specific reason, and an immutable audit record.