Welcome

Lattix is a data-centric security platform. Instead of protecting the network, servers, or applications that surround your data, Lattix embeds encryption, access policy, and tamper-evident audit directly into every data object. The data defends itself as it moves between environments, organizations, and systems.

This documentation covers what Lattix is, how it works conceptually, which products are available today, and the configuration choices you'll make as a tenant administrator.

Who this is for

• Security architects evaluating how Lattix fits into an existing zero-trust roadmap.
• Platform and IT engineers setting up a Lattix tenant, configuring identity, classification, and connectors.
• Compliance, risk, and data governance leaders looking for an architectural foundation that makes regulatory requirements enforceable at the data layer.
• Partner and coalition administrators configuring cross-organization data sharing.

What is — and isn't — in this documentation

This site covers the publicly available Lattix platform: the concepts you need to understand, the products you can use today, and the administrative controls you configure in the Mesh Dashboard.

It does not cover:

• Deployment, installation, or infrastructure operations — those live in customer-specific operational runbooks delivered with your deployment.
• API reference material — SDK reference documentation is distributed per-language with each SDK package.
• Product roadmap or pre-release capabilities — new capabilities are announced on the Insights page as they become generally available.

How to read this

If you're new to Lattix, read in order:

1. Platform Overview — the end-to-end picture: identity, policy, encryption, enforcement, and audit.
2. Core Concepts — the primitives that appear throughout the rest of the documentation: ZTDF, ABAC, the hierarchical key model, the mesh fabric, the immutable ledger.
3. Products — the product suite and what each product does.
4. Configuration — the administrative surface area a tenant actually controls.
5. Best Practices — recommendations for rolling Lattix out well the first time.

Experienced readers can jump straight to Configuration or Best Practices.

A note on scope

Lattix is a large platform and the documentation is deliberately focused. We describe what customers interact with and the architectural ideas they need to reason about the system. Internal service names, specific algorithm parameters, performance tuning, and operational internals are intentionally omitted from public documentation. If you have a production deployment and need that level of detail, it is delivered through your named support channels.