Composable backend construction kit

Act I Â· A backend built to move

Change the theatre.
Keep the code.

Compose against stable capabilities, then change providers, runtimes, and topology as demand growsâ€”from one laptop to a distributed system.

Explore Theatora â†—See how it works â†“

Behind every stage

A backend is not
a single service.

It is identity, data, storage, messaging, compute, workflows, policies, observabilityâ€”and the infrastructure that keeps them running.

Theatora is not a preassembled backend. It is a framework for describing, composing, implementing, and deploying backend systems without starting from a particular cloud, database, or runtime.

Act II Â· The company

One coherent backend.
Four composable layers.

Each layer has a clear role. Change the implementation without rewriting the application.

Modules

Reusable backend behavior.

Authentication, organizations, billing, leaderboards, inventory, and more.

AuthBillingLobby

Capabilities

What the application needs.

Contracts that stay independent of any particular implementation.

IdentityRelational StoreObject StoreQueueRealtimeComputeWorkflowObservability

Bindings + Providers

Contracts meet implementations.

Bind relational to PostgreSQL, objects to S3, queues to NATSâ€”or choose your own.

RelationalStorePostgreSQL

ObjectStoreS3

QueueNATS

Runtimes

Run where the work belongs.

Local processes, containers, WASM, serverless, edge, clusters, or a combination.

LOCALEDGECLOUD

Act III Â· The score

Describe the backend
you intend to run.

A backend definition captures desired compositionâ€”not merely a list of infrastructure resources. Tooling can create, compose, validate, inspect, diff, deploy, migrate, and upgrade it.

createcomposevalidateinspectdiffdeploymigrateupgrade

theatora.yamlâ— â— â—

name: my-application

modules:
  - identity
  - notifications

bindings:
  database:
    capability: relational
    provider: postgres
  events:
    capability: queue
    provider: nats

runtime:
  provider: container

Different performances

Compose for the
application at hand.

The same underlying model supports radically different backend shapes.

Web & SaaS

Build the complete service layer for accounts, organizations, billing, application data, background jobs, and audit trails.

Realtime

Keep live state synchronized across users and services with presence, events, coordination, and durable queues.

Games

Run the systems behind play: player identity, cloud saves, inventory, economies, sessions, and matchmaking.

Edge

Place latency-sensitive work near users while coordinating routing, compute, cache, configuration, data, and workflows.

Same definition Â· New scenery

From one laptop
to a distributed system.

The backend can grow with the developer and the application. Begin with a self-contained local composition, rebind capabilities for production, then introduce replicas, clusters, regions, and edge execution when the system actually calls for them.

01 Â· Develop

One laptop

Local process Â· embedded data Â· local objects Â· local queue

DataSQLite
ObjectsLocal filesystem
QueueIn-memory / local queue
RuntimeNative local process

02 Â· Operate

Production

Managed providers Â· containers Â· durable storage Â· observability

DataPostgreSQL
ObjectsS3-compatible storage
QueueNATS
RuntimeContainers

03 Â· Expand

Distributed

Clusters Â· replicas Â· regions Â· edge runtimes Â· coordinated workflows

DataPostgreSQL HA
ObjectsReplicated object storage
QueueNATS cluster
RuntimeKubernetes / edge

A seamless path at every scale

Keep the code.
Keep the data, too.

Theatora lets the backend move without forcing the application to move with it. Start with Alopex DB and that same continuity reaches the data layerâ€”from embedded on one laptop to a distributed cluster.

Same applicationâ†’New theatreâ†’Same data path

The curtain is yours