System Architecture & Security

Built for zero data retention and sub-2-second latency.

Impulsed processes Git diffs inside isolated, stateless workers. Raw source code is never stored on disk, logged, or used to train models.

Cloud architecture

Designed for security, speed, and zero retention.

How Impulsed processes regulated engineering workloads from pull request webhook to immutable compliance evidence.

Step 01 · Edge Ingest

Webhook Ingestion.

GitHub Enterprise and GitLab webhooks are ingested via serverless edge workers with strict HMAC-SHA256 signature verification.

Step 02 · Isolation

Ephemeral AST Sanitization.

Unified Git diffs are parsed inside isolated, ephemeral containers; raw secrets and high-entropy tokens are masked prior to inference.

Step 03 · Zero Data Retention

Frontier Gemini 3.8 Flash Reasoning.

Reasoning runs on Google Gemini 3.8 Flash via the Interactions API with strict Zero Data Retention (store: false) and structured JSON schema enforcement.

Step 04 · Signed Evidence

Immutable Audit Ledger.

HMAC-SHA256 signed JSON compliance artifacts and customer changelogs are persisted in the workspace ledger ready for Vanta, Drata, or external auditors.

Security Specifications

Defense-in-depth from webhook ingress to signed output.

HMAC-SHA256 & Short-Lived Installation Tokens

Every GitHub and GitLab webhook is validated using constant-time HMAC-SHA256 signature comparison. GitHub App tokens expire automatically within 60 minutes.

Ephemeral V8 Isolate Sandboxes

Each pull request evaluation runs in a dedicated, memory-capped isolate that is destroyed immediately after returning the structured JSON compliance verdict.

Contractual Zero Data Retention (ZDR)

Enterprise LLM inference calls operate under strict ZDR agreements — prompts and diffs bypass provider abuse logs and human review queues.

VPC Peering & Self-Hosted Runner Option

Regulated banking and healthcare teams can execute the AST diff engine entirely inside their own AWS/GCP VPC or GitHub Actions self-hosted runners.