SDK
Use npm packages for fast product integration.
Zero-Key Encryption
CIFER encrypts data inside hardware-isolated TEE enclaves using ML-KEM-768, with integration paths for Web3 protocols, Web2 companies, AI agents, and encrypted workspaces.
Integration Paths
import { Cifer } from "@cifer/sdk";
const cifer = new Cifer({
network: "base",
mode: "zero-key"
});
const sealed = await cifer.encrypt({
payload: customerRecord,
policy: "post-quantum-ready"
});
await sealed.commit();Use npm packages for fast product integration.
Enterprise-friendly Web2 integration without wallets or blockchain knowledge.
Encryption primitives designed for LLM-native workflows and autonomous agents.
Direct EVM integration on Ethereum, Avalanche, and Base pathways.
Confidentiality Modes
CIFER needs to feel usable by protocol teams, enterprises, and AI-native builders. The mode split makes that decision clean.
Users authorize encryption and decryption with signatures. Commitments can settle on Base.
Best for dApps, RWA, paymentsTeams integrate with REST or npm, no wallet required, while keeping an upgrade path to on-chain commitments.
Best for SaaS and enterprise dataAI agents can encrypt and commit data without exposing raw keys to the orchestration layer.
Best for LLM-native productsWhat CIFER Encrypts
Protect documents, media, and sensitive records at rest.
Quantum-safe payment keys and private flow support.
End-to-end encrypted communication with forward-looking security.
Policy-based document protection with zero-key architecture.
Web2 Mode
Companies can integrate CIFER through standard APIs today, then add on-chain commitments later with minimal product disruption.
ML-KEM-768 is standardized in FIPS-203, not an experimental primitive.
Reduce harvest-now-decrypt-later exposure for encrypted records.
TEE-managed transitions keep application code clean.
CIFER Hub
Vault, MiniChat messaging, notes, delegated access, and cloud integrations show CIFER as a product layer, not only infrastructure.