KrewOS Hub
A catalogue, not a marketplace.
Verified Agents, Pods, Crew Templates and Packs — classified across fourteen dimensions, versioned, dependency-locked and tested. Reuse is the point, and verification is what makes reuse safe.
Browsing is public. Using a component requires a workspace.
- Agents
- Pods
- Crew Templates
- Packs
- Agents
- 218
- Single roles with typed contracts
- Pods
- 74
- Coordination patterns over Agents
- Crew Templates
- 31
- Complete runnable outcomes
- Packs
- 4
- Licensed vertical bundles
Verification tiers mean something specific.
A badge is worthless unless the bar behind it is published. Here is exactly what each tier required.
| Tier | What it required | Usable in production |
|---|---|---|
| Draft | Manifest validates and compiles. Nothing else. | No |
| Tested | Publisher-supplied evaluation suite present and passing at a declared threshold, with the dataset visible to entitled tenants. | Development only |
| wGrow verified | Independent review of the manifest, effect declarations, permission scope, prompt-injection surface and evaluation methodology. Re-verified on every minor version. | Yes |
| Tenant verified | Your organisation’s own review process signed off by your named component owner. Scope and reviewer recorded. | Yes, within your tenant |
| Deprecated | Superseded or withdrawn. Existing pinned uses continue; new installs are blocked and owners are notified. | Existing pins only |
Use, configure or fork.
Three modes with different upgrade behaviour and different ownership. Compatible updates may be recommended, but they are never installed silently.
| Mode | What you get | Updates | Who owns correctness |
|---|---|---|---|
| Use | The published component at a pinned version, unmodified. | Compatible updates recommended in your inbox; you choose when to move. | The publisher |
| Configure | The same component with the publisher’s declared configuration surface set to your values. | Same as Use. Your configuration is carried forward and revalidated. | Publisher for behaviour, you for configuration |
| Fork | A private copy you can change without limit, with lineage recorded back to the source. | Upstream changes appear as a diff you may merge. Never automatic. | You, from the moment of the fork |
Classification is the search index.
Every component is classified on the same dimensions, which is why filtering across two hundred components is useful rather than exhausting.
Industry Jurisdiction Language Risk level Human control level Input type Output type Connector dependency Quality status Model class required Declared effects Evidence floor Cost band Publisher
Private tenant catalogues
Your own verified components stay yours. Publish to your organisation without publishing to the world, with the same verification workflow, the same classification and the same dependency locking.
Dependency locks
A Crew Template pins the exact versions of every Agent, Pod, Knowledge Pack and policy it depends on. A release is a checksummed closure, not a pointer to whatever is current.