A shared home for
your team's knowledge.
Pathrule Cloud keeps your workspaces, their history and your team's knowledge in one managed place. It adds Team Intelligence on team plans, the Remote MCP endpoint and billing, with the console at app.pathrule.io.
zsh
# your team's workspaces live in Pathrule Cloud$ pathrule setup[ok] Signed in as you@acme.com[ok] Workspace attached to this folder.$ pathrule statusCurrent folder: attached to acme-shop# HTTP clients reach the same workspace through Remote MCP$ claude mcp add --transport http pathrule https://mcp.pathrule.io/mcp
More than sync.
Organizations and rolesMembers and roles per organization, and the workspaces your agents read from and write to.Persistence and historyKnowledge is stored and versioned in Cloud. A deleted memory, rule or skill stays restorable for 30 days.Team IntelligenceOn team plans, owners and admins turn team evidence into suggested patterns. Only what a person verifies reaches your agents.Remote MCPA hosted endpoint with OAuth 2.1 sign-in for Claude Code, Codex, Claude.ai and other Streamable HTTP clients.CLI and VS CodeConnect a local folder to a Cloud workspace, and to the agents you use.BillingPlans, seats and invoices in the console at app.pathrule.io.
A managed home for the knowledge a team maintains together, with access governed by the organization.
Choose your deployment boundary.
- Pathrule CloudPathrule runs the workspaces, their history and Team Intelligence for you.
- Local mode
pathrule setup --localruns with no account, and knowledge is stored on your machine. - Self-hostedYour own database and identity provider. SSO is available only in self-hosted deployments.
Managed by Pathrule, kept on one machine, or run on your own infrastructure. The knowledge model is the same in all three. What Cloud mode stores and sends, and what stays on your machine, is on the security page.
Where to go deeper.
Start with
Cloud.
- Open Pathrule CloudThe console at app.pathrule.io.
- PricingWhat each plan includes, and its allowances.