PathruleCloud Signals
Pathrule Cloud for Signals - write-only project keys and where to manage them, how events are read, which plans include it, and retention.
Pathrule Cloud runs Signals for you: managed ingestion, retention, and access for your agents with your own session. Standalone and Local Signals stay free and unmetered on every plan; this page is only about Cloud.
Project keys
The Cloud destination authenticates with a project key. Keys start with prs_, are write-only and are public by design, so they are safe to ship in browser code: a key can send events but read nothing.
Create, list and revoke keys on the workspace's Signals page in the Pathrule Cloud console. Add the SDK with npm install @pathrule/signals and pass the key to the Cloud destination, as the quickstart shows. An agent can set this up with you; see agent integration.
Reading events
pathrule instrument events and the pathrule_runtime_events tool read Cloud groups with your own session, so an agent sees only workspaces you can see.
Plans
| Plan | Standalone and Local Signals | Cloud Signals |
|---|---|---|
| Solo | Yes | No |
| Pro | Yes | Yes |
| Team | Yes | Yes, shared across the organization |
| Enterprise | Yes | By contract |
Events are counted per month on a UTC calendar-month boundary, and a Team organization shares one allowance across its workspaces. See the pricing page for what each plan includes.
Retention
Groups follow the same lifecycle as in Pathrule Local: an unresolved group expires after 14 days without an occurrence in production, 7 days in development or preview, and 30 days for a declaration. Archived groups are compacted after 90 days, and compacted records and usage history are deleted after a year.
What Cloud runs for you
- the managed ingest pipeline,
- recording fixes on Cloud, and verifying them with the same policy as Local,
- envelope deduplication,
- automatic retention.