# HyperProbe

Capture variable values and stack context from a running service without pausing it. HyperProbe exposes read-only probes to developers and coding agents after the service SDK is installed.

Canonical URL: https://aiidelist.com/ide/hyperprobe

Language: en

Updated: 2026-09-11

## Overview

- Category: Developer Workflow Tools
- Runtime state capture for human and agent-assisted service debugging.
- Editor base: VS Code

## Quick verdict

Useful when an investigation needs values missing from logs and you can instrument the affected service first.

## Best for

- Teams debugging running backend services
- Coding agents that need runtime evidence

## Strengths

- Can obtain runtime values that existing logs did not record.
- Makes the same debugging evidence available through editor and agent workflows.

## Limitations

- Projects where adding a service SDK is not possible
- Users needing private hosting on the free tier
- Initial service instrumentation and deployment are required.
- Professional pricing has a three-service minimum; private deployment is an enterprise option.

## Capture the value that the logs missed

HyperProbe addresses a specific debugging problem: a request took an unexpected branch, but existing logs do not show the value that caused it. A read-only probe can capture state when execution reaches a selected line without stopping the process.

This is most useful after narrowing the investigation to a service and code path. A probe will not return a useful capture if the affected request never reaches its location.

## Get your first useful capture

1. Follow the [quickstart](https://docs.hyperprobe.co/quickstart) to create a service and install the editor integration and appropriate SDK.
2. Initialize the SDK as directed and deploy the instrumented service with source and build metadata that match the running version.
3. Place a probe on an executable line near the suspected condition, then exercise that request path.
4. Inspect the captured variables and stack, or let your configured MCP client use that evidence to investigate the cause.

## Separate setup from subsequent debugging

The no-redeploy workflow applies after instrumentation is in place. For a first trial, use a staging service and a reproducible request, then decide which captured fields are appropriate for your production environment. Free managed-cloud operation and enterprise private deployment have different data boundaries; choose the deployment that matches your requirements.

## Features

### Runtime evidence

- Read-only probes capture variables and stack context
- JavaScript/TypeScript, Java/Kotlin, Python, and Ruby support
- No redeploy for subsequent probes after SDK setup

### Developer and agent access

- VS Code extension
- MCP access for tools such as Claude Code, Codex, and Cursor
- Shared capture workflows on team plans

## Pricing

freemium

- Free: $0 — One service on managed cloud with unlimited probes and captures.
- Professional: $99 — service/month — Minimum three services. $79 per service/month with annual billing; includes 30-day capture history and a shared workspace.
- Enterprise: Custom — Self-hosting or private VPC, RBAC, approvals, and PII redaction options.

Pricing checked: 2026-09-12

## Privacy and data handling

The free plan uses managed cloud. Captures can contain runtime data; review field handling and retention. Private deployment and PII redaction are listed as enterprise options.

## Enterprise features

- Self-hosting or private VPC
- RBAC and approval controls
- PII redaction

## Sources

- [Official website](https://www.hyperprobe.co/)
- [Documentation](https://docs.hyperprobe.co/)
- [Installation](https://docs.hyperprobe.co/quickstart)
- [Pricing](https://www.hyperprobe.co/)
- [HyperProbe product, languages, and pricing](https://www.hyperprobe.co/)
- [HyperProbe service setup](https://docs.hyperprobe.co/quickstart)
- [HyperProbe on Y Combinator](https://www.ycombinator.com/companies/hyperprobe)

Last checked: 2026-09-12