bandsaas-cli

bss

Platform management for BandSaaS. Tenant admin, analytics, support tickets, funnel tracking - from the terminal.

Install

npm install -g bandsaas-cli

Quick Start

# Login with your SuperAdmin API key
bss login --key YOUR_SA_API_KEY

# Platform dashboard
bss stats

# Revenue metrics
bss revenue

# Signup funnel
bss funnel

# List all tenants
bss tenants

# View a tenant
bss tenant show TENANT_ID

# Support tickets
bss tickets
bss ticket show TKT-abc123

# Chat with τAI h-conductor
bss tai "show me open P0 bugs" --dept dev

# AI Licensing (A2A copyright moat)
bss licensing crosswinds                 # licensing overview for a band
bss licensing crosswinds register        # register a track by ISRC
bss licensing crosswinds issue           # issue a scoped AI licence
bss licensing crosswinds access-log      # provable access log (granted + blocked)

# Compliance evidence
bss compliance                           # snapshot (posture + frameworks + A2A events)
bss compliance posture                   # CISO posture score (0-100)
bss compliance frameworks eu-ai-act      # framework assessment
bss compliance audit-events --filter blocked
bss compliance export --format json      # export the OCSF audit log

# Full reference
bss help

Features

• Dashboard - tenant counts, user stats, post/order totals
• Revenue - MRR, ARR, platform fees, payouts
• Funnel - signup → verified ($1) → active → paying
• Tenants - list, view, suspend, activate
• Support - tickets, reply, close
• τAI Chat - talk to h-conductor (6 departments: dev, devops, bizintel, compliance, helpdesk, fixer)
• AI Licensing - register tracks by ISRC, issue/revoke per-use AI licences, provable access log (the A2A copyright moat)
• Compliance - posture score, framework assessment (EU AI Act, NIST AI RMF, SOC 2, Colorado SB24-205, GDPR), OCSF audit-event stream + export

Compliance-for-agents parity

The same AI-licensing and compliance surface is exposed to per-band agents over the remote MCP server (mcp.bandsaas.com, v1.3.0, 46 tools). An agent authenticated with a band-scoped bsk_ key gets read-only bandsaas_compliance, bandsaas_compliance_posture, bandsaas_compliance_frameworks, bandsaas_compliance_audit_events and bandsaas_compliance_export tools — a per-band mirror of the bss compliance commands here (which run platform-wide via the SuperAdmin API). Same evidence, two front doors: this CLI for platform operators, the remote MCP for a band's own agent.

Config

bss login --local --key YOUR_KEY    # saves to .bss/config.json (project-local)
bss login --key YOUR_KEY            # saves to ~/.bss/config.json (global)
bss config                          # show which config is active

Local config overrides global. Add .bss/ to your .gitignore.

Agent Integration

Add to your CLAUDE.md or agent instructions:

## BandSaaS Admin
Use the bss CLI for platform management.
Key is in .bss/config.json (auto-loaded).
Run bss --help for full reference.

JSON Output

All commands support --json for machine-readable output:

bss stats --json
bss tenants --json
bss tickets --json

Documentation

• BandSaaS
• Roadmap

License

Proprietary - Tyga.Cloud Ltd. See LICENSE.