Security
The agent runs where your build already runs.
Pulse is pre-production observability for .NET. pulse-agent executes as a step on the customer CI runner — GitHub Action, Azure Pipelines task, or CLI. Application and data services run on Google Cloud. User authentication is Google Cloud Identity Platform. Users sign in with a Microsoft or Google account. Source code is not transmitted to Codebase Pulse.
Deployment boundary
Analysis runs on the customer’s existing CI runner. The workspace authenticates with
PULSE_TOKEN, stored in the customer’s CI secrets. Codebase Pulse does not require inbound access to the customer network and is not in the production path.Data leaving the job
The agent transmits metadata: timings, test outcomes, performance signals, repository health, and optional SARIF summaries. That payload is sufficient for the report and for headlines on the pull request or in CI output. Source and the working tree remain on the runner.
Scope
Pulse is not a production APM and not a general-purpose profiler store. Guard is an optional quality gate on headline metrics and is disabled until the customer enables it. A SOC 2 report is not published at this time.
Infrastructure
Google Cloud, with a regional data seat
Reports, metering, and the agent API are hosted on Google Cloud. The marketing website is a separate environment.
For customers in the EU and EEA, Pulse data is stored in Google Cloud in the European Union. That region is in production. A United States region is planned. Customers in the United States, and Global customers who select a US seat, will be served from that region when it is available. EU and EEA Pulse data is not transferred to the United States. Privacy.
Product traffic is encrypted in transit with TLS. Data at rest is encrypted with Google Cloud’s default encryption. Customer-managed encryption keys are not offered on the published plans.
Authentication
Identity Platform for users. Workspace tokens for CI.
Interactive access to Pulse uses Google Cloud Identity Platform (GCIP). Users sign in with their Microsoft or Google account. Sessions are issued by Identity Platform. Access is granted per customer workspace — the legal entity on the invoice.
CI jobs authenticate with a workspace-scoped PULSE_TOKEN held in the customer’s secret store. The agent does not use an interactive user account. Revoking the token terminates further uploads from that pipeline. Tokens must not be committed to source control or shared with another organisation, as set out in Terms.
Additional identity providers or enterprise SSO are available on request. Contact us.
Retention
Job metadata, metering, and billing records
Codebase Pulse stores the metadata required to produce the report, publish headlines, meter Pulse Runs, apply Guard when enabled, and issue invoices. Retention follows the term confirmed for the plan. Source code, local build artifacts, and runner storage remain with the customer.
Website enquiries are delivered by Resend. Google Analytics 4 is loaded only after cookie consent. Neither is part of Pulse job metadata. Privacy.
Agreements
Data processing and security review
A data processing agreement, a residency commitment, or a security questionnaire is available on request.