AI apps will touch more sensitive data in the next two years than every enterprise SaaS of the last decade.
Frontier models aren't going to solve this — it's architecturally opposed to their interests.
Four cryptographic guarantees. Each independent. All running together.
No username, no email, no password to compromise. Users authenticate via Face ID or Touch ID through WebAuthn. Krava hashes credentials through a one-way function — the result is stored, but cannot be reversed to reveal an identity. Krava is architecturally incapable of exposing who you are.
AES-256-GCM encryption across every piece of user data — memory, chat history, and identity. Data is encrypted client-side before it ever reaches a database, using a key held only by the user. Persistent encrypted storage across sessions means no one — including Krava — can read what's stored.
For sensitive workloads, inference runs inside NVIDIA H100/H200 Trusted Execution Environments (TEEs). The GPU operator is architecturally incapable of reading data in memory during processing. SOC 2 Type II certified. Cryptographically verifiable — not just auditable.
Route to Anthropic, OpenAI, Fireworks, or self-hosted models based on task sensitivity, cost, and capability. Sensitive tasks route to Tinfoil TEE; general tasks use commercial APIs. Never locked to a single provider — maximize security, minimize cost and token usage.
One install. Encrypted memory, passkey identity, zero-retention inference — all running in your product by end of day.
Provision a user, get back an encrypted token. That's the entire integration surface. Encrypted memory, passkey identity, and zero-retention inference are all underneath.
import { createPrivyClient } from '@krava/sdk'
const krava = createPrivyClient({
appKey: process.env.KRAVA_APP_KEY
})
// Provision a user — returns an encrypted userToken
const { userToken } = await krava.provisionUser({
externalUserId: user.id
})
// Done. Encrypted memory, passkey auth,
// and zero-retention inference — all live.
Krava ships a Lovable starter template — a pre-wired project with the SDK installed, a working passkey login, and encrypted memory ready to go. Fork it, build on it.
View Lovable Starter Template →No backend required · Works with Lovable's default Supabase setup
Open the Krava Lovable template and click Fork. Everything is pre-configured — SDK, auth, memory.
Set KRAVA_APP_KEY in your Lovable environment variables. Get your key at krava.io.
Prompt Lovable as normal. Passkey login and encrypted memory are already wired up — just ship the feature you actually care about.
Your users' data is encrypted before it hits any database. You can say it — and prove it.
Real products. Paying users. Running on the same SDK.
The private AI coach for senior leaders.
A coaching product for executives and founders working through sensitive decisions — board dynamics, layoffs, fundraising — where every other AI product fails the privacy bar. Passkey login, encrypted memory, TEE inference.
Visit Privy Coach →stack: passkey_auth · aes-256-gcm · tinfoil_tee
A private autonomous AI agent.
An autonomous AI assistant capable of multi-step work — research, drafting, inbox triage, meeting prep — where the user holds the keys to everything the agent knows about them. Each user gets their own containerized runtime.
Learn more →stack: openclaw_runtime · runpod · tinfoil_tee
Private AI for iMessage.
An iMessage-native AI assistant built on Krava's privacy infrastructure. Your conversations stay yours — not stored, not used for training, not visible to anyone but you.
Learn more →stack: imessage · krava_sdk · zero-retention
The SDK is MIT licensed and free to self-host. Hosted pricing — per call, per memory item, per agent pod-hour — is being finalized. Early builders get preferred rates.
Get API Key →