iExec documentation

Appearance

ChatGPT Ask in ChatGPT

🚀 What Is an iApp? ​

An iExec Application (iApp) is your regular application code (Python script, AI model, data processor) that can securely process protected data (created by DataProtector) inside a confidential computing environment called TEE (a Trusted Execution Environment).

Why iApps Matter? ​

iApps let you process sensitive data while keeping it private and secure.

Imagine you want to build:

🤖An AI that analyzes personal health data
📧An email tool that needs access to contact lists
💰A financial advisor that processes bank statements
🛡️A content filter that reads private messages

Users have this data, but they won't give it to your regular app. With iApps, they will.

Key Concepts ​

//TODO

✅

True Privacy: Users never expose their raw data. Your app processes it privately inside secure enclaves.

✅

Verifiable Execution: Cryptographic proof that your code ran exactly as intended. No black box execution.

✅

Decentralized Infrastructure: No single point of failure. Your app runs across a distributed network of workers.

✅

Zero Trust Architecture: Users don't need to trust you with their data. The protocol guarantees privacy.

How It Works ​

1User provides personal data
2Data is protected with DataProtector
3Protected data transferred to Trusted Execution Environment (TEE)
4Your iApp runs inside TEE and processes protected data
5Confidential computing performed while maintaining privacy

Nobody sees the raw data except your code running inside the secure enclave.

Your iApp can send emails, update contracts, make transactions, trigger notifications - anything your code needs to do with the protected data. This isn't about trust - it's about mathematical guarantees that privacy is preserved.

The Trust Model ​

Here's why users will actually use your iApp with their private data:

What Users See ​

  • ✅ "This code runs in a secure enclave, not on the developer's servers"
  • ✅ "My data gets used privately for actions I want"
  • ✅ "Even iExec workers can't see my data during execution"
  • ✅ "I can revoke access anytime"

What You Get ​

  • ✅ Users willing to use your services with their sensitive data
  • ✅ New business models around privacy-preserving analytics
  • ✅ Competitive advantage through privacy guarantees

How It Works ​

Your code runs in a Trusted Execution Environment (TEE) a secure area inside specific processors (Intel SGX/TDX chipset). Everything that happens there stays private and protected, even from the operating system.

An authorized user can trigger an iApp that processes someone's protected data inside this private environment. The data is used, but never exposed, not even to the person running the app.

1User provides personal data
2Data is protected with DataProtector
3Protected data transferred to Trusted Execution Environment (TEE)
4Your iApp runs inside TEE and processes protected data
5Confidential computing performed while maintaining privacy

Nobody sees the raw data except your code running inside the secure enclave.

Your iApp can send emails, update contracts, make transactions, trigger notifications - anything your code needs to do with the protected data. This isn't about trust - it's about mathematical guarantees that privacy is preserved.

Use Cases ​

📧

Private Communication

Users send emails, notifications, or messages using their protected contact lists without exposing recipient information.

🔮

Trustworthy Oracles

Users contribute real data to oracles while keeping their private information confidential.

🤖

Personal AI Assistants

Users let AI models perform actions based on their private data - trading, scheduling, recommendations.

⚡

Automated Actions

Users set up automated workflows that use their private data to trigger actions, transactions, or updates.

❓ Frequently Asked Questions ​

📦 What can I build with iApps?

Anything that runs in Docker! AI models, data processing scripts, web scrapers, image processing, financial calculations, etc. If it runs in a container, it can be an iApp.

⚡How fast are iApps?

Initial task scheduling takes ~30 seconds (depending on the resources the worker download, congestion etc), then your code runs at normal speed depending on complexity.

🛡️ Are iApps really secure?

Yes! Code runs in Intel SGX or TDX secure enclaves. Even the worker running your iApp can't see what's happening inside the enclave.

🚀 How do I deploy my first iApp?

Try our Hello World for a quick start, or check the iApp Generator section for detailed instructions.

🔧 What programming languages are supported?

iApps can be built in any language that runs in Docker (Python, JavaScript, R, Java, Go, etc.). However, iApp Generator currently supports only Python and Node.js for simplified development.

Start Building ​

Ready to build privacy-first applications?

🚀 Try iApp Generator ​

📖 Learn with Guides ​

🎯 See iApps in Action ​

Real iApps you can use today:

TL;DR: iApps = Your code + Secure execution + User privacy + Verifiable results. Cloud computing, but nobody can spy on your stuff. 🔒