Skip to main content

What you install, and how it connects

You work with Lattica through clients you install. Behind them is the platform: it compiles your pipeline, stores it, and runs it under encryption on accelerated workers. This page shows both sides and how they connect.

What you install​

Clients are packages. You install the one that matches what you want to do. There are two you will care about.

Studio

lattica-studio
For researchers and developers who build, deploy, and manage pipelines
  • Build a pipeline from HomOps
  • Deploy it and compile it
  • Create tokens, generate keys, and start workers

Query Client

lattica-query
For end-users who run queries
  • Send encrypted queries to a deployed pipeline
  • Get encrypted results back and decrypt them
Models, workers, and tokens come with Lattica Studio. You do not install them on their own. When you deploy, they are already there: studio.models, studio.workers, studio.tokens.

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
Studiomanagement is already included
Install lattica-studio at setup with your License. That package pulls in the query client. An end-user who only runs queries can install lattica-query on its own. See Installation & Setup.
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
encryptrun_querydecrypt
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 UI side of the platform. It can do the same management work a client does, create models, grant access, start and stop workers, and it adds dashboards and statistics. Two things happen only in the console.

Web Console

onboarding · billing · statistics
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).

A note on the Management Functionality​

The Lattica Studio (lattica-studio) handles deploy, account, model, token, and worker administration through studio.models, studio.workers, and studio.tokens. For the full method reference, see the platform documentation.

Next​

Start building

Build the Pipeline

Compose HomOps into a pipeline and set its parameters.

→