feros
Architecture

System Architecture

End-to-end architecture across feros control-plane and voice-runtime services.

System Architecture

feros splits concerns between a Python control plane and a Rust runtime plane.

Service Boundaries

  • studio/web (:3000): dashboard UI for agents, builder, calls, integrations, settings
  • studio/api (:8000): config CRUD, builder APIs, evaluations, integrations, settings, calls APIs
  • voice/server (:8300): telephony webhooks, browser session creation, runtime session registration
  • voice/engine (embedded library in voice/server): realtime audio pipeline and provider orchestration
  • integrations (Rust library): encryption, token refresh, secret resolution, provider registry
  • Infrastructure: Postgres (required), Redis (optional for distributed OAuth state storage)

Runtime Ownership

  • studio/api and voice/server are separate processes.
  • voice/server owns live call/session execution.
  • studio/api persists control-plane state and serves dashboard APIs.

End-to-End Flow

studio/web studio/api Postgres Twilio / Telnyx voice/server voice/engine STT Provider LLM Provider TTS Provider

First Agent

Create, test, and deploy your first feros voice agent.

Runtime Architecture

Rust voice runtime execution model in `voice/engine`.

On this page

System ArchitectureService BoundariesRuntime OwnershipEnd-to-End Flow