for · engineering teams

One coding-agent workflow, every developer, every repo.

Standardise on a single orchestrator instead of a different shell-alias mess per developer. Ringlet keeps every project's credentials isolated, every spending line itemised, and every tool call auditable.

What teams use Ringlet for

  • Credential isolation per project. Project A's Anthropic key never leaks into Project B's session. Per-customer engagements get their own profile.
  • Per-team provider policy. Default new profiles to MiniMax for cost; pin Anthropic for compliance-sensitive work; route through a self-hosted gateway for audit.
  • Cost visibility before the invoice. SQLite ledger + CSV export feed straight into FinOps spreadsheets. Engineering managers don't wait for the monthly bill.
  • Audit trail. Hook every tool use to a central log. Slack alert on destructive shell commands. SIEM-friendly JSON output.
  • Onboarding script. New developer's machine ready in one shell-script run — install Ringlet, sync the team registry, restore the team's standard profile set.

A team setup script

setup.sh
#!/usr/bin/env bash
set -euo pipefail

# 1. Install Ringlet
curl -fsSL https://raw.githubusercontent.com/neul-labs/ringlet/main/install.sh | sh

# 2. Pull team registry (private GitHub repo)
ringlet registry add team https://github.com/yourco/ringlet-registry

# 3. Create standard profiles
ringlet profiles create claude default     --provider company-gateway
ringlet profiles create claude security    --provider anthropic-direct
ringlet profiles create codex  back-office --provider company-gateway

# 4. Wire audit hook
ringlet hooks add --all-profiles --on tool-use \
  --webhook 'https://audit.yourco.com/agents'

# 5. Daily usage report → Slack
ringlet hooks add --all-profiles --on daily-rollup \
  --webhook 'https://hooks.slack.com/services/...'

echo "Ready. Run 'ringlet profiles run default' to start."

What you give up

Ringlet is at 0.1.x. The team tier (shared profiles synced to a central server, SSO, centralised policy) is on the roadmap but not yet shipped. Today you get:

  • One-developer isolation (very good).
  • Team-wide consistency via a shared TOML registry repo (good).
  • Centralised policy enforcement (not yet — coming in the team tier).
  • Single sign-on, audit dashboards, role-based access (not yet — enterprise tier).

Procurement and licensing

Ringlet itself is MIT-licensed. There is no per-seat fee. The team tier (when it ships) will be a paid hosted service that augments the open-source binary — you can always self-host the core.

Get on the team-tier early-access list

Email teams@neullabs.com with how many developers you're rolling out to and what your current pain points look like. We're prioritising the team-tier roadmap based on what early teams actually need.

next

Start with one developer, expand from there.

The 0.1.x release is enough to standardise one team. Roll it out on a Friday, see the cost line on Monday, decide if you want the team tier when it ships.