Infrastructure & Hosting
Cloud Infrastructure
- Hosted on enterprise-grade cloud infrastructure providers
- Production infrastructure isolated from non-production environments
- Infrastructure designed for high operational availability
- Runtime-state APIs optimized for low-latency delivery
Geographic Hosting
- Primary infrastructure region strategy defined during onboarding
- Future support planned for regional deployment preferences and data residency requirements
Operational Availability Goals
- Runtime-state APIs designed for high availability
- Operational control systems monitored continuously
- Recovery-oriented infrastructure philosophy
Encryption & Network Security
Transport Security
- HTTPS/TLS enforced across all public endpoints
- Secure API transport required for all integrations
- Modern TLS standards applied to external communication
Encryption At Rest
- Application data encrypted at rest
- Operational metadata encrypted using managed infrastructure security controls
- Backup encryption practices applied where supported
Credential Handling
- Passwords stored using industry-standard hashing algorithms
- API keys securely generated and isolated per environment
- Sensitive credentials never exposed in operational logs
Authentication & Access Control
Access & Session Rules
Reliable Incident Access
Email/password authentication is supported, alongside secure magic-links as a secondary login method to ensure SREs maintain access during external SSO degradations.
Organizational Limits
Access is strictly restricted to onboarded organizations only. The MVP operates a simplified Org-wide Operational Admin model, where authorized admins can invite additional admins within verified domains.
Session Management
Secure session expiration and token handling are strictly enforced, alongside operational login activity audits.
Future Identity Roadmap
We are actively scheduling enterprise identity federation integrations on our roadmap:
Auditability & Operational Logging
Operational Audit Logging
RuntimeHQ maintains a comprehensive, audit-ready operational history of actions:
Immutable Operational History
- Operational history is designed to be append-only where possible
- Actor identities and absolute timestamps are preserved for COE reconstruction
Timestamp Standards
- All timestamps are recorded internally as UTC in the database
- UI displays localized local organizational time contexts
Runtime Safety Controls
Environment Separation
- Production and non-production API keys are strictly separated
- Non-production runtime state testing is isolated from production triggers
- Safe workflows prevent accidental production incident activations
Engine Protections
- Deterministic runtime-state resolution model
- Most severe operational state wins during conflicts
- Runtime-state propagation controlled centrally
Concurrency Protection
- Optimistic concurrency protections protect active incidents against overwrites
- Designed to facilitate simultaneous multi-admin incident mitigations
Data Management
Operational histories are retained for audit. Archived apps are preserved to protect audit timeline integrity.
Periodic, encrypted backups are executed and recovery procedures operationally verified.
Recovery-oriented design ensures continuous edge delivery of runtime states during major cloud incidents.
Privacy & Data
We only collect app identifiers, operational messages, and runtime states. We do not ingest customer end-user PII.
Full support for access workflows, customer deletion request handling, and data privacy operations.
Regional database hosting preferences and isolated storage pools are defined on our roadmap.
Vulnerabilities
We encourage security researchers to coordinate reports on authentication, credentials, and state vulnerabilities.
Reports are reviewed promptly and coordinate mitigations managed diligently based on operational triage severity.
Operational Reliability
Availability Target: Standard API target is 99.9% availability. Edge node groups are continuously monitored to ensure dependability.
Incident Response Philosophy: The delivery mechanism is designed to remain operationally isolated and fully functional even when central command dashboards undergo database mitigations.
Maintenance Policy: Production-impacting maintenance events are avoided where possible, with mandatory notifications delivered in advance.
Future Security Roadmap
Trust & Security FAQ
Review disclosures regarding transport encryption, data isolation, and our minimal PII footprint strategy.
Is RuntimeHQ secure for enterprise operational workflows?
Does RuntimeHQ encrypt data at rest?
Does RuntimeHQ support HTTPS and TLS?
Where is RuntimeHQ hosted?
Does RuntimeHQ support SSO?
Does RuntimeHQ maintain operational audit logs?
Can RuntimeHQ customers choose hosting regions?
Does RuntimeHQ store customer end-user personal data?
Does RuntimeHQ support environment isolation?
Secure runtime-state control for your platforms
Schedule a dedicated security and architecture review with our reliability engineering team. Let's evaluate safe integration practices.
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