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.

Tango Vision employees: sign in with your staff account

If you work at Tango Vision you already have an account — the company staff account you use for the other internal tools (the hub realm at auth.tangovision.dev). Don't ask for a developer account and don't register one: on the developer sign-in page click Tango Vision staff, sign in with your staff credentials, and a developer account is created for you on the spot, linked to your staff identity.

1. Open the developer portal and click Sign in.
2. On the "Sign in to Tango Vision Developers" page click Tango Vision staff (under the email/password form).
3. Sign in on the "Tango.Vision Employees" page with your staff account.
4. Accept the Developer Terms of Service once.

You land back in the portal, signed in. Your email is already verified (it is trusted from the staff realm), your account carries the developer role, and because your staff email is on a company domain you sit on the internal quota tier — 20 concurrently-active sandboxes instead of 3. Everything else works exactly as for external developers: mint keys in the portal, or npx @tv/extension-sdk login and pick the same Tango Vision staff button in the browser it opens (CLI sign-in).

Two things SSO does not give you

• A registry token. @tv/* packages — including the SDK CLI you scaffold modules with — come from the private registry, which has no SSO. Ask the platform team for a Verdaccio token (operator runbook: registry-developer-credentials) before running Getting started.
• Admin rights over other developers' keys. A staff session manages its own org only. Cross-org key management (listing or revoking an external developer's keys, minting for another org) needs the developer_admin realm role, granted to reviewers on request.

Already invited as an external developer with the same email before SSO existed? The first staff sign-in offers to link the two accounts — confirm with your existing developer password and keep one account.

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 (employees: use the Tango Vision staff button instead — see above):

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?

Two developers working on one sandbox: see Two developers, one sandbox. An internal-tier key or a raised key cap: write to the contact named in your welcome message, by email or Telegram; developers@tango.vision reaches the same people.

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.