# Telnyx Compute: Stateful Actors (Beta) — Documentation Index
> Stateful Actors (Beta) documentation within the Compute section of the Telnyx developer docs (https://developers.telnyx.com).
> This file: https://developers.telnyx.com/docs/development/llms/compute-stateful-actors-beta-llms-txt · Root index: https://developers.telnyx.com/llms.txt

## Overview

- [Stateful Actors](https://developers.telnyx.com/docs/edge-compute/stateful-actors.md): A stateful actor is a single-threaded server owning one entity's state: one instance per name, calls routed to it, methods run one at a time, writes persisted.

## Get Started

- [Stateful Actors Quick Start](https://developers.telnyx.com/docs/edge-compute/stateful-actors/quick-start.md): Scaffold an Account Stateful Actor, deploy it, and prove per-account isolation, safe concurrent debits, and persistence.

## Concepts

- [How It Works](https://developers.telnyx.com/docs/edge-compute/stateful-actors/concepts/how-it-works.md): Derive the stateful actor execution model from first principles, then map each mechanism — per-entity lock, flush-before-ack storage — to what you'd build in C.
- [Execution Model](https://developers.telnyx.com/docs/edge-compute/stateful-actors/concepts/execution-model.md): The four guarantees a stateful actor's runtime makes: one instance per name, one call at a time, writes durable before reply, and only persisted state survives.
- [Lifecycle & Placement](https://developers.telnyx.com/docs/edge-compute/stateful-actors/concepts/lifecycle.md): Where a stateful actor instance runs, when it activates and evicts, and what survives restart: placed on first touch, evicted when idle, only storage persists.
- [Addressing](https://developers.telnyx.com/docs/edge-compute/stateful-actors/concepts/addressing.md): Reach a Stateful Actor instance by name. idFromName is deterministic; newUniqueId mints a fresh one. Both return a stub you call methods on.

## Reference

- [Overview](https://developers.telnyx.com/docs/edge-compute/stateful-actors/api-reference.md): The Stateful Actor API surface: StatefulActor, ActorContext, per-instance storage, the ActorNamespace and ActorStub bindings, alarms, configuration, and errors.
- [Base Class](https://developers.telnyx.com/docs/edge-compute/stateful-actors/api-reference/base.md): The StatefulActor base class — subclass it, declare async methods, and they become RPC-callable from a stub. Holds this.ctx and this.env.
- [Actor Context](https://developers.telnyx.com/docs/edge-compute/stateful-actors/api-reference/context.md): The this.ctx object on a StatefulActor — the instance's identity, per-key storage, single alarm, one-shot init, and its live WebSockets.
- [Actor Storage](https://developers.telnyx.com/docs/edge-compute/stateful-actors/api-reference/storage.md): Per-key persistent storage for a Stateful Actor, accessed as this.ctx.storage: get, put, delete, list, transaction, plus the alarm API and turn-atomic writes.
- [Actor Namespace](https://developers.telnyx.com/docs/edge-compute/stateful-actors/api-reference/namespace.md): The env.<BINDING> handle your function calls into — idFromName (deterministic) and newUniqueId (random), both returning an ActorStub.
- [Actor Stub](https://developers.telnyx.com/docs/edge-compute/stateful-actors/api-reference/stub.md): The client handle returned by idFromName / newUniqueId. Calling a method on the stub is an RPC to that one actor instance.
- [Actor Alarms](https://developers.telnyx.com/docs/edge-compute/stateful-actors/alarms.md): Schedule deferred work from inside a Stateful Actor with the single per-instance alarm. At-least-once delivery redrives on failure, so keep handlers idempotent.
- [Configuration](https://developers.telnyx.com/docs/edge-compute/stateful-actors/api-reference/configuration.md): The telnyx.toml [[actors]] block that declares an actor binding — binding (the env property) and type (the class to instantiate per name).
- [Errors](https://developers.telnyx.com/docs/edge-compute/stateful-actors/api-reference/errors.md): Errors the Stateful Actor runtime surfaces: BlockConcurrencyTimeoutError, ActorOutputGateError, ActorMethodTimeoutError, ActorFetchTimeoutError, CodecError.

## Guides

- [Project Structure](https://developers.telnyx.com/docs/edge-compute/stateful-actors/guides/project-structure.md): A Stateful Actor project is one module that exports two things — the actor class and a fetch handler — wired together by an [[actors]] binding in telnyx.toml.
- [Local Development](https://developers.telnyx.com/docs/edge-compute/stateful-actors/local-development.md): Run a Stateful Actor project locally with telnyx-edge dev — a full function + actor stack in Docker where env.<BINDING> calls resolve and actor state survives hot reloads.
- [Shared Actors](https://developers.telnyx.com/docs/edge-compute/stateful-actors/shared-actors.md): Reach one Stateful Actor type from multiple functions on the same account by declaring the same type under different bindings — the owner ships the class, the reference ships none.
- [When to Use Stateful Actors](https://developers.telnyx.com/docs/edge-compute/stateful-actors/guides/when-to-use.md): Use a stateful actor when an entity has state that must be mutated coherently across many requests. Use a plain function for stateless work, and a database for cross-entity transactions or bulk queri…
- [Key-Value](https://developers.telnyx.com/docs/edge-compute/stateful-actors/guides/storage/key-value.md): Store a Stateful Actor's state at this.ctx.storage with get/put/delete/list and atomic transaction(): private, durable, strongly consistent per-key storage.
- [SQL](https://developers.telnyx.com/docs/edge-compute/stateful-actors/guides/storage/sql.md): Query a Stateful Actor's private, durable SQLite database at this.ctx.storage.sql with synchronous exec(), typed rows, and transactionSync() for atomic writes.
- [WebSockets](https://developers.telnyx.com/docs/edge-compute/stateful-actors/websockets.md): Terminate a live WebSocket on a Stateful Actor: inbound frames dispatch one at a time on the owning instance, with durable state and ws.send() replies.
- [Connection Lifecycle & Limits](https://developers.telnyx.com/docs/edge-compute/stateful-actors/websockets/lifecycle.md): How Stateful Actor WebSocket connections open and close: handshake guarantees, close codes, duration budget, reconnect pattern, and frame and queue limits.