The Runtime State Engine
At the heart of RuntimeHQ lies our deterministic state resolver. Incidents and scheduled maintenance windows produce raw state events.
Deterministic Resolution
Most severe operational state wins in case of conflicts (Outage > Degraded > Maintenance > Operational).
Centralized Computation
The engine computes the effective unified state in real-time, removing computation overhead from your micro-services.
Unified Edge Expositions
Resolved states are served instantly via globally replicated edge nodes to ensure 100% runtime availability.
Precedence Resolver Logic
"Card processing experiencing minor disruptions. SRE team actively mitigating."
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.
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
Set: Checkout API, Start: Saturday 22:00 UTC, Duration: 2 Hours.
"Database migration in progress. Billing services will resume at 00:00 UTC."
At 22:00, global edge endpoints automatically swap active state to "maintenance". Resolves back to healthy at 00:00.
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)
Append Operational Note
Timeline entries are strict and append-only for SRE auditability. Pinned notes dynamically populate the Correction of Error (COE) report timeline.
Deterministic priority engine resolved: App Checkout Outage state takes precedence over database scheduled maintenance window.
Confirmed payment gateway connection pools exhausted. Third-party provider Stripe resolving their DNS issues.
Linked Checkout API and Mobile Application to Incident #INC-4022.
Activated OUTAGE state for app Checkout API. Message: "Credit Card processing is experiencing service anomalies. SRE is resolving."
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.
React SDK Integration
Use our native React hook to automatically fetch, cache, and update UI state in your client components.
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'} />;
}Active States
Checkout Service API
Message: payment clusters isolated.Saturday DB Migrate
22:00 - 00:00 UTC
All Sandboxes Safe
4 active environments
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.
Product Architecture FAQ
Review complete details regarding conflict resolution, API performance, and state propagation constraints.
What is a runtime-state engine?
How does RuntimeHQ handle conflicting operational states?
Can multiple applications be attached to one incident?
Does RuntimeHQ support degraded-state messaging?
Can RuntimeHQ be used with React or Next.js?
Does RuntimeHQ provide UI banner components?
Can RuntimeHQ support non-production testing?
How does RuntimeHQ improve incident operations?
Is RuntimeHQ an incident management platform?
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.
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