Deep Dive: Core Technology

Operational State Control for Customer-facing Applications

Activate outages, degraded service, and maintenance states once. RuntimeHQ propagates them consistently across customer-facing applications while your teams retain full control over application behavior.

Core Engine

The Operational State Control Engine

RuntimeHQ serves as the operational state authority for customer-facing applications. Incidents and maintenance events create operational state changes that RuntimeHQ resolves, governs, and propagates consistently.

1

Deterministic Resolution

Most severe operational state wins in case of conflicts (Outage > Degraded > Maintenance > Operational).

2

Centralized State Authority

The engine computes the effective unified state in real-time, eliminating fragmented operational state handling across applications.

3

Global State Distribution

Operational states are propagated globally through low-latency edge infrastructure to ensure 100% runtime availability.

Precedence Resolver Logic

Active Outage StateActive (Priority 1)
Scheduled Database MaintenanceOverruled
Resolved: Outage Overwrites
API Portal Degraded StateOverruled
Architecture

Global Edge Architecture

RuntimeHQ is designed around asynchronous state computation and edge-distributed state delivery.

Outage Incident Trigger WorkflowProd Safe
1. Select StateDegraded or Outage
2. Link Impacted AppsPayments API, Mobile Checkout
3. Customer Copy

"Card processing experiencing minor disruptions. SRE team actively mitigating."

Crisis Action

Operational State Activation

When systems degrade unexpectedly, speed is everything. Engineering teams should not coordinate outages through feature flags, ad hoc dashboards, and manual application updates.

  • Fast State Activation: Activate outage, degraded, or maintenance states instantly across connected applications.
  • Impact Scope Coordination: Apply a single operational state across affected applications and operational impact scopes.
  • Operational Governance: Maintain consistent operational behavior across teams during outages and maintenance events.
Planned Schedule

Maintenance Windows

Govern planned maintenance events and operational state transitions from a centralized control plane. Seed state transitions in advance to minimize operational overhead.

Centralized Scheduling

Pre-seed exact start/end parameters for automatic edge propagation.

Auditability & COE Readiness

Every scheduled window keeps a detailed immutable log trace of who, when, and what changed.

Scheduled Maintenance Pipeline

1. Define Schedule & Target App

Set: Checkout API, Start: Saturday 22:00 UTC, Duration: 2 Hours.

2. Define State Metadata

"Database migration in progress. Billing services will resume at 00:00 UTC."

3. Automatic Edge Transitions

At 22:00, global edge endpoints automatically swap active state to "maintenance". Resolves back to healthy at 00:00.

Audits & COEs

The Operational Timeline

One of RuntimeHQ's strongest operational concepts. Generate authoritative operational timelines reconstructions for post-incident audits and Correction of Error (COE) reports.

Active Incident Timeline (Incident #INC-4022)

Timezone: Org Local (America/Central)
Append Operational Note

Timeline entries are strict and append-only for SRE auditability. Pinned notes dynamically populate the Correction of Error (COE) report timeline.

14:24:02
State Conflict Resolvedby System Resolver

Deterministic priority engine resolved: App Checkout Outage state takes precedence over database scheduled maintenance window.

14:22:15
Append operational noteby S. Jenkins (SRE)

Confirmed payment gateway connection pools exhausted. Third-party provider Stripe resolving their DNS issues.

14:18:40
Attach Impact Scopeby M. Chen (Incident Cmd)

Attached Checkout and Payments impact scopes to Incident #INC-4022.

14:15:10
Incident Startedby M. Chen (Incident Cmd)

Activated OUTAGE state for app Checkout API. Message: "Credit Card processing is experiencing service anomalies. SRE is resolving."

Integration

SDKs & Integrations

Technical trust requires simple and dependable implementation. Integrate with any technology using our native SDK wrappers or direct JSON edge APIs.

Native React & Next.js Support: Auto-caching, Server-side rendering (SSR), and low-latency operational state synchronization.

Environment Key Division: Unique production vs. non-production key environments to guarantee operational testing stays isolated safely from production.

CDN Edge Enabled

React SDK Integration

Use our native React provider and hook to automatically fetch, cache, and update UI state in your client components.

tsx
import { RuntimeHQProvider, useRuntimeHQ } from "@theruntimehq/react";

// 1. Wrap your application root with the provider
export default function App() {
  return (
    <RuntimeHQProvider runtimeKey="rt_prod_xxxxx" intervalSeconds={60}>
      <SearchComponent />
    </RuntimeHQProvider>
  );
}

// 2. Consume dynamic state changes reactively in components
function SearchComponent() {
  const { loading, error, getCapabilityState } = useRuntimeHQ();

  if (loading || error) return null;

  const searchCapability = getCapabilityState('search');
  const isSearchDown = searchCapability?.state === "OUTAGE";
  const isSearchDegraded = searchCapability?.state === "DEGRADED";

  return (
    <div className="search-container">
      <input 
        type="text" 
        placeholder="Search products..." 
        disabled={isSearchDown}
      />
      {(isSearchDown || isSearchDegraded) && (
        <p className={`helper-message ${isSearchDown ? 'text-red-600' : 'text-amber-600'}`}>
          ⚠️ {searchCapability.message}
        </p>
      )}
    </div>
  );
}
Global Operational Command Center
Active Operational States
Checkout Service API
Message: payment clusters isolated.
Outage
Upcoming Maintenance
Saturday DB Migrate

22:00 - 00:00 UTC

Staging Keys status
All Sandboxes Safe

4 active environments

Control Surface

The Operational Dashboard

The dashboard is not the product itself - it is a dedicated control surface. Our console is designed to feel dense, focused, and immediately scannable for engineering teams acting under outage stress.

  • • High Information Density: Built for fast operational awareness, not visual decoration.
  • • Operational State Visibility: Track live states across production and non-production pipelines instantly.
  • • Governance & Audit Controls: Ready to plug into security frameworks for enterprisewide compliance.
FAQ

Product Architecture FAQ

Review complete details regarding conflict resolution, API performance, and state propagation constraints.

What is a operational state control engine?
A operational state control engine computes effective live application state based on incidents and maintenance windows. RuntimeHQ determines the final operational state consumed by applications.
How does RuntimeHQ handle conflicting operational states?
RuntimeHQ uses deterministic operational state resolution where the most severe operational state wins during conflicts.
Can multiple applications be attached to one incident?
Yes. RuntimeHQ supports operational state coordination across applications to simplify operational coordination during production outages.
Does RuntimeHQ support degraded operational states?
Yes. RuntimeHQ supports: • operational • degraded • outage • maintenance runtime-state types.
Can RuntimeHQ be used with React or Next.js?
Yes. RuntimeHQ provides integration references and SDK guidance for: • React • Next.js • React Native • custom frontend systems
Does RuntimeHQ provide UI banner components?
RuntimeHQ primarily provides APIs and SDKs so organizations can render runtime state using their own design systems and UI components.
Can RuntimeHQ support non-production testing?
Yes. RuntimeHQ supports production and non-production API key separation to safely test operational state workflows.
How does RuntimeHQ improve incident operations?
RuntimeHQ reduces operational friction by centralizing: • runtime-state activation, • customer banner copy, • application targeting, • operational visibility, • audit history.
Is RuntimeHQ an incident management platform?
No. RuntimeHQ is operational state infrastructure. It focuses on operational state propagation and customer-facing operational visibility.
Architecture Review

Establish a single source of operational state

Eliminate fragmented operational response. Activate outages, degraded service, and maintenance states once, then propagate them consistently across customer-facing applications.

Book technical discussion

Connect directly with our architects to evaluate integration feasibility. No sales pitch.

runtimehq-shell
$ echo $ARCH_EMAIL
Recommended Context

To make our discussion more productive, tell us a little about your current operational workflow.

  • Manual operational coordination
  • Feature flag-based operational controls
  • Application-specific outage handling