A terminal your security team will actually approve.

Why this matters for your team

• No sign-in. No telemetry. No data leaves the machine. Yaw doesn’t ship usage analytics, command tracking, or session telemetry. Sessions, history, and connections live on the developer’s machine. The only outbound traffic is license activation against our payment provider, update checks, and AI requests sent directly to whichever provider your team has configured. That answers the security review without a new vendor questionnaire.
• BYOK across AI providers - your AI spend stays on your existing contracts. Yaw connects to Anthropic, OpenAI, and any other provider your team already pays for. No vendor lock-in, no new procurement cycle, no marked-up AI tokens. If your team has an Azure OpenAI commit or an Anthropic enterprise agreement, Yaw uses it directly.
• Windows ARM and Apple Silicon, first-class. Yaw ships native binaries for Windows ARM64, Windows x64, macOS (Intel + Apple Silicon), and Linux (deb, rpm, AppImage). Hardware refreshes to ARM-based Windows laptops or M-series Macs don’t leave anyone on your team waiting for tooling support.

What you get

• Per-seat license keys with a self-serve admin portal. Add or remove seats anytime. Reassign a seat when a teammate changes machines or leaves. Increases prorate mid-cycle, decreases take effect at renewal.
• Centralized billing. One invoice for the whole team. Monthly or annual, your choice. Annual saves 17%. Invoice billing available for 10+ seats.
• Every feature, no gating. Yaw doesn’t lock features behind tiers. The Business license adds team-shared connections (SSH and database), team-shared commands published once by the admin and synced to every seat, and the admin portal. Everything else is identical to the individual license.
• Priority email support direct from the founder. Support is handled by a small in-house team, and priority threads go straight to the founder -- the person who wrote the code. No tier-one queue, no ticket routing.

Pricing

Talk to sales

Tell me about your team and timeline. I read every message personally and reply within one business day.

Or email contact@yaw.sh directly.

Who’s behind this

Yaw Labs is lean, run by the lead dev and 3 testers/support reps/community advocates. Yaw Terminal is built and supported by Jefferson Hale, a developer with a background in DevOps and SRE who got tired of terminals that phoned home. Support is in-house - no offshore routing, no anonymous ticket queue. When you commit to Yaw for your team, you’re committing to a tool with a small, accountable team where the lead dev still picks up the phone.

Also from Yaw Labs: mcp.hosting - hosted MCP servers for teams running AI agents in production.