A gRPC-first API workbench.

Test gRPC, gRPC-Web, WebSocket, and REST APIs from one workspace. Run local mocks, inspect streaming responses, and use the same project from the desktop app or CLI.

Download release Star on GitHub 5

layang run ./workspace --request "Get Track" --env dev

Layang desktop app showing the API request and schema workbench

Core workflow

Requests, schemas, mocks, and responses stay in one project.

Import a Proto, select a method, send a request, inspect the response, and save the work without moving between separate tools.

Native gRPC and gRPC-Web

Run unary and server-streaming methods with request bodies, metadata, response history, trailers, and assertions.

target: localhost:50051
method: demo.v1.GreeterService/SayHello
transport: native-grpc

REST

Build requests with params, headers, auth, body modes, examples, and local mock scenarios.

WebSocket

Open ws/wss connections, send payloads, inspect live events, and use local mock responses.

Proto schemas

Import `.proto` files and browse services, methods, request messages, response messages, and revisions.

Response viewer

Inspect latest JSON, message history, tables, search results, and streaming payloads without losing the current scroll position.

Benchmarks

Run latency samples from saved requests and export results for local checks or CI.

Protocols

Use the protocol that matches the service.

REST, WebSocket, native gRPC, and gRPC-Web requests share the same workspace, environments, documentation, and project files.

Layang WebSocket request and live event workflow — WebSocket requests use the same workspace and response workflow as the other supported protocols.

Protocol Client Typical use

Native gRPC Desktop Unary, server-streaming, client-streaming, and bidirectional calls.

gRPC-Web Desktop / browser Unary and server-streaming calls through browser-compatible endpoints.

WebSocket Desktop Live ws/wss connections, messages, events, mocks, and benchmarks.

REST Desktop HTTP requests, examples, docs, auth, and local mock scenarios.

Mocking

Run local mocks without maintaining another project.

Mock scenarios live with the workspace. Start them from the app, edit saved scenarios, and keep streaming behavior close to the request definitions that use it.

Layang gRPC mock streaming editor — gRPC mock scenarios with response sequences and streaming controls.

SCENARIO Per-method scenarios

Keep multiple saved responses for the same RPC method and switch between scenarios when needed.

STREAM Scheduled responses

Configure response sequences, intervals, loops, and maximum loop counts for server-streaming methods.

LIVE Live Push

Keep a stream open and send saved responses manually without closing the client connection.

FILES Workspace-backed

gRPC, REST, and WebSocket mock scenarios stay with the workspace and can be reviewed in Git.

Web Access

Expose gRPC services to browser clients.

Web Access provides a gRPC-Web endpoint backed by the local Native gRPC Mock runtime or another configured gRPC target.

Browser-compatible endpoint

Run gRPC-Web over HTTP or HTTPS. HTTPS uses HTTP/2 and can fall back to HTTP/1.1 when configured.

Browser
  -> gRPC-Web / HTTPS
  -> Web Access
  -> Native gRPC

Independent runtime

Native gRPC and Web Access have separate status and Start/Stop controls.

TLS and certificates

Configure HTTPS certificates and trust internal CA certificates for local or lab environments.

CORS

Configure browser origins without changing the underlying gRPC service definition.

Custom upstream

Route Web Access to the local mock runtime or another gRPC target.

Workspace

The workspace is the project.

Requests, Proto revisions, environments, mocks, and documentation are stored as workspace files. The desktop app and CLI read the same project.

Readable project files Git-friendly changes Desktop and CLI use the same workspace Machine-local state stays under `.layang/`

Documents/Layang/Workspace

layang.yml
collections/
protos/
environments/
mocks/
workspace-schemas/
docs/
.layang/

Documentation

Generate docs from workspace data.

Build Markdown or HTML documentation from request metadata, Proto definitions, examples, mocks, and saved responses.

API reference Service, method, request, response, and source information.

Examples Include saved request and response examples where they are useful.

Export Keep Markdown in the repository or publish generated static documentation.

Layang generated documentation preview — Documentation preview generated from the current workspace.

CLI

Use the same workspace from the terminal.

Run validation, saved requests, mocks, benchmarks, documentation, and CI checks without exporting the project to another format.

layang validate ./workspace --json

layang run ./workspace \
  --request "Get Track" \
  --env dev \
  --reporter junit \
  --output reports/layang-junit.xml

layang mock:start ./workspace \
  --protocol all \
  --daemon

layang benchmark ./workspace \
  --request "Get Track" \
  --iterations 50

layang docs:build ./workspace --check

layang ui ./workspace

Validate Check workspace structure, schemas, saved requests, and mock files.

Run Execute saved requests with environments and CI-friendly exit codes.

Report Write JSON or JUnit output for local checks and build pipelines.

Layang 1.1.6

Download Layang.

Desktop releases are available from GitHub. Standalone CLI packages are available for CLI-only workflows.

Download release Star on GitHub 5