streb streb

For Teams

Processualize AI Development

Use streb to deliver AI-assisted software consistently, at scale, with full auditability — across every project and every developer.

Get developers started in 5 minutes
8–16 h
manual setup per developer — learning Claude Code features, writing CLAUDE.md rules, configuring Beads, Jira OAuth, best practices
vs
with streb
< 5 min
production-ready setup: consistent, proven configuration deployed to every developer on the team

For a team of 10 developers: 80–160 hours saved. Two to four weeks of engineering time — back.

Plus the long-term value of consistent, battle-tested configurations across every project.

The Delivery Model

The Agentic Development Factory

IT consulting firms already think in terms of delivery factories, standardized processes, and quality gates. streb maps directly onto this model. Every loop has defined input and output artifacts. Every developer runs the same environment. Every agent action is recorded.

The result: a standardized, repeatable, quality-controlled production line for AI-assisted software delivery that you can deploy across your entire practice — and demonstrate to clients.

See the 10-loop SDLC architecture
Consistent across every project
Every developer, every project, every machine — the same production-ready configuration. No drift. No "it works on my machine."
New developers productive on day one
5 minutes instead of 2 weeks. New team members arrive at a project and are contributing within the hour.
Demonstrable methodology for clients
Show clients a governed, structured AI delivery process — not ad-hoc prompting. The 10-loop framework and audit trails are client-presentable artifacts.

Enterprise & Compliance

Audit-ready by default

streb's git-native audit trail satisfies compliance requirements without additional tooling. Every agent action is recorded, queryable, and reviewable.

Complete Audit Trail

Every agent tool call is logged to tool-audit.jsonl. Requirement, task, and code changes are tracked in git history. The result is a complete, tamper-evident record compatible with SOC2, ISO 27001, and similar standards.

Traceability Chain

Every line of code traces back through its commit, task, requirement, and source document. Git hooks enforce task IDs in every commit. The chain is verifiable by the quality gate in Loop 9.

Secret & Security Protection

Pre-command hooks block access to .env, *.pem, and credential files. Headless mode applies stricter secret scanning. OWASP Top 10 prevention rules are configured by default.

adesso AI-Hub Gateway

All Claude API traffic is routed through the AI-Hub, for project cost attribution. API costs are tracked per project for accurate client billing.

Deployment options

From individual developer machines to VDI fleets — streb supports enterprise deployment patterns without admin rights.

Developer Machine

Each developer runs streb init once. No admin rights required. Installs to user directories. Prerequisites: Git, Node.js LTS, 500 MB disk space.

Developer setup guide →
VDI / Golden Image

Pre-install prerequisites, set environment variables in system profile, optionally run streb init --yes once, then deploy to all VDIs. Supports silent deployment.

# System-level config
export ANTHROPIC_BASE_URL="https://adesso-ai-hub..."
export ANTHROPIC_AUTH_TOKEN="your-token"
streb init --yes --config-strategy backup
CI / Pipeline

Headless mode provides a CI-native entry point. Configure with --profile ci. The included GitHub Actions template supports manual dispatch, issue-triggered runs, and scheduled crons.

GitHub Actions setup →

Project Tracking

Jira stays your source of truth

streb sets up bidirectional Jira sync via Beads. Tasks created in Beads automatically appear in Jira. Jira updates sync back to Beads. Your project managers see their Jira boards as normal — developers work in git and the terminal.

The bridge is transparent. streb handles the OAuth configuration as part of streb init. No manual token management.

Bidirectional sync: Beads ↔ Jira
OAuth configured during streb init
Tasks carry satisfies links to requirements
EPIC labels trigger agent runs in GitHub Actions
Project managers see normal Jira boards
No external service beyond your Jira instance

For IT Administrators

What you need to know before allowing streb in your environment.

Architecture

See the full 10-loop SDLC

Understand how streb structures the entire software delivery lifecycle — from requirement extraction through quality gates to EPIC closure.

How It Works
Get Started

Ready to onboard your team?

Send developers to the setup guide. Each developer runs one command and is productive in under 5 minutes.

Developer Setup Guide