Single request debugging
Choose service.method, configure Payload, Metadata, Auth, and TLS, then inspect response and duration.
RPCORA keeps targets, schemas, Metadata, Auth, TLS, variables, responses, and failure diagnosis in one workflow.
One successful call does not make a workflow reproducible. RPCORA moves upstream response values into downstream requests and turns failures into handoff evidence.
Choose service.method, configure Payload, Metadata, Auth, and TLS, then inspect response and duration.
Run saved requests in order while token, userId, and traceId move through the steps.
Generate clues around target, TLS, Metadata, schema source, and gRPC status.
RPCORA focuses on reproducible and shareable debugging, not just one-off calls.
| Need | RPCORA | Ordinary debugging |
|---|---|---|
| Request context | Payload, Metadata, Auth, TLS, and environment variables together | Scattered across commands, scripts, or client settings |
| Schema source | Reflection, Proto folders, and Git repos in one workbench | Manual switching between tools |
| Chain reproduction | Chains store steps and runtime variables | Manual copy-paste or temporary scripts |
| Failure handoff | Doctor produces redacted reports | Screenshots, logs, and verbal context |
RPCORA Doctor organizes clues around target, TLS, Metadata, schema source, and gRPC status.
Chain replay turns login, auth, and business calls into a reproducible path without manual context copying.
Yes. RPCORA is built for local, internal, and microservice gRPC debugging workflows.