Open-Source Testing · unkn0wn-root

resterm

Resterm is a keyboard-driven terminal API client for REST, GraphQL, gRPC, WebSocket, and SSE protocols. It stores requests as plain text files, runs locally without cloud sync, and includes built-in support for SSH tunnels, Kubernetes port-forwarding, OAuth 2.0, workflows, tracing, and profiling.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/unkn0wn-root/resterm

1.8k

GitHub stars

Forks

Primary language

Apache-2.0

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	unkn0wn-root/resterm
Owner	unkn0wn-root
Primary language	Go
License	Apache-2.0 — OSI-approved
Stars	1.8k
Forks	48
Open issues	0
Latest release	v0.45.2 (2026-07-07)
Last updated	2026-07-08
Source	https://github.com/unkn0wn-root/resterm

What resterm is

Written in Go, Resterm provides a TUI with Vim-style navigation, a CLI runner (`resterm run`), and an embeddable headless Go API for custom integrations. It executes requests defined in `.http`/`.rest` files with conditional logic, multi-step workflows, captures, variables, and assertions using RestermScript—a purpose-built expression language.

Quickstart

Get the resterm source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/unkn0wn-root/resterm.git2cd resterm3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Local API development and debugging

Teams working on REST, GraphQL, or gRPC services can rapidly test endpoints, inspect responses with tracing and profiling, and version control requests as plain files alongside code.

Multi-protocol API testing workflows

Define complex multi-step workflows combining REST, GraphQL, gRPC, WebSocket, and SSE in a single `.rest` file with conditional logic, captures, and assertions for end-to-end API validation.

CI/CD integration and headless automation

Use `resterm run` or embed the headless Go API to execute requests in pipelines, compare runs across environments, and generate JSON or JUnit reports without a GUI.

Implementation considerations

Requests are plain `.http`/`.rest` files with RestermScript expressions; teams must learn the syntax and conventions. Documentation and examples are provided, but training time is required.
SSH tunnels and Kubernetes port-forwarding require local network access and credential management (e.g., kubeconfig, SSH keys). Ensure your deployment environment supports these modes.
Workflows, assertions, and captures rely on RestermScript; complex conditional logic or custom validation may require careful test design and debugging within the TUI.
The headless Go API is public but marked as embeddable; compatibility guarantees across minor versions are unknown. Test integration thoroughly before production adoption.
glibc 2.32+ is required for Linux pre-built binaries. Older distributions must build from source, which adds setup overhead.

When to avoid it — and what to weigh

Need cloud-based request synchronization — Resterm explicitly keeps everything local with no cloud sync or account system. If your team requires centralized, cloud-backed request storage, this is not a fit.
Require commercial vendor support or SLAs — This is a community-driven open-source project. Unknown maintainer velocity and no formal support channels mean you cannot rely on vendor guarantees or SLAs.
Heavy reliance on GUI-based workflow builders — Resterm is keyboard-centric and file-driven. Users who prefer point-and-click interface builders or graphical workflow editors will find the text-based model limiting.
Existing tooling deeply embedded in Postman, Insomnia, or Paw — Migration cost from established tools may be high. If your team has significant investment in another platform's plugins, templates, or collaboration features, evaluate the cost-benefit carefully.

License & commercial use

Licensed under Apache License 2.0 (Apache-2.0), a permissive OSI-approved license. Permits commercial use, modification, and distribution with explicit warranty disclaimers and requirement to include license notices.

Apache-2.0 is a well-established permissive license that allows commercial use without royalties or attribution requirements (beyond license inclusion). However, this is a community-driven project with no vendor backing; commercial adoption assumes acceptance of community-only support and potential maintenance gaps.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Adequate
License clarity	Clear
Deployment complexity	Low
DEV.co fit	Good
Assessment confidence	High

Security considerations

Resterm stores requests and credentials locally; no cloud transmission means reduced risk of interception, but local credential management (SSH keys, auth tokens, env files) relies on OS-level security. OAuth 2.0 and command-backed auth reduce need to hardcode secrets in files, but `.http` files can contain sensitive data—version control and file permissions must be managed carefully. No mention of encryption at rest, credential vaulting, or security audit history in the data provided.

Alternatives to consider

Postman

Cloud-based API platform with team collaboration, syncing, and extensive integrations. Better for organizations needing centralized management and vendor support, but requires accounts and external hosting.

Insomnia

Desktop/web API client with GUI workflows, local-first option, and plugin ecosystem. Simpler onboarding for non-CLI users, but less code-first and workflow-definition-focused than Resterm.

curl / HTTPie + shell scripts

Lightweight CLI tools for simple request testing. No TUI or workflow engine, but zero overhead and maximum portability. Suitable for minimal use cases or CI/CD scripting only.

Software development agency

Build on resterm with DEV.co software developers

Resterm is a strong fit for development teams seeking a local-first, text-driven API client with workflow automation and CI/CD integration. Assess licensing, maintainer commitment, and your team's CLI comfort before adoption.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

rest-assured milkman apitest

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source Testing API Development Application Development DevOps Talk to DEV.co

resterm FAQ

Can I use Resterm in CI/CD pipelines?

Yes. Use `resterm run` to execute `.rest` files headlessly, output JSON or JUnit reports, and compare runs across environments. The embedded Go API (headless package) also enables custom CI integration.

Does Resterm sync requests to the cloud?

No. Resterm is explicitly local-first with no cloud sync, accounts, or telemetry. All data stays on your machine.

Can I collaborate on API requests with my team?

Resterm does not provide built-in collaboration. You can version control `.http` files in Git and share via pull requests, but real-time collaboration or cloud-based sharing is not supported.

What platforms are supported?

Linux (glibc 2.32+), macOS, and Windows. Pre-built binaries are available; build-from-source is an option for older Linux distributions.

Software development & web development with DEV.co

Adopting resterm is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source testing software in production.

Evaluate Resterm for your API testing needs

Talk to DEV.co Schedule a Consultation