Skip to main content

Dependencies and Services

External Services​

The platform can integrate with:

  • PostgreSQL
  • Redis
  • Google Cloud Storage
  • Stripe
  • E2B
  • Anthropic, OpenAI, and Google model APIs
  • Composio
  • search and browse providers such as Tavily, SerpAPI, Firecrawl, and Jina
  • OAuth providers for sign-in

Configuration Model​

The settings layer is built from multiple focused config classes, including:

  • database
  • redis
  • storage
  • sandbox
  • Stripe
  • OAuth
  • credits
  • agent runtime
  • MCP
  • mobile
  • prompt enhancement
  • Nano Banana
  • session title settings

This matters because the env surface is intentionally broad and domain-specific.

Application Container​

ApplicationContainer is a startup-built singleton that wires together repositories and services. It gives non-request contexts such as Socket.IO handlers and workers a stable way to access domain services.

Shared Infrastructure Modules​

Storage​

  • local storage for development
  • cloud-backed storage for production
  • deterministic path resolution for user/session/project assets

Redis​

  • async client
  • caching
  • cancellation token management

PubSub​

  • topic-based async fan-out
  • Socket.IO delivery subscriber
  • database persistence subscriber

Why This Page Exists​

Without a dependency overview, contributors end up rediscovering:

  • which settings class owns a variable
  • whether a capability is local-only or provider-backed
  • where a service is supposed to be resolved from

This page is the bridge between raw env references and the code architecture pages.