Partner accounts: SHDWsdk for every customer of your platform
Integrations & Data Sources
#partner#oem#platform#multi-tenant#client organizations#org_slug#reseller
Platforms can give each of their customers their own SHDWsdk organization, trust page and statements, managed from one account and fed by one key.
How It Works Under the Hood
- •A partner account manages client organizations. Each client has its own audit log, AI-BOM, statements, sign-in policy and trust page (private until published).
- •Partner owners and admins administer every client. A client's MFA requirement applies to them; a client's SSO requirement doesn't, because they sign in through the partner.
- •One partner key sends data for every client: each event carries org_slug. Each client has its own audit chain and rate limit, and an unknown slug is rejected rather than written anywhere else. Partner keys get five times the request rate.
- •Clients inherit the partner's plan and follow it when it changes.
How to Use It Step-by-Step
- 1Ask us to enable partner access for your organization (partners@shdwsdk.ai).
- 2Add client organizations in Dashboard → Clients.
- 3Send each client's events with your partner key and org_slug set to the client's slug.
Routing events to a client organization
// JavaScript
resolveContext: () => ({ orgSlug: tenant.shdwSlug, customerRef: tenant.id })
# Python
with shdwsdk.organization("firm-one"):
...
# OpenTelemetry attribute
shdw.org_slug = "firm-one"Related guides
- Python SDK, OpenTelemetry and LiteLLM
- Data completeness: reconcile with provider billing
- Alerts: Slack and signed webhooks
- Developer console: pipeline health, drop rates and live events
- Carbon accounting export and cost/carbon savings
- Deployment and model coverage: clouds, private hosting and self-hosted models
- Interactive CLI Setup Wizard (npx @shdwsdk/sdk init / npx shdw-init)
- Non-Blocking Client Wrapper (shdw.wrapClient) & Fail-Silent Guarantee
