LASSX documentation
Product documentation for the LASSX appliance. This public host is not a REST, GraphQL, webhook, or MCP server. Agents can read the documentation HTTP surface at /openapi.json and LASSX developer resources. Use these guides, the labeled demo, and sales@lassx.io.
- Editions & deployment
Buy the SKU that matches the buyer; run the same core — deploy once, render the edition env, ship the right doc pack.
- Identity, SSO & RBAC
Enterprise SSO plus sovereign fail-safe: federated login on a permission matrix, with audited break-glass local admins.
- Compliance & assessor evidence
Export-first and probe-backed: run the assessor pack, attach the 800-171 appendix to your SSP, treat residual CVEs as media-driven cutovers.
- Lifecycle, upgrade & day-2 ops
Artifact-first and gated: configure a source or upload media, full backup, lockout, execute with progress, then verify.
- Platform security
Prefer product controls and versioned media over ad-hoc host edits — those are supply-chain events, not harmless shortcuts.
- Data management
Ingest with policy, create with allowlisted jobs and a single binary SoT, protect with full-platform backup, exit with open portability.
- Multi-tenancy
Hierarchical and hybrid: users belong to orgs; product data hangs under workspaces; chats tighten with participants; RLS and vector filters backstop the app.
- Built-in tooling
Native tooling is product surface under policy and RBAC — not ad-hoc scripts on the chat process.
- LASSX vs Open WebUI RAG
Open WebUI teaches a local AI to read your PDFs; LASSX builds a governed knowledge program safe enough for operators who cannot outsource control.
- Chat sharing & collaboration
Collaborate in the same thread as the model — without giving every invitee the whole past.
Also: Security & trust · Live demo · llms.txt · sitemap.xml