Files
zeekay b057b28176 chore(brand): finish v2 substitution sweep — residual files
After merging chore/purge-zama-brand and chore/purge-zama-brand-v2,
applied the v2 commit's substitution map to the ~18 files those
branches missed:
  notebooks (docs/advanced_examples/*.ipynb, cifar_brevitas_finetuning/*.ipynb)
  pyproject.toml, poetry.lock
  .gitleaksignore, .github/workflows/publish_aws_ami.yaml
  .github/ISSUE_TEMPLATE/release.md, private_dictionary.txt

Substitutions (consistent with v2 commit's mapping):
  zama-ai/concrete-ml    → luxfhe/ml-sdk
  zama-ai/concrete       → luxfhe/torus
  zama-ai/tfhe-rs        → luxfhe/tfhe
  zama-ai                → luxfhe
  github.com/zama-ai     → github.com/luxfhe
  docs.zama.ai           → docs.luxfhe.com
  zama-pypi-cpu          → luxfhe-pypi-cpu
  Concrete ML            → TorusML
  concrete-ml            → torus-ml
  concrete_ml            → torus_ml
  Concrete framework     → Torus framework
  Concrete compiler      → Torus compiler
  Concrete by Zama       → Torus by Lux Industries
  tfhe-rs / TFHE-rs      → Lux-FHE
  fhEVM                  → TorusEVM
  Zama                   → Lux Industries
  Fhenix                 → (removed)

After this commit, the only "zama" string matches remaining in the
working tree (per grep -ril) are inside base64-encoded PNG image
data in notebooks — coincidental substring matches, NOT real
references. Verified 10 files × 1-2 matches each, all 0 outside b64.

Residual real work for phase 2 (NOT in this commit):
  - 89 Python files contain `from concrete.fhe import …` etc.
    These require luxfhe/torus to be a publishable Python module
    before the import statements can be safely renamed. Tracked
    in the v2 commit's roadmap.
  - deps_licenses/*.txt retain Zama upstream license text per
    BSD-3-Clause-Clear §1-§2.
  - LICENSE retains original Zama copyright per the same clause.
2026-05-29 14:07:10 -07:00
..
2025-12-27 21:08:09 -08:00

description, layout
description layout
TorusML is an open-source, privacy-preserving, machine learning framework based on Fully Homomorphic Encryption (FHE).
title description tableOfContents outline pagination
visible
true
visible
true
visible
true
visible
true
visible
false

Welcome

Get started

Learn the basics of TorusML, set it up, and make it run with ease.

What is TorusMLUnderstand the TorusML library with a full example.start1.pnggetting-started
InstallationFollow the step-by-step guide to install TorusML in your project.start2.pngpip_installing.md
Key conceptsUnderstand important cryptographic concepts to implement TorusML.start3.pngconcepts.md

Build with TorusML

Start building with TorusML by exploring its core features, discovering essential guides, and learning more with user-friendly tutorials.

FundamentalsExplore core features.build1.png
GuidesDeploy your projects.build2.png
TutorialsLearn more with tutorials.build3.png

Explore more

Access to additional resources and join the Lux Industries community.

References & Explanations

Refer to the API, review product architecture, and access additional resources for in-depth explanations while working with TorusML.

Support channels

Ask technical questions and discuss with the community. Our team of experts usually answers within 24 hours in working days.

Developers

Collaborate with us to advance the FHE spaces and drive innovation together.