Team plan
Get your team running with evidence-first AI investigations
Managed setup, custom knowledge base, and hands-on onboarding for growing engineering orgs.
$299 AUD / month
Up to 10 engineers · month-to-month · cancel anytime
$2,990 Pay annually — 2 months free
Pricing by team size
Up to 10 engineers
$299 AUD
or $2,990 AUD / year
Best for a single squad or platform team
11–25 engineers
$499 AUD
or $4,990 AUD / year
Multiple squads sharing one service registry
Compare plans
Open Source vs Team
| Feature | Open Source | Team |
|---|---|---|
| Service registry & knowledge base | ✓ | ✓ |
| Investigation prompts & workflows | ✓ | ✓ |
| Custom registry setup for your repos | — | ✓ |
| Knowledge base scaffolding | — | ✓ |
| Live team brown-bag (90 min) | — | ✓ |
| Office hours (2× in month one) | — | ✓ |
| Onboarding runbook | — | ✓ |
| Priority email support (1 business day) | — | ✓ |
| 30-day launch support | — | ✓ |
| Community / self-serve only | ✓ | — |
What's included
Everything you need to go live
Everything in Open Source
Full workbench — service registry, prompts, workflows, and compose templates.
Custom service registry
We map your repositories, services, and local checkout layout into `service-registry.yaml`.
Knowledge base scaffolding
Starter architecture docs, integration notes, and glossary tailored to your domain.
Team onboarding brown-bag
90-minute live session: investigation workflow, evidence-first output, and compose drafts.
Office hours
Two 45-minute follow-up sessions in your first month for questions and tuning.
Priority email support
Responses within one business day for setup, workflow, and troubleshooting questions.
Onboarding runbook
A written guide your team can follow after go-live — prompts, examples, and conventions.
30-day launch support
Hands-on help while your team adopts the workbench across real enquiries.
Onboarding
Four weeks to go-live
A clear timeline with deliverables at every step — from registration to ongoing support.
Register your team
5 minutesSubmit the registration form with your company, role, team size, repos, and preferred kickoff window.
Deliverable: Registration received
Confirmation & kickoff
30 min callWe confirm within one business day, send an invoice or agreement, and schedule a 30-minute kickoff call.
Deliverable: Kickoff scheduled + access checklist
Registry & knowledge setup
1–2 sessionsTogether we configure your service registry, sibling repo paths, and starter knowledge docs for your domain.
Deliverable: Configured `service-registry.yaml` + knowledge stubs
Team training brown-bag
90 minutesLive session for your engineers: run a real enquiry end-to-end — evidence, risk, recommendation, compose draft.
Deliverable: Recorded session + shared slides
Go-live & office hours
2× 45 minYour team runs real investigations. Two office-hour sessions cover tuning, edge cases, and workflow gaps.
Deliverable: Tuned prompts + team runbook
Priority support
MonthlyEmail support continues on your Team plan. Upgrade to Enterprise for SSO, custom integrations, and SLA.
Deliverable: 1 business day response SLA
Support
Priority help when you need it
- Channel
- iman.suherman@gmail.com
- Response SLA
- Within 1 business day
- Launch blockers
- Same day for launch blockers (first 30 days)
- Hours
- Mon–Fri, 9am–5pm AEST/AEDT
- Escalation
- Reply with [URGENT] in the subject for launch blockers during your first month.
Included
- ✓ Setup and configuration questions
- ✓ Workflow and prompt tuning
- ✓ Registry and knowledge base updates
- ✓ Brown-bag and office-hour scheduling
- ✓ Compose template customisation
- ✓ Launch blocker triage (first 30 days)
Not included
- — Application code changes in your product repos
- — On-call incident response or pager duty
- — Custom agent, MCP, or integration development
- — SSO, compliance, or enterprise SLA (see Enterprise plan)
FAQ
Common questions
How does registration work?
Submit the registration form on this page. You receive a confirmation email and we notify our team at iman.suherman@gmail.com. We confirm within one business day and send next steps.
Do you store my form data?
Form submissions are sent by email only — we do not store registration data in a database on workbench.suherman.net.
Do we need Jira or ServiceNow to use the workbench?
No. Setup is clone + fill service-registry.yaml + investigate. Jira is optional: paste tickets for analysis, or sync open incidents with an API token into context/active-incidents.md. See /setup and knowledge/integrations/jira.md.
Where does the service registry come from — Terraform or Helm?
The registry is always knowledge/service-registry.yaml. Draft from sibling folders, gh, Terraform/Helm hints, or by hand. For many repos use the unitized bootstrap (plan + one service per turn) so quota limits do not kill a half-finished setup — workflows/bootstrap-knowledge.md. Infra sources are discovery hints, not a live feed from Terraform state.
Do you offer Airflow or Jenkins for the incident → MR loop?
Open source defaults to 100% pull: on-call brings Docker up locally, passes a PagerDuty id, and multi-CJS retrieves context (npm run incident:stage:a|b|c). Paying Team/Enterprise can run 100% push: always-on Docker with a webhook URL you configure in PagerDuty so alerts hit an endpoint that runs the rest. Airflow/Jenkins are optional schedulers around the same stages. See knowledge/architecture/incident-pipeline.md.
Can we start on Open Source and upgrade later?
Yes. Many teams clone the repo first, then upgrade to Team when they want hands-on registry setup and training.
What do we need before kickoff?
A list of repositories and services your team investigates, who owns each, and at least one real enquiry you want the workbench to handle. Optional: Terraform/Helm paths or Jira access if you want those wired during onboarding.
How is billing handled?
Month-to-month by default. Annual billing saves two months. Invoice sent after kickoff confirmation.
Registration
Register your team
Tell us about your engineering team. We'll confirm within one business day and send a confirmation email.