Confidential AI
Train and run AI.
Keep your data private.
Run training and inference in confidential hardware that protects your data and models while they’re in use. Verify the software and control what it can share.
Docker deployments
Run your container in confidential hardware.
Use your own application or a vendor’s Docker container. Verify the code and control which services it can connect to.
- 01
Choose your software.
Select an exact Docker image version, the data it needs, and the services it can reach.
- 02
Approve changes on-chain.
Changing the code or permitted connections requires a new release and on-chain approval.
- 03
Check before connecting.
Use hardware attestation to confirm that the running software matches an approved release.
Training & inference
Keep data private
while models use it.
Training & fine-tuning
Keep datasets and model weights inside the confidential runtime during training. Decide who can receive the trained model.
Inference
Process prompts and private context inside confidential hardware. Control where responses go and what gets retained.
Connections & data controls
Decide what gets in.
And what gets out.
Connect to accounts, tools, and services without giving the application unrestricted network access.
Accounts & credentials
Connect private databases, business accounts, and MCP tools using credentials stored in the confidential runtime.
Network access
A network proxy checks outbound connections against the list of services you allow.
Responses & logs
Your code determines what the application sends or saves. Review it alongside the network rules.
Working with Lit
Tell us what
you want to run.
Share your model, the data it needs, and your performance goals. We’ll help you choose suitable hardware and plan the deployment.
Contact for Lit AICommon questions.
What if my application calls an external model?
What can I verify?
Which models and hardware are supported?
Can I start from the crypto dashboard?
Compare private compute
Build with Lit