Skip to main content

What you install, and how it connects

Lattica includes client packages that connect to the Lattica Platform. The clients are used to build, deploy, manage, and query pipelines. The platform compiles and stores deployed pipelines, manages the resources required to run them, and coordinates encrypted execution on workers.

What you install​

Clients are separate packages. They can be installed in the same environment or in different environments, depending on the user's role and responsibilities.

Studio

lattica-studio
For researchers and developers who build, deploy, and manage pipelines
  • Build a pipeline from HomOps
  • Deploy and compile it
  • Manage deployed pipelines
  • Create and manage access tokens
  • Manage workers for encrypted queries

Query Client

lattica-query
For end-users who run queries
  • Create the secret key and evaluation key
  • Register the evaluation key with the Lattica Platform
  • Encrypt input locally
  • Send encrypted queries to a deployed pipeline
  • Receive encrypted results and decrypt them locally

Who installs what​

Lattica Studio and the Query Client can sit in one environment or two. Pick by role.
Researcherbuild and test in one place
Studio+Queryboth in the same environment
End-useronly runs queries
Queryon its own, can be a separate machine
Studiobuilds, deploys, and manages
StudioManage pipelines, access tokens, and workers, without running encrypted queries.
For research and testing, both live in one environment. That is the setup these docs assume unless noted.

How it connects​

Here is the same picture as a system. Clients hold credentials and talk to the platform. The platform runs your pipeline on workers. Your data stays encrypted.
Clients you run
Lattica Studio
holds License
builddeploymanage
containsmanagement · models, workers, tokens
Query Client
holds Access token
encryptquery.encrypteddecrypt
deploy pipeline
encrypted query
Platform infrastructure
Workloads
your compiled pipelines, stored
Workers
run the pipeline body on ciphertext
Licenseoperator credential · build and deploy
Access tokenper-deployment · run queries
In a researcher setup, both clients run on your machine, so deploy and query happen from the same place. In production, the Query Client can live wherever your end-users are.

The web console​

The console is the browser interface for managing the Lattica account and platform resources.

Web Console

onboarding · billing · statistics
It can be used for

  • Account and access management

  • Pipeline and resource management

  • Worker management

  • Credits and billing

  • Usage and statistics

Lattica console Models page, with credits, worker volume, and existing models
Two things happen only in console:
Console only
Get your License

Sign up, log in, and take your License. You need it before you install any client. Guide

Console only
Add credits

Worker time is paid in credits, bought here. Pricing

Everything else the console does, you can also do from a client. The console is the place you start (get a License) and the place you pay (add credits).

Next​

Start building

Build the Pipeline

Compose HomOps into a pipeline and set its parameters.

→