Active/active by design. A mesh that spans your cloud.
MisterShell cores self-cluster into one mesh — every core serves traffic, the mesh federates across regions, and operators and AI agents reach a local core while workers execute close to your resources. Self-hosted, latency-optimized, with no single point of failure.
No single point of failure
Deploy three or more cores and they self-cluster active/active (multi-core high availability comes with the Pro edition). Every core serves traffic; an elected leader orchestrates task scheduling exactly-once. Lose a core and the cluster keeps serving — a new leader is elected automatically and in-flight scheduling continues without duplication.
Self-clustering
Cores form one mesh with an elected leader — leadership fails over automatically through the database lease, no extra orchestrator to run. Cluster status is one command away on the operator console, and a health endpoint feeds your load balancer.
Automatic failover
A failed core is absorbed automatically; a new leader is elected and exactly-once scheduling survives the transition.
Stateless workers
Workers hold no state and reconnect automatically, so session reach stays resilient through a failover.
Each release ships with its own upgrade notes; take a database backup first and follow them.
One fabric, spanning regions
Cores mesh automatically within a region and federate across regions into a single high-availability fabric with one fabric-wide elected leader. Drop cores into each region and they join the fabric — one coordinated mesh you can see in the live Fabric topology view, every core, region, and attached worker, sensor, and proxy on one graph. One policy model and one audit trail, everywhere.
Latency-optimized global access
Run a core in every region and place workers next to your resources. Operators and AI agents connect to the nearest core; workers execute close to the targets they manage — so access is fast wherever your people and infrastructure are, under one policy and one audit trail worldwide.
Local for operators
People and AI agents hit the nearest core — no cross-region round-trips for everyday work.
Local for resources
Workers run inside each region and segment, so sessions and automation reach targets over the shortest path.
Global governance
One inventory, one set of policies, one audit trail — regardless of how many regions you span.
Recordings survive node loss
Session recordings replicate across the cluster as they are captured and finalize to the object store you own. A captured session stays replayable even if the core that hosted it fails mid-session — your audit evidence outlives any single node.
Plugs into the infrastructure you already trust
MisterShell makes its own application tier highly available and rides on the managed load balancers, databases, and caches your cloud already runs. There is no separate data platform to run — you leverage the high-availability infrastructure you already operate, and MisterShell becomes a first-class, resilient citizen of your global cloud estate.
Start on one container. Grow to active/active — same image.
The deployment you start with is not a dead end. The very same image scales from a single container to an active/active cluster spanning regions — no re-architecting. Multi-core high availability comes with the Pro edition.
- 1
Single container
Everything embedded — control plane, data services, and a worker in one container. The fastest path to a working workspace; ideal to evaluate or run a small single-zone estate.
- 2
HA cluster
Add cores in one region and they self-cluster active/active: every core serves traffic, an elected leader schedules exactly-once, and recordings replicate. No single point of failure in the application tier.
- 3
Multi-region
Run a core in each region for geographic reach and low-latency locality — users and workers connect to the nearest region, federated into one mesh.
- 4
Multi-region, highly available
Redundant cores in every region — the full topology. One HA fabric spanning regions: each region is internally redundant and local to its users, all under one policy and audit model.
MisterShell makes its own application tier highly available and, by design, leverages the managed load balancer, database, and cache you already operate — rather than duplicating platforms your team already runs — so those stay under your control. See the deployment docs for prescriptive Docker and Kubernetes guidance for each topology.
Get in Touch
Want a guided demo, or a trial license to evaluate Pro or Enterprise on your own infrastructure? Tell us — we'd love to hear from you.