Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

hotpath Cloud - performance feedback for developers and coding agents

Note: hotpath Cloud is currently in open beta.

hotpath Cloud is a backend service for the open-source hotpath-rs profiler. It provides an automated feedback loop for performance signals collected from your Rust application, helping both developers and coding agents detect regressions before they are merged.

To get started, log in at hotpath.rs/app. The hotpath-rs GitHub App asks for minimal permissions: no access to your code, only write access to pull requests to post comments. The only data it gets from your CI is the benchmark reports your workflow uploads. See privacy policy for details.

The GitHub Actions integration compares benchmark results against a baseline and posts a PR comment whenever a significant regression or improvement is detected:

hotpath Cloud pull request comment

You can define acceptable regression thresholds using a customizable regression policy and set fine-tuned performance budgets. This helps eliminate noisy alerts and ensures that warnings are emitted only when performance changes in a meaningful way.

# hotpath/policy.toml (excerpt)

# Flag a function whose allocations grow by 20% or more
[functions.alloc]
judged = true
min_percent_change = 20
metrics = ["avg", "total"]

# The hot path must never allocate, whatever the baseline did
[[functions.budgets]]
match = "my_crate::router::route"
alloc = { total = "0 B" }
message = "route() is on the hot path and must not allocate"

# Prevent N+1 calls: at most 5 SQL queries per request, on every route
[[server.budgets]]
match = "*"
timing = { sql_per_request = 5 }
message = "too many SQL queries per request, check for N+1 calls"

The hotpath cloud CLI and dedicated AI skill bring the same feedback loop to coding agents. Agents can analyze benchmark results, identify regressions, and use the profiling data to guide performance optimization:

AI agent summarizing a hotpath Cloud diff

Benchmark reports are persisted in hotpath Cloud, making it easy to share results with your team and compare each report against its baseline:

hotpath Cloud dashboard diff page

See this diff on hotpath.rs

Getting Started

hotpath Cloud supports hotpath version 0.28 or newer.

The quickest way to set up hotpath Cloud is to let your own AI coding agent do it. Install the hotpath CLI and run init-ci inside your project repo:

cargo install hotpath --version '^0.28'
hotpath init-ci --agent claude # or --agent codex / --agent opencode

hotpath init-ci downloads the hotpath_init_ci agent skill from GitHub and starts your installed Claude Code, Codex or OpenCode with it as setup instructions. The agent adds the hotpath-cloud feature, a regression policy file and a GitHub Actions benchmark workflow, so every pull request gets a performance comment.

Use --forks for public repositories that want to benchmark pull requests from forks. Fork pull requests need a separate setup for security reasons:

hotpath init-ci --agent claude --forks

For private repositories, or if you don’t need benchmarks on pull requests from forks, run hotpath init-ci without --forks.

Your agent remains in control: you review and approve edits through its regular permission prompts. Requires curl and the claude, codex or opencode CLI on PATH.

Manual setup

Follow the CI integration guide to add the benchmark workflow by hand.