Managing Applications

Applications are the core entities in RuntimeHQ. Once registered, you can manage their operational state, configure user-facing capabilities, and retrieve the keys needed to integrate with our SDKs.

Application Capabilities

Capabilities represent specific user-facing modules or business operations mapped to your application (e.g., payments, claims, transfers).

From the Overview tab of any Application Details page, you can:

• Add Capabilities: Declare new modules that you want to track independently.
• Archive Capabilities: Safely deprecate capabilities without losing historical data.

Capability Naming Conventions

Capability names are used directly by SDKs for runtime state evaluation and comparisons. Keep them short, crisp, and meaningful:

• Simple names: Ideal for standalone modules, such as payments, claims, or transfers.
• Dot notation grouping: If you plan to create multiple related capabilities within a domain, dot notation convention can be used for grouping based on your needs:
  • payments.card-processing
  • payments.ach
  • payments.digital-wallet
  • payments.wire-transfers

Note: Because capability names are consumed directly by client SDKs for runtime comparisons, capability renaming is disabled once created.

Integration & Runtime Keys

The Integration tab provides access to your Runtime Keys. These keys have a strictly read-only scope for the application's runtime operational state and are safe to expose in public or browser environments.

• Production Key: Used for live environments.
• Non-Production Key: Used for staging, testing, and local development.

Non-Production Simulation

To test how your application reacts to outages or degraded conditions without affecting production traffic, you can use the Non-Production Simulation State. This allows you to override the operational state (e.g., simulating Degraded, Outage, or Maintenance states with custom operational messages and capability targeting) exclusively for clients using the application's Non-Production Key.

For full workflow details, peacetime drill scenarios, and edge verification steps, see the dedicated Non-Production Simulation guide.