Security & Data Boundary

The agent runs where your build already runs.

Codebase Pulse is pre-production observability for .NET and Rust. pulse-agent executes locally on your existing CI runner — as a CLI step, GitHub Action, or Azure Pipelines task — and parses compiler, test, benchmark, and load-test artifacts in place. Source code and raw binaries never leave your infrastructure.

  1. Deployment boundary

    All artifact parsing happens on the customer’s CI runner. Outbound traffic is a single HTTPS connection to the Pulse API authenticated with a workspace-scoped PULSE_TOKEN stored in your CI secrets. Codebase Pulse requires zero inbound network access to your environment and never sits in your production path.

  2. Local parsing, metadata only

    Raw build logs (.binlog, cargo --timings), compiled binaries, and working trees stay on the runner. The agent transmits only structured metric summaries, timing graphs, test outcomes, hardware telemetry, and rule fingerprints needed to render the report and post pull-request headlines.

  3. Operational scope

    Pulse is a CI signal layer, not a production APM and not a source-code scanner hosted on third-party build servers. Guard ( --guard on pull request jobs) gates headline metrics against the baseline branch you configure — usually after baseline runs on that branch look trustworthy. A SOC 2 report is not published at this time.

Payload transparency

What stays on your runner vs. what is transmitted.

Security and architecture teams can verify exactly what crosses the network boundary when a pipeline step completes.

Stays on your CI runner

Never transmitted to Codebase Pulse

  • Application source code, headers, and the Git working tree
  • Compiled binaries, assemblies, crates, container images, and packages
  • Full raw MSBuild .binlog files (which can embed environment variables and source snippets)
  • Environment variables, connection strings, and CI secret store values

Sent to the Pulse backend

Structured telemetry & summaries

  • Timing graphs and durations (projects, crates, MSBuild targets, analyzer rules, test cases)
  • Test outcomes, normalized failure signatures (stripped of dynamic GUIDs/numbers), and flaky metrics
  • Benchmark statistics (mean, P95, allocations), load-test KPIs (p95, throughput, error rate, k6 checks/thresholds), and aggregated OpenTelemetry operation counters
  • SARIF rule IDs, file paths, and deterministic fingerprints — plus Git ownership/bloat statistics when pulse-agent owner or pulse-agent repo is used
  • Runner hardware profile (CPU single-core score, core count, RAM and disk I/O utilization during the job)

Infrastructure & Residency

Google Cloud, with a regional data seat

Reports, metering, and the ingestion API are hosted on Google Cloud. The marketing website is operated as a separate environment.

For customers in the EU and EEA, Pulse data is stored on Google Cloud in the European Union. That region is live in production, and EU/EEA customer data is never transferred to the United States. A dedicated United States region is planned for US customers and Global organisations that select a US seat. Privacy.

All traffic between pulse-agent, the web UI, and backend services is encrypted in transit using TLS. Data at rest is encrypted using Google Cloud’s default encryption. Customer-managed encryption keys (CMEK) are not offered on published plans; for air-gapped or in-house requirements, see our contact page.

Authentication & Access Control

Identity Platform for users. Scoped tokens for CI.

Interactive access to the Pulse web UI uses Google Cloud Identity Platform (GCIP). Engineers sign in with their corporate Microsoft or Google account. Access is isolated per customer workspace — bound to the legal entity on the invoice.

CI pipelines authenticate with a non-interactive, workspace-scoped PULSE_TOKEN stored in your CI secret manager. Revoking a token immediately terminates uploads from that pipeline. When you opt into PR comments or inline GitHub SARIF annotations via pulse-agent summary --vcs-token, the VCS token is used directly by the agent on your runner to call your Git provider’s API and is not stored by Codebase Pulse. See Terms.

Additional identity providers or enterprise SSO are available on request. Contact us.

Retention

Predictable retention by plan

Codebase Pulse retains job metadata only for the window confirmed on your plan (14 days on Starter, 30 days on Team, 90 days on Growth, or 365 days on Enterprise), after which run records are deleted. Aggregate metering and billing records are kept as required by tax and accounting law.

Website enquiries are delivered via Resend, and Google Analytics 4 is loaded on the marketing site only after explicit cookie consent. Neither service receives CI job metadata. Privacy.

Agreements & Reviews

Data processing and security review

Need a signed Data Processing Agreement (DPA), EU data residency confirmation, or answers to a vendor security questionnaire? We handle reviews directly with your security or legal team.