A Rust backend service that proxies requests to NEAR AI Cloud API (using OpenAI-compatible API format) while tracking user conversations in PostgreSQL. Provides OAuth authentication (Google/GitHub), user session management, and serves a frontend as static files. Designed to run in a Trusted Execution Environment (TEE) for enhanced security and privacy.

• 🔒 TEE Execution: Runs in a Trusted Execution Environment with cryptographic attestation
• 🤖 OpenAI-Compatible API: Drop-in replacement for OpenAI API endpoints (proxies to NEAR AI Cloud API)
• 🔐 OAuth Authentication: Google and GitHub OAuth support
• 💬 Conversation Tracking: Persistent conversation management in PostgreSQL
• 📊 User Management: Session management, user settings, and analytics
• ⚡ Streaming: Real-time SSE streaming for AI responses

crates/
├── api/          # Axum HTTP server, routes, middleware, OpenAPI docs (utoipa)
├── services/     # Business logic: auth, conversation, response proxy, user management
├── database/     # PostgreSQL (tokio-postgres, deadpool), migrations, repositories
└── config/       # Environment-based configuration structs

• Repository Pattern: Database access through trait-based repositories (PostgresUserRepository, etc.)
• Service Layer: Business logic in services crate, injected into AppState
• NEAR AI Cloud API Proxy: All /v1/* routes forward to NEAR AI Cloud API with auth; conversation endpoints (/v1/conversations/*) track IDs in PostgreSQL
• Patroni Support: Optional cluster discovery for HA PostgreSQL via DATABASE_PRIMARY_APP_ID

1. Request → Auth middleware (validates session token) → Route handler
2. Conversation operations → Forward to NEAR AI Cloud API → Parse response → Track in DB
3. Generic /v1/{*path} → Forward to NEAR AI Cloud API (pass-through)

• Rust 1.90.0 (see rust-toolchain.toml)
• PostgreSQL 16+ (or use Docker Compose)
• Docker and Docker Compose
• For reproducible builds: skopeo, jq, Docker BuildKit

1. Clone and configure:

   git clone <repository-url>
   cd chat-api
   cp env.example .env
   # Edit .env with your configuration

2. Start PostgreSQL:

   docker compose up -d postgres

3. Run the server (migrations run automatically):

   cargo run --bin api

   Server starts on http://localhost:8081. Visit /docs for OpenAPI documentation.

docker compose up -d              # Start all services
docker compose up -d --build      # Rebuild and start
docker compose logs -f api        # View logs
docker compose down               # Stop services

cargo test --features test                                    # All tests
cargo test --test admin_tests --features test                # Admin tests only
cargo test --test e2e_api_tests --features test -- --ignored --nocapture # E2E tests (real API calls)

cargo fmt          # Format code
cargo clippy       # Run linter
cargo clippy --fix # Auto-fix issues

See env.example for all configuration options.

cargo build              # Debug build
cargo build --release    # Release build (output: target/release/api)

Standard build (for development):

docker build -t chat-api .

Reproducible build (for production):

./scripts/build-image.sh                              # Build
./scripts/build-image.sh --push <registry>/<tag>     # Build and push

This project implements reproducible builds to ensure bit-for-bit identical Docker images from the same source code. Critical for security, auditability, and TEE attestation verification.

Features:

• Pinned Debian package versions (via APT preferences)
• Debian snapshot archives (date: 20250411T024939Z)
• Deterministic timestamps (SOURCE_DATE_EPOCH set to git commit timestamp)
• Pinned base images (SHA256 digests, not tags)
• Locked dependencies (Cargo.lock, pnpm-lock.yaml, build-config.toml)

Verify reproducibility:

./scripts/build-image.sh
DIGEST1=$(skopeo inspect oci-archive:./oci.tar | jq -r .Digest)
rm -f oci.tar
./scripts/build-image.sh
DIGEST2=$(skopeo inspect oci-archive:./oci.tar | jq -r .Digest)
# Digests should match

Build output: OCI archive at ./oci.tar with manifest digest for verification.

This API is designed to run in a Trusted Execution Environment (TEE) (Intel TDX CVM), providing hardware-level security and cryptographic attestation.

Benefits:

• 🔒 Code integrity: Isolated, tamper-proof environment
• 🛡️ Data privacy: User data and API keys protected from host access
• ✅ Attestation: Cryptographic proofs verify execution environment
• 🔐 Confidentiality: Even cloud providers cannot access application memory

The API provides attestation reports via /v1/attestation/report:

NONCE=$(openssl rand -hex 32)
curl "https://private.near.ai/v1/attestation/report?nonce=${NONCE}&signing_algo=ecdsa"

Reports include:

• Intel TDX quotes (hardware-level proofs)
• Image digests (from reproducible builds)
• Event logs and cryptographic signatures
• Model provider attestations (end-to-end security)

• Automatic TEE detection via dstack-sdk
• VPC authentication for secure key management (set VPC_SHARED_SECRET_FILE)
• Reproducible builds required for attestation verification
• Development mode: DEV=true returns mock attestation data
• Production mode: DEV=false requires TEE execution and generates real attestation reports

Migrations are in crates/database/src/migrations/sql/ and run automatically on startup. Supports PostgreSQL and Patroni clusters (via DATABASE_PRIMARY_APP_ID).

OpenAPI docs available at /docs.

Key endpoints:

• /v1/auth/* - OAuth authentication
• /v1/conversations/* - Conversation management
• /v1/responses - OpenAI-compatible Responses API (proxied to NEAR AI Cloud API)
• /v1/attestation/report - TEE attestation reports
• /v1/users/* - User management
• /v1/admin/* - Admin operations

Note: All requests are proxied to NEAR AI Cloud API (with OpenAI compatible endpoints). Set OPENAI_BASE_URL to your NEAR AI Cloud API endpoint.

This service prioritizes privacy and data security. See CLAUDE.md for detailed logging and security guidelines.

Critical Rules:

• Never log customer conversation content, titles, or user input
• Never log security credentials (API keys, tokens, passwords)
• Only log IDs and system metrics, never user data
• All customer data must be encrypted at rest and in transit

PolyForm Strict License 1.0.0 - see LICENSE file for details.