Judoscale Authentication

generated: '2026-10-26'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://judoscale.com/docs/heroku-getting-started
sources:
- https://judoscale.com/docs/heroku-getting-started
- https://judoscale.com/docs/aws-getting-started
- https://judoscale.com/docs/fly-getting-started
- https://judoscale.com/docs/railway-getting-started
description: Authentication methods for Judoscale as documented on the provider pages.
schemes:
- type: oauth2
  name: Heroku OAuth
  evidence: Jud​oscale integrates with Heroku via OAuth , which grants access to all of your teams and apps (sadly), but after granting access
    you’ll come back to Judoscale and choose which team(s) and app(s) to link for autoscaling.
  how_to_obtain: Click “Authenticate with Heroku” which redirects to Heroku’s authorization screen where you authorize Judoscale to access your
    account.
- type: apiKey
  name: Fly Organization Token
  evidence: Jud​oscale needs your Organization Token in order to fetch apps and machines information, and create/destroy machines when autoscaling.
  how_to_obtain: Generate a new token in the Fly dashboard under “Tokens”, name it “Judoscale”, and paste it into Judoscale’s Connect to Fly form.
- type: apiKey
  name: Railway Team Token
  evidence: Jud​oscale needs your Team Token in order to fetch project environments and services information, and update the number of running
    replicas.
  how_to_obtain: Create a new Team token in Railway account settings, name it “Judoscale”, and paste it into Judoscale’s Connect to Railway form.
docs: https://judoscale.com/docs/heroku-getting-started