Skip to main content

​
Account, license, and API key

Manage users and API keys on your Engine. A Registry account does not grant access to other companies’ Engines. Direct HTTP integrations use X-API-Key.

​
Sign in

Open your Threadify dashboard and choose a sign-in method:
  • Continue with email or SSO to sign in with your account.
  • Sign in with API key to create a browser session with that key’s permissions.
The license owner can sign in immediately. Everyone else must first be invited from Team with an admin, member or viewer role. Share the sign-in link shown by Threadify; invitation emails are not sent automatically. Browser sessions expire after eight hours. Signing out, suspending the user or revoking the source API key invalidates the session.

​
API keys

Open Developer → API Keys to create credentials for SDKs, OpenTelemetry and automation. Use a service account with only the permissions the integration needs. For the CLI, run:
See the CLI guide for headless login and environment-variable setup.

​
Self-host configuration

Set your license key and public dashboard address in config.yaml:
Point your HTTPS reverse proxy at the Engine port. The dashboard and API are served from that address; host the dashboard at the root of the hostname. browser_origin must match the origin you open in the browser. For local use, keep the hostname consistent: choose either localhost or 127.0.0.1. Administrators can override server.public_url in Settings → Engine → Engine URL. UI changes apply immediately; config changes require a restart.