Every AI prompt.
Every commit.
Documented.

Every prompt you type into Claude Code, Cursor, or Gemini CLI is timestamped and stored locally. When you commit, the session is linked to that commit's SHA. A permanent, queryable record of which AI helped write which code.

SOC 2 requires evidence of how software is developed. EU AI Act Article 13 requires transparency documentation for AI-assisted systems. Prompture generates both automatically — no manual paperwork.

The knowledge graph shows who has AI-assisted expertise in which file paths. The literacy score tracks how effectively each engineer uses AI over time. The coach surfaces patterns via Claude on AWS Bedrock.

Your public profile at /u/handle shows your verified AI contribution history — real commits, real prompts, real confidence scores. Not a resume claim. Cryptographically linkable evidence.

One curl command. Installs git hooks and Claude Code hooks into your repo. Takes 30 seconds.

Use Claude Code, Cursor, Gemini CLI, or Aider as you always do. Hooks silently capture each session in local SQLite.

On git commit, the post-commit hook scans recent AI sessions and links them to the commit SHA. Data stays on your machine until you push.

git push triggers the pre-push hook which sends session + commit data to Prompture. The matcher runs and produces confidence-scored attribution.

Stats, matches, knowledge graph, and cost attribution in real time. Share your public profile URL with anyone.

Generate AIBOM exports, audit CSVs, and compliance reports for SOC 2, EU AI Act, or internal governance.

Show exactly what you prompted, what confidence the attribution carries, and which commits came from collaborative sessions vs fully AI-generated ones.

Your Claude Code bill is a black box. Prompture breaks it down by repo, branch, model, and day. See which features cost the most to build.

Your /u/handle page is a live, verified record of your AI-assisted engineering work. A cryptographically linked audit trail that anyone can inspect.

Install once, forget about it. The hooks run silently. You keep using whatever AI tools you use. git push handles everything.

Auditors require evidence of your SDLC controls. Prompture's audit log, AIBOM exports, and match history provide timestamped, append-only records of AI involvement in every commit — satisfying CC8.1, CC8.2, and AI-specific controls.

High-risk AI systems must document training data, capabilities, and human oversight. Prompture's attribution data constitutes the 'instructions for use' documentation required by Article 13.

Enterprise tier supports customer-managed encryption keys (CMEK) and regional data residency. On-prem Docker/Helm bundle available for complete air-gap deployment.

Integrate with your existing Okta, Azure AD, or Google Workspace identity provider. Automatic user provisioning and deprovisioning via SCIM. RBAC with owner, admin, and member roles.

See who has AI-assisted expertise in which parts of the codebase. When an engineer leaves, their knowledge doesn't walk out the door — it's captured in the graph.

Track how effectively each engineer uses AI over time: match rate, prompt quality, model utilisation. Use for training prioritisation, team health reviews, and demonstrating AI ROI to leadership.

Absolute file paths, system tags, agent harness noise, and tool metadata are stripped from prompt previews before storage.

Every database row is scoped by org_id. Row-level security in Postgres ensures no cross-org data access even within the same cluster.

The audit log table has no UPDATE or DELETE permissions. Events are immutable once written.

Prompture never stores file contents, diffs, or source code. Only prompt text, token counts, and git commit metadata.

Enterprise tier supports customer-managed encryption keys and regional data residency. On-prem Docker/Helm bundle available for complete air-gap deployment.