---
# System prepended metadata

title: DStack Overview @ SF Pi-rateship Mar 21st

---

# DStack Overview @ SF Pi-rateship Mar 21st

## Overview

Script: https://otter.ai/u/DZuLReLRmEGSAohr1C_sz-T2XsA?utm_source=copy_url

![photo_2025-03-24_02-23-25](https://hackmd.io/_uploads/ryQoVsRnJl.jpg)


DStack is a confidential computing platform that uses Trusted Execution Environments (TEEs) to enable secure, privacy-preserving computation with strong trust guarantees. It allows developers to run applications in secure containers while minimizing trust in administrators and operators.

## Architecture Components

### Core Components

1. **Confidential Virtual Machines (CVMs)** 
   - Isolated execution environments using TEE technology
   - Each CVM runs containerized applications
   - Isolation model supports container-level or VM-level security boundaries

2. **DStack Gateway**
   - Serves as interface between external clients and confidential workloads
   - Handles TLS termination with standard certificates for browser compatibility
   - Multiple gateways can be deployed for redundancy using a mesh topology
   - Planned for upgrade to Gateway v2 with SNI support and custom domain handling

3. **On-chain Key Management System (KMS)**
   - Manages encryption keys and security policies for applications
   - Enables programmable governance for application upgrades
   - Allows for "community takeover" of abandoned applications
   - Policies and attestation records stored on blockchain for transparency

4. **VPN Mesh**
   - Internal secure communication between components
   - Based on "wireguard" technology
   - Ensures authenticated connections between CVMs and gateways

## Security Model

### Trust Minimization

DStack's key differentiator is its "trust-minimized confidential containers" approach:

1. **No Admin Trust**
   - Unlike traditional confidential computing solutions, DStack doesn't require trusting the admin
   - Infrastructure operators cannot access or manipulate application data
   - Security enforced through TEE attestation and on-chain governance

2. **Two-by-Two Security Model**
   - Handles four scenarios based on the trustworthiness of Certificate Authorities (CAs) and developers
   - Provides graceful degradation of security properties under different threat models
   - Leverages certificate transparency for additional security verification

3. **Remote Attestation**
   - Applications can verify the authenticity of the DStack environment
   - Chain of attestations from hardware through software stack
   - For multi-component applications, supports "mega attestation" to verify full system integrity

### Secure Communication

1. **Gateway TLS Handling**
   - Uses wildcard certificates for domain endpoints (e.g., *.dstack.fala)
   - Handles browser connections with standard TLS
   - Internal connections secured via VPN
   - Certificate transparency used to verify legitimacy of certificates

2. **Custom Domains**
   - Support for customer-provided domains with Cloudflare integration
   - Security verification of domain ownership through DNS records
   - Certificate transparency checking for domain history

## Features and Capabilities

### Containerization and Deployment

1. **Docker Support**
   - Applications packaged as Docker containers
   - Support for Docker-in-Docker for advanced use cases
   - GitHub integration for automated deployment from repositories

2. **Multi-GPU Support**
   - Integration with NVIDIA attestation for secure GPU usage
   - Plans for distributed GPU training support
   - Recent updates to support multiple GPUs within a single CVM

3. **Load Balancing**
   - Multiple instances of the same application can be deployed across machines
   - Redundancy for high availability
   - Plans for more sophisticated routing capabilities

### State Management

1. **Storage Options**
   - Encrypted volume support for persistent data
   - Plans for distributed database support
   - Consideration of TiDB, ZooKeeper, and other strongly consistent databases

2. **State Sharing**
   - Challenges with consistent state across distributed nodes
   - Discussion of consensus mechanisms (Raft vs. BFT)
   - Potential for integrating with Data Availability (DA) protocols

### Governance Features

1. **Community Takeover Mechanisms**
   - Applications can be configured for community governance if developers abandon them
   - Payment for services can come from any source, not just the original developer
   - Enables long-term sustainability of services (e.g., gaming servers)

2. **Open Source Policies**
   - Support for crowdfunding to "unlock" proprietary code
   - Options for staged openness from proprietary to community-governed
   - Plans for establishing standards for security and governance

## Development Roadmap

### Prioritized Features

1. **On-chain KMS** - For decentralized governance of applications
2. **Gateway v2** - SNI support, redundancy, custom domains
3. **GPU Support** - Integrating with NVIDIA's attestation for multi-GPU configurations
4. **Distributed Database** - For consistent state management
5. **Load Balancing** - Supporting multiple application instances

### Integration Goals

1. **CICD Pipeline** - GitHub integration for automated deployment
2. **Standards Development** - Creating security baselines for applications
3. **Audit Planning** - Working with external security auditors (mentioned NCC Group, Trail of Bits, Least Authority)

## Use Cases

1. **Gaming Servers** - Minecraft and other multiplayer games that benefit from community takeover capabilities
2. **Personal Data Agents** - Digital twins with access to sensitive personal data
3. **Distributed VercelA** - Serverless functions with privacy guarantees
4. **Zero-Knowledge Provers** - Offloading cryptographic computations to secure environments

## Technical Challenges

1. **Network Latency** - Plans for globally distributed TEE instances
2. **Consensus Security** - Addressing limitations of distributed consensus (e.g., Raft's vulnerability to network partitioning)
3. **Record-Level Key Rotation** - For granular data protection in databases
4. **Upgrade Security** - Balancing agility with security for system components

## Development Philosophy

DStack aims to provide a platform where:
1. Services are composable and extensible
2. Developers can build with reduced trust requirements
3. Users have guarantees of service continuity
4. Sensitive computations remain private and verifiable
5. Application stack is compatible with existing web infrastructure

The platform draws inspiration from both Web2 cloud architecture (e.g., GCP, AWS) and Web3 governance models to create a hybrid system that provides the best of both worlds.

---
Context of the Session
