Developer account & access

To build modules against the Tango Vision platform you need a developer account. It's separate from any building-tenant login — developers live in their own identity realm and never get access to tenant data.

Register

Invite-only during the preview

Self-registration is currently closed while the developer platform is in preview. To get a developer account, write to developers@tango.vision — we create the account for your email address, and you receive an email with a link to verify the address and set your own password (minimum 12 characters; can't match your email).

Three things happen when your account is set up, in order:

1. Email verification. We email you a link; click it to confirm the address is yours. You can't sign in until you do.
2. Terms of Service. On first sign-in you must accept the Developer Terms of Service. This is a one-time action.
3. developer role. Once verified, your account carries the developer role automatically — that's what authorizes you against developer-facing services.

Sign in

After verifying, sign in at the same realm:

https://auth.k8s.tangovision.dev/realms/developers/account

Lost your password? Use Forgot password on the sign-in page — a reset link goes to your verified email.

Get a sandbox API key

Module work happens against an on-demand sandbox, which you reach with a sandbox API key (a tvk_… bearer token for sandbox-api.k8s.tangovision.dev).

Mint keys yourself in the developer portal: sign in with your verified account and mint org-scoped keys — no email round-trip. You'll get the plaintext token once; store it in your secret manager immediately. Keys carry a scope (sandbox by default) and expire after 90 days. Up to 5 active keys per org; revoke unused ones in the same place.

Need something non-standard?

A shared org for several developers, an internal-tier key, or a raised key cap still go through developers@tango.vision.

Once you have a key, follow Getting started to scaffold your first module, or jump straight to On-demand sandboxes.

What your account can and can't do

• ✅ Register sandboxes and develop modules against them.
• ✅ Hold org-scoped API keys for the sandbox provisioner.
• ❌ Access any production building tenant or its data. The developer realm is isolated from tenant SSO by design — see the boundary-of-responsibility doc.