Security and governance

The AI your security team can sign off on.

Nothing moves without a person. Nothing happens without a record. This page is written for the people who have to be sure of both.

Scroll across the city to explore the scenarios.

Governance

  • Every write action requires explicit human approval. No exceptions.
  • A preview before every approval: what changes, which records.
  • A full audit trail: who, when, what, and why.
  • Agents can’t see outside their Workspace or override a policy.
  • Every insight shows its sources: which systems, which records.

Security

  • Tenant isolation, logical and cryptographic.
  • TLS 1.2+ in transit, AES-256 at rest.
  • Role-based access, scoped by Workspace.
  • Your operational data never trains foundation models.
  • SOC 2 Type 2 certified. Report available under NDA.
In plain terms

Luceris is

  • One layer across the systems you already run
  • Agents that propose, and people who approve
  • A record of every change, written back to your system
  • SOC 2 Type 2 certified

Luceris is not

  • A replacement for your CMMS, ERP, or lease system
  • An autonomous decision engine
  • A model trained on your data
  • A dashboard
Data handling

Where your data lives, who sees it, what we never do.

Where it lives

  • Isolated per tenant, logically and cryptographically.
  • Encrypted in transit and at rest.
  • Regions on request.

Who sees it

  • People and agents see only their Workspace.
  • Roles decide who can approve.
  • Every read and write is logged.

What we never do

  • Train a foundation model on your data.
  • Act without a person’s approval.
  • Let an agent see outside its boundary.
Security architecture

Six pillars that protect your data and operations across every layer of the platform.

  • Data Isolation

    Every customer’s data is scoped to their organization on every read and write, and that scoping is enforced in code review and mechanically in CI rather than left to convention. Within each tenant, Workspaces provide an additional layer of internal segmentation, so teams and agents only reach what they should. Agent state is scoped per workspace and deleted on teardown.

    • Organization-scoped isolation on every data-access path, enforced in CI
    • Every request bound to a single organization by a verified token claim
    • Workspace-level internal segmentation for teams and agents
    • Agent state scoped per workspace and deleted on teardown
  • Encryption & Access Control

    All data is encrypted in transit using TLS 1.2+, and encrypted at rest by the managed data services we run on. Access is governed by role-based access control (RBAC) that maps to your organizational structure. Your source-system credentials are held in a dedicated secrets manager and referenced only by identifier, never inlined into application code or configuration.

    • TLS 1.2+ encryption for all data in transit, with no unencrypted protocols
    • Encryption at rest across all managed data services
    • Role-based access control (RBAC) mapped to your org structure
    • Integration credentials isolated in a secrets manager, referenced by identifier
  • AI Model Governance

    Your operational data never trains foundation models. Before any prompt reaches a model provider, personal details in it are replaced with stable tokens, and those tokens are only resolved back for authorized users in your own browser. Agents query your data through read-only, privacy-coarsened views, and every action an agent proposes must pass through human-gated approval before execution.

    • Operational data is never used to train or fine-tune any model
    • Personal details tokenized before prompts reach a model provider
    • Zero data retention enforced on our OpenAI traffic
    • Agents read through read-only, privacy-coarsened views only
    • File processing runs in isolated sandboxes with all outbound network denied
    • Agents cannot take autonomous action without approval
  • Explainability & Transparency

    Every insight an agent surfaces includes the contributing entities and source systems that informed it. Decision context is fully inspectable, so your teams can understand not just what was recommended, but why.

    • Contributing entities visible for every insight
    • Source systems identifiable for each data point
    • Decision context fully inspectable before approval
    • Confidence scoring with supporting evidence
  • Compliance Alignment

    Luceris is SOC 2 Type 2 certified. Every action and decision is traceable, events are logged in a structured form you can report against, and data-governance rules are enforced in the platform rather than documented and hoped for.

    • SOC 2 Type 2 certified
    • Full audit traceability for every action and decision
    • Structured event logging for compliance reporting
    • Data-governance rules enforced in the platform, not by policy alone
  • Operational Resilience

    The platform is built on fault-tolerant infrastructure with data versioning and recovery capabilities. Structured event logging ensures that every state change is tracked and recoverable.

    • Fault-tolerant infrastructure with redundancy
    • Data versioning and point-in-time recovery
    • Structured event logging for all operations
    • Graceful degradation under failure conditions

SOC 2 Type 2 certified.

The report, the policies, and a security questionnaire are available under NDA. Your team will usually have what it needs within a day.