Share your agents’ work within your team, securely.

The short version

• Synced work in allowlisted repositories is shared with members of your Powerplant organization. It is not public and there is no cross-organization sharing mode.
• You can delete traces uploaded from your agents from Powerplant.
• Secret-shaped text is redacted before laptop sessions leave the machine, and before cloud-agent transcripts enter reference storage.
• Raw transcripts are stored separately from account, session, cost, room, and derived-product data.
• Stored credentials are encrypted with AES-256-GCM.
• Production and staging use separate databases, raw-storage buckets, AI-tracing projects, and analytics projects.
• Organization owners can request deletion. We run the deletion deliberately and confirm in writing when it is complete.

The organization is the boundary

Powerplant is transparent by default inside a team. By default, members invited to an organization can see synced agent sessions; people outside it cannot. That boundary is enforced in both the application API and the database’s row-level security policies.

Your connected agent uses Powerplant through OAuth. The agent interface only accepts tokens issued for it, tokens expire within an hour, and every data request remains limited to your organization. Each request is also checked against the live grant you approved; revoking that grant from your Profile takes effect on the client’s next request.

Secrets are scrubbed before storage

For laptop sessions, Powerplant redacts credentials on your machine before upload. For Cursor cloud sessions, the same redaction runs on Powerplant’s server before the transcript is written to the raw-data store.

The redactor removes known secret-bearing fields and scans text for credential formats including API keys, access tokens, connection-string passwords, private keys, and secret-looking environment variables. Stored text is redacted again before full tool-call arguments are served through MCP.

What Powerplant stores

Storage, credentials, and observability

Session metadata and product data live in Postgres. Redacted raw transcripts live in a separate Cloudflare R2 bucket. The application only joins those tiers for work that needs the transcript.

Credentials you optionally connect for services such as Cursor or Anthropic are encrypted at rest with AES-256-GCM. They are write-only through the product API, and a repository-level architecture test prevents the encrypted credential column from appearing outside its owning service.

Operational logs and error reports are scrubbed and do not intentionally contain transcript content. Product analytics contain identifiers, tool names, outcomes, and measured durations, never transcript text, SQL text, or search phrases.

Infrastructure and service providers

These are the services that can process or store Powerplant data today. Customer-selected integrations such as Cursor and GitHub remain under the customer’s own relationship with those providers.

Your data, and deletion

Storing history and context for later analysis is a core feature of Powerplant, so most synced data is retained while your organization is active. Today, organization deletion is a verified, human-run operation requested by an owner, though self-serve org deletion is coming soon.

The operation removes the organization’s live database records, known raw transcript objects, derived snapshots, encrypted provider credentials, and the organization’s observability traces. It leaves content-free security audit records with their organization link severed. We confirm what was deleted and when.

How we test the boundary

Security invariants run in our comprehensive test suite: organization isolation, row-level security, credential containment, token lifetimes, framing policy, migration safety, and source redaction all have executable checks.

Powerplant also has an adversarial MCP audit harness. It creates two synthetic organizations in a non-production environment, probes authentication and cross-organization isolation with ordinary credentials, verifies cleanup, and treats missing coverage as a failure or a named exception. It is an internal control, not an external penetration test or certification.

Compliance

Powerplant is currently invite-only, and we work with our pilot customers’ teams on security and compliance. We are currently targeting the end of December 2026 for SOC 2 Type 1 certification.

If your organization needs a particular control, DPA, or security document, email founders@usepowerplant.com. We would love to partner with a customer who has specific security requirements, but is also keen to get the benefits of Powerplant, and could help us accelerate our in-progress security hardening and validation work.

FAQ