FHE-Powered Search

H33 Encrypted Search
Query Data That Never Decrypts

Search over encrypted data using fully homomorphic encryption. Build encrypted indexes, run keyword and similarity queries on ciphertext. Zero plaintext exposure at any point in the pipeline.

0
Plaintext Exposure
FHE
Powered Search
AND/OR
Boolean + Similarity
CKKS
Encrypted Indexes
Three Steps, Zero Decryption
From indexing to results, your data stays encrypted through the entire search pipeline. Not even the search server sees plaintext.
1 Index

Encrypt & Index Data

Documents and fields are encrypted with BFV or CKKS before indexing. The encrypted index is built server-side over ciphertext. Original data never appears in plaintext on the search infrastructure.

BFV Encryption CKKS Embeddings Encrypted Fields
2 Query

Encrypted Query on Encrypted Index

Your search query is encrypted client-side and sent to the server. FHE operations match the encrypted query against the encrypted index. The server computes on ciphertext without decrypting anything.

FHE Matching Encrypted Comparisons Zero Knowledge
3 Results

Matches Returned, Still Encrypted

Search results are returned as encrypted ciphertexts. Only the data owner can decrypt the matching records. The search server never learns what was queried or what matched.

Encrypted Results Client-Side Decrypt Full Privacy
API
Three Endpoints, Full Encrypted Search
Simple REST API for building, querying, and searching encrypted data. Works with any language or framework.
POST /api/search/index Build or update an encrypted search index
POST /api/search/encrypted Search encrypted data with encrypted queries
GET /api/search/query Run privacy-preserving queries with boolean operators

Features
Complete Encrypted Search Toolkit
Six capabilities that make searching encrypted data as practical as searching plaintext, without ever exposing the underlying data.
🔍

Keyword Matching

FHE-powered exact and partial keyword matching over encrypted fields. BFV integer encoding enables precise string comparisons without decryption. Supports prefix, suffix, and substring patterns.

🧠

Similarity Search (CKKS)

Run cosine similarity and nearest-neighbor searches on encrypted vector embeddings using CKKS approximate arithmetic. Ideal for semantic search over encrypted documents and records.

🔗

Boolean Queries

Combine encrypted search predicates with AND, OR, and NOT operators. Build complex multi-field queries that execute entirely in ciphertext space. Full boolean algebra on encrypted data.

📚

Encrypted Indexes

Build and maintain search indexes over encrypted data. Inverted indexes, B-trees, and hash maps all operate in ciphertext. Index updates are encrypted and never expose document contents.

🛡

Zero Exposure

Data is encrypted before it reaches the search server and stays encrypted throughout indexing, querying, and result retrieval. Not even the infrastructure operator can access plaintext.

Regulatory Compliance

Meets the technical safeguard requirements for HIPAA, GDPR, CCPA, and SOX. Search sensitive data without creating compliance exposure. Audit-ready encrypted processing logs.


Use Cases
Search Sensitive Data Without Exposure
🏥

Healthcare

Search patient records, diagnoses, and treatment histories without exposing protected health information. HIPAA-compliant queries over encrypted EHR data. Researchers can query datasets they never see in plaintext.

Legal & E-Discovery

Run e-discovery queries across encrypted document repositories. Search privileged communications without exposing attorney-client content. Keyword and pattern matching on sealed court records.

🏦

Financial Services

Search encrypted transaction logs for fraud detection, compliance checks, and audit trails. Query encrypted account records without exposing customer financial data to search infrastructure.

🕵

Intelligence & Defense

Search classified and compartmented datasets without exposing content to search operators. Encrypted queries on encrypted intelligence databases. Need-to-know enforcement at the cryptographic level.

Traditional Search vs. H33 Encrypted Search
Traditional search requires decrypting data before indexing and querying. H33 never decrypts.
Capability Traditional Search H33 Encrypted Search
Data at rest Decrypted for indexing Always encrypted
Data during search Plaintext in memory Ciphertext throughout
Query privacy Server sees queries Queries are encrypted
Result privacy Server sees results Results are encrypted
Index exposure Reveals data structure Index is encrypted
Breach exposure Full plaintext leak Ciphertext only
Compliance risk High (plaintext processing) Minimal (no exposure)
Insider threat Operators see data Operators see ciphertext

Start Searching Encrypted.

Get your API key in seconds. Build encrypted search into your application on your free tier.

Start Searching Encrypted

1,000 free units/month · BFV + CKKS · Zero plaintext exposure

Verify It Yourself