Self-hosting MobSession

Self-hosting runs MobSession entirely on your own infrastructure: your backend, your web app, your datastore. Session data stays inside the boundaries you control. It's for teams whose security, compliance, or data-residency rules rule out a managed backend.

Preview. This is in early access and rolling out to teams.

How MobSession runs today

By default, the agent runs on the orchestrator's machine and talks to a managed backend we operate. That backend holds session metadata, history, and coordination state. It's the quickest way to start and needs no infrastructure of your own.

Self-hosting changes where that backend lives: you stand up your own and point the CLI at it.

What self-hosting gives you

• Data stays in your environment. Transcripts, history, and coordination state are written to a datastore you own. Nothing leaves your network.
• Bring your own datastore. Connect a database you already run, so retention, backups, and access controls follow your existing policies.
• Configure retention. Set how long session data is kept and when it's purged. See Data and retention for the model and defaults.
• Network isolation. Run the backend and web app inside your private network or VPC, behind your own authentication and ingress rules.

Architecture

The self-hosted setup keeps the same shape as the managed one, with every piece under your control.

The CLI

The orchestrator runs the MobSession CLI on their machine, exactly as today. The only difference is config: you point the CLI at your own backend URL instead of the managed default. The agent still runs on the orchestrator's machine.

Your backend

You deploy the MobSession backend inside your network. It handles session coordination, history, and the API the CLI and web app talk to, and it connects to the datastore you provide. Everything persisted lands in storage you own.

Your web app

You deploy the MobSession web app next to your backend. Reviewers and observers reach it over your network, and session data is served entirely from your environment.

The result is a single trust boundary: CLI to your backend to your web app, all inside infrastructure you run.

Who it is for

Self-hosting targets teams with strict data-control needs:

• Organizations with data-residency or sovereignty obligations.
• Regulated industries where session data can't touch a third-party backend.
• Security teams that need all tooling inside a private network or VPC.
• Companies enforcing internal policies on retention, encryption, and audit directly.

If a managed backend works for your team, the default setup is the simpler path.

Getting into the early-access program

Self-hosting is in early access. During this phase we work directly with teams to provision a deployment, connect your datastore, and tune retention to your policies.

To request access:

• Review the enterprise overview to see how self-hosting fits the rest of MobSession's enterprise capabilities.
• Read Data and retention to understand what is stored, where, and for how long.
• Reach out to start the conversation. We'll share the deployment guide, walk through the architecture for your environment, and help you stand up your first instance.

As the program grows, we'll expand the deployment guide and add self-service tooling. For now, early-access teams get hands-on help.