App 08 — Team

Your team. Their roles.

RBAC, email invites, and per-member spend tracking. Add teammates with the right permissions and know exactly who's spending what.

Start free See the API

Team members 4 active

Member	Role	Status	This month
alice@acme.co	admin	active	$12.47
bob@acme.co	developer	active	$8.91
carol@acme.co	developer	active	$3.22
dave@acme.co	viewer	pending	—

What Team does

Four Roles

Admin, Developer, Viewer, and Auditor. Each role scoped to the right level of access. Assign on invite or change later via API.

Email Invites

Invite teammates by email. Each invite gets a unique token. Accept via link. The mailer integration sends the email automatically.

Per-Member Spend

See exactly how much each team member is spending. Monthly rollups by customer ID with request counts and token breakdowns.

Audit Integration

Every invite, role change, and removal is logged to Brand's append-only audit ledger. Full accountability for team changes.

API-First

Full REST API for member CRUD, invite acceptance, and spend queries. Automate onboarding and offboarding in your CI pipeline.

Zero Dependencies

No LDAP, no Okta integration required. Team management ships inside the binary. Works on day one with no extra config.

The API

Manage your team programmatically. Invite members, update roles, track spend — all via REST.

# Invite a new team member
curl -X POST /api/team/members \
  -d '{"email":"alice@acme.co", "name":"Alice", "role":"developer"}'

# List all team members
curl /api/team/members

# Update a member's role
curl -X PUT /api/team/members/tm_8a4f2c \
  -d '{"role":"admin"}'

# Accept an invite
curl -X POST /api/team/accept-invite \
  -d '{"token":"a1b2c3..."}'

# Per-member spend this month
curl /api/team/spend
  

Built by one person, on purpose

Stockyard is a solo project. There is no sales team, no board of directors, no venture capital timeline pushing for growth at all costs. The product decisions are made by someone who uses the tools daily and ships code to the same repository. This has trade-offs — support response times depend on one person's schedule, and feature requests compete with a single developer's bandwidth. But it also means the product stays focused, pricing stays simple, and the roadmap is not driven by what investors want to see in a quarterly report.

The architecture reflects this philosophy. A single Go binary with embedded SQLite is not just a technical choice — it is a commitment to operational simplicity that makes the project sustainable for a solo maintainer. No microservices to orchestrate, no database migrations to coordinate, no container registry to manage. When a bug gets reported, the fix goes into one repository, one binary, and one deploy. The same simplicity that makes Stockyard easy for users to run makes it possible for one developer to maintain 150 tools without burning out.

Know who's doing what.

Team ships with every Stockyard instance. Self-hosted or Cloud.

Start free Back to platform

Explore: Self-hosted proxy · OpenAI-compatible · Model aliasing