Deep Dive: Core Technology

Operational runtime-state control for customer-facing applications

Manage outages, degraded states, and maintenance windows from a centralized operational control system.

Core Engine

The Runtime State Engine

At the heart of RuntimeHQ lies our deterministic state resolver. Incidents and scheduled maintenance windows produce raw state events.

1

Deterministic Resolution

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

2

Centralized Computation

The engine computes the effective unified state in real-time, removing computation overhead from your micro-services.

3

Unified Edge Expositions

Resolved states are served instantly via globally replicated edge nodes to ensure 100% runtime availability.

Precedence Resolver Logic

Active Outage StateActive (Priority 1)
Scheduled Database MaintenanceOverruled
Resolved: Outage Overwrites
API Portal Degraded StateOverruled
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

Incident Operations

When systems degrade unexpectedly, speed is everything. Incident Commanders cannot waste time locating feature flag dashboards or scheduling code redeployments.

  • Fast Incident Activation: Trigger globally resolved outage state variables in under 1 second.
  • Multi-Application Coordination: Map a single operational state to 10+ endpoints and web portals simultaneously.
  • Pre-filled Warning Modals: Instant standard copy templates to ensure customer messages remain consistent.
Planned Schedule

Maintenance Windows

Standardize planned database maintenance, migrations, or upstream provider outages. 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. Pre-fill State Banner Message

"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 instant, verified timeline 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
Link applicationby M. Chen (Incident Cmd)

Linked Checkout API and Mobile Application 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 zero-layout-shift banner injections.

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 hook to automatically fetch, cache, and update UI state in your client components.

tsx
import { RuntimeProvider, useRuntimeState } from '@runtimehq/react';

// 1. Wrap your application root
export default function App() {
  return (
    <RuntimeProvider apiKey="rt_pub_prod_8f2d9c..." appId="app_checkout_prod">
      <CheckoutLayout />
    </RuntimeProvider>
  );
}

// 2. Consume effective state in any component
function CheckoutLayout() {
  const { state, message, isLoading } = useRuntimeState();

  if (state === 'outage') {
    return (
      <div className="bg-red-50 border-b border-red-200 p-3 text-center text-xs text-red-700">
        ⚠️ {message || 'Checkout is temporarily degraded. Our SRE team is investigating.'}
      </div>
    );
  }

  return <PaymentForm disabled={state === 'outage'} />;
}
Global Operational Command Center
Active 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 dashboard 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.
  • • Active Environments View: Track live states across production and non-production pipelines instantly.
  • • Security Integration: 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 runtime-state engine?
A runtime-state 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 runtime-state resolution where the most severe operational state wins during conflicts.
Can multiple applications be attached to one incident?
Yes. RuntimeHQ supports multi-application incident targeting to simplify operational coordination during production outages.
Does RuntimeHQ support degraded-state messaging?
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 runtime-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 runtime-state infrastructure. It focuses on runtime-state propagation and customer-facing operational visibility.
Architecture Review

Secure runtime-state control for your platforms

Protect production platforms, eliminate feature flag chaos, and ensure consistent outage communication globally. Schedule a dedicated SRE architecture review.

Book technical discussion

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

runtimehq-sre-shell
$ echo $SRE_EMAIL
Recommended Context

To help us prepare for our discussion, please share some context on your current outage banner workflow, such as:

  • Hardcoded banner deployments
  • Toggling CMS content manually
  • Editing feature flags during active incidents