Open Source Cloudflare Workers Alternatives

Rivet Actors are long-running, lightweight processes for stateful workloads. State lives in memory beside the compute and persists automatically, which removes the usual routine of loading a session out of a database and writing it back on every single request.

You create one actor per agent, per session, per document or per tenant, and each one arrives with the plumbing already attached: WebSockets for real-time streaming, workflows with automatic retries, durable queues, and its own timers and cron jobs. Actors run indefinitely while active and hibernate when idle, scaling down to zero.

Observability is built in, from local development through to production.

• SQLite viewer: browse and query an actor's own database while it runs.
• Workflow state: inspect progress, steps and retries as they execute.
• Event monitoring: track every state change and action as it happens.
• REPL: call actions, subscribe to events and interact with your code directly.
• Agent skills: a published skill set gives coding assistants what they need to add Rivet to a project.

RivetKit is a library first, so installing the package runs actors inside your own process during development. Production has three routes: a self-hosted Rust binary or Docker container backed by Postgres, the file system or FoundationDB, or the managed Rivet Cloud edge network. Clients exist for Node.js, Bun, Deno, React and Next.js, with examples for Hono, Express, Elysia and tRPC.

OpenComputer turns a cloud agent into ordinary source code. A project holds one or more agents that run in the cloud, so there is no console to click through and no infrastructure to stand up before an agent answers its first request.

The CLI scaffolds a hello world project with an opencomputer directory holding a project file and an agents folder. Deploying in watch mode binds the directory to an account and pushes every edit to a development environment as you make it. A browser application can live in the same repository with its own lifecycle. Sessions themselves run on real Linux machines with a shell, a filesystem, package managers and network access.

The dashboard and the runtime cover the parts of an agent that usually need custom plumbing.

• Versioned deployments: publishing under an alias creates an immutable release, and earlier ones stay addressable.
• Project view: the playground, sessions, files, connections, channels, schedules and agent schema are all inspectable.
• Durable sessions: a session hibernates when idle and resumes where it left off.
• Scheduling: cron expressions fire an agent without a separate scheduler.
• Secret handling: credentials are bound to an origin and injected after a request leaves the machine.

The TypeScript CLI is separate from the older Go tool and covers login, agent listing, one-off sessions and named runs. It targets the hosted API by default, with a flag or an environment variable to point somewhere else. Teams that need their own cloud or private network are served by the enterprise tier.