Red Planet Labs · Authentication Profile

Red Planet Labs Authentication

Authentication

Authentication profile for Rama's built-in REST API. Rama is deployed by the user onto their own cluster; the REST API documentation describes no application-layer authentication scheme (no API key, token, OAuth, or mTLS). Access is expected to be governed at the network/deployment boundary of the self-hosted cluster rather than by the API itself.

Red Planet Labs secures its APIs with none across 0 declared security schemes, as derived from its OpenAPI definitions.

CompanyEnterprise SaasBackend PlatformDistributed SystemsDatabaseJVMClojureJavaDeveloper ToolsRama
Methods: none Schemes: 0 OAuth flows: API key in:

Security Schemes

Source

Authentication Profile

red-planet-labs-authentication.yml Raw ↑ 
generated: '2026-07-21'
method: searched
source: https://redplanetlabs.com/docs/~/rest.html
description: >-
  Authentication profile for Rama's built-in REST API. Rama is deployed by the
  user onto their own cluster; the REST API documentation describes no
  application-layer authentication scheme (no API key, token, OAuth, or mTLS).
  Access is expected to be governed at the network/deployment boundary of the
  self-hosted cluster rather than by the API itself.
summary:
  types:
  - none
schemes: []
notes: >-
  Because Rama is self-hosted software rather than a public cloud API, there is no
  vendor-issued credential. Operators are responsible for network isolation,
  firewalling, and any reverse-proxy authentication placed in front of Supervisor
  daemons and the Conductor UI (default port 8888).
docs: https://redplanetlabs.com/docs/~/rest.html