Drivers in ActorCore the infrastructure layer between your actor code and the underlying systems.

You rarely need to manually configure drivers. The platform package you’re using will configure the appropriate drivers for you. See the documentation for your platform for details.

​
Accessing Driver Context

Drivers expose a custom driver context for functionality specific to the given driver. This can be accessed as a parameter to createVars then later accessed with c.vars. Read more about the createVars lifecycle hook.

​
Available Drivers

Choose a driver based on your deployment needs - Memory for development, Rivet or Cloudflare Workers for production environments, and Redis for specialized self-hosted scenarios.

Memory

In-memory driver for development and testing. Simple and lightweight with no external dependencies.

Redis

Self-hosted option for custom deployments where you need fine-grained control over your infrastructure. Suitable for specialized deployment scenarios.

Rivet

Fully-managed cloud platform with built-in scaling, deployment, and monitoring. Recommended for production deployments.

Cloudflare Workers

Edge computing platform for global distribution and low latency. Recommended for production deployments.