Changelog

What reached production, and when. Things we have not built yet are listed on the security page, not here.

  1. Setup from the command line

    One command now does the whole first run. npx -y tiertwo registers the hosted endpoint in every MCP host on the machine, reads those same host configs to find the remote systems your agents already call, and opens the browser so you can connect them in one list. After you connect a system it offers to remove the direct entry from the hosts so the agent's calls go through Tier Two instead of around it. That step asks first and is reversible: npx -y tiertwo undo puts every entry back.

    • No install, no key pasted, no new identity: the command holds nothing but a one-time link
    • Header values never leave the machine; only the system's name and origin travel
    • Local stdio servers are left alone
    • The add-mcp one-liner still works on its own

  2. Devices, device health, and Client 0.3.1

    Every managed machine now has a page of its own. The Agents screen gained a Devices view that lists each machine with its health, its trust rung, and the agents seen on it. Revoking a device also revokes those agents and refuses any later call that still carries the machine's identity. Admins set health requirements under Settings, Advanced, Device health, and can turn on Enforce so an unhealthy machine loses Managed. Client 0.3.1 also fixes a packaging fault that stopped 0.2.0 and 0.3.0 from launching on macOS.

    • Nine checks: disk encryption, screen lock, firewall, secure boot, SIP, Gatekeeper, OS version, Client version, posture age
    • Enforce is off by default, and a check the Client cannot probe never counts against a device
    • Client 0.3.1 reports the new posture, re-checks hourly and on wake, and shows its health in the tray

  3. Client 0.2.0, for the hosted endpoint

    The desktop Client no longer runs a local gateway. It registers the hosted endpoint in your MCP hosts and adds the machine's device identity to every call, so posture rides along with the person's sign-in. It replaces 0.1.x, which talked to the retired local path.

    • One binary, no proxy: hosts talk to trytiertwo.com/mcp directly
    • Device identity and posture on every call from a managed machine
    • Signed and notarized macOS packages; Debian and RPM for Linux

  4. The hosted endpoint, and three modes

    Connecting an agent no longer means installing anything. Tier Two runs an MCP endpoint your agent registers with one command; the first tool call opens a browser and signs you in. Behind it, every (connection, tool) pair is Allow, Ask, or Block. The rules, permissions and grants that used to sit in front of a call collapse into one mode you can read at a glance.

    • npx add-mcp registers the endpoint in every MCP host it knows
    • Sign-in is OAuth through your workspace: no key to paste and no code to type
    • Posture presets: Open, Recommended, Locked. Recommended reads Allow, writes Ask
    • An Ask pauses the call and completes it when a person approves

  5. Audit export to your SIEM

    Both ledgers now leave the product. Configure an HMAC-signed webhook or a Splunk HEC destination and Tier Two delivers three versioned streams (decisions, governance changes, and sessions) in order and at least once, on a five-minute cadence.

    • Signature scheme you verify the way you verify a Stripe webhook
    • Per-stream cursors and a settle watermark, so nothing is skipped on a retry
    • Test-send and secret rotation in the dashboard

  6. The Tier Two Client

    An optional desktop app for organizations that want the machine itself to count. It carries a device identity, reports posture, and lets policy require an org-managed device for the tools that warrant one.

    • macOS builds are signed with a Developer ID certificate and notarized by Apple
    • Debian and RPM packages for Linux
    • Fleet enrollment by MDM or an admin-minted enroll secret

Connect your first agent.

Start free. One command, no credit card required.

Sign upRead the docs