Lattica Studio
lattica-studio is the control-plane client for Lattica
homomorphic workloads.
It handles model lifecycle operations:
- deploy and compile encrypted pipelines
- start and stop worker sessions
- create and manage query tokens
- coordinate first-time encrypted query setup
Encrypted inference requests are executed by lattica-query after this setup.
Requirements
- Python
>=3.11 - A valid Lattica account license key
Install
Published package:
pip install lattica-studio
Quickstart
Set your license key:
export LATTICA_LICENSE_KEY="<your-license-key>"
Run the end-to-end MNIST example:
python -m lattica_studio.example
The example in lattica_studio/example.py builds a
pipeline artifact, deploys it, starts a worker, creates a token, generates keys,
and sends encrypted queries.
Core workflow
Use this sequence in production and development:
- Deploy and compile a model pipeline.
- Start a worker session for that model.
- Create a query token (owner/admin step).
- In query clients, generate keys and upload evaluation key (EK).
- Send encrypted queries and decrypt responses client-side.
Practical iteration strategy
Worker runtime is billed while active, so keep workers up only when needed.
Recommended staged iteration:
- Stage A (pipeline changes): deploy and compile.
- Stage B (one-time per compiled context): create token, generate keys, register EK.
- Stage C (repeated queries): start worker only for query windows, then stop.
If the pipeline architecture changes, treat it as a new encrypted context: redeploy, create a fresh token, and regenerate keys.
Resource inspection helper
Use the table-printing helper to inspect account resources:
python -m lattica_studio.list_and_display models
python -m lattica_studio.list_and_display workers
python -m lattica_studio.list_and_display tokens
python -m lattica_studio.list_and_display all
list_and_display reads LATTICA_LICENSE_KEY by default, or accepts
--license-key.
More docs
License
Distributed under the Lattica Studio License: internal, non-commercial, research, or evaluation use only.
Copyright (c) LatticaAI Inc. All rights reserved.
Metadata
Release files for lattica-studio 0.15.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lattica_studio-0.15.0-py3-none-any.whl | Python 3 | none | any | Details for lattica_studio-0.15.0-py3-none-any.whl |
Release files / lattica_studio-0.15.0-py3-none-any.whl
| Download URL | lattica_studio-0.15.0-py3-none-any.whl |
|---|---|
| Size | 27.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ef8821e6706486126767fc19d106c98def5ccea6d0ea1445d8972b83443fd6f1
|
|
BLAKE2b-256 checksum How to use checksums |
3b833470f80643b976b5fd6b816aa14ce0e44e919a864650d3e2e3943d15c198
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.7.12
|
Security for lattica-studio 0.15.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.