Review how LoadStrike handles self-hosted execution, licensing metadata, runtime access checks, and website data collection.
LoadStrike runs self-hosted in customer-controlled environments, while licensed execution uses hosted licensing services for runtime access checks and, for the Go SDK, runtime delivery.
Those services exchange runner, environment, version, and entitlement metadata rather than application request or response payload bodies. LoadStrike also stores the customer, billing, runner-binding, lease, and audit records needed to enforce license access and runtime limits.
Security, procurement, platform, and architecture teams evaluating what the LoadStrike-hosted control plane receives during licensed execution.
Enterprise reviews usually slow down when product pages stay high-level and the data-handling story is spread across multiple technical surfaces. This page brings the core licensing and website-handling picture into one buyer-facing summary.
This page connects the self-hosted product model to the licensing and website data used to operate the service, so teams can separate runtime execution in their own environment from the account, access, and support data handled by LoadStrike.
These public pages connect the control-plane explanation back to the documented product and buying path.
Read the technical documentation for runner validation, environment rules, and runtime access.
Review the self-hosted commercial model and runner-key plan framing.
Separate website analytics and contact-form handling from runtime licensing data.
Use the security and compliance contact path for follow-up review.
No. Runtime access checks use runner, environment, version, and entitlement metadata rather than application request or response payload bodies.
Start with this page and the licensing and runtime access docs, then contact LoadStrike if your review needs questionnaires, procurement follow-up, or negotiated terms.
Website analytics and contact-form handling are documented separately on the website privacy page so they can be reviewed independently from product runtime access and licensing data.
Start with the implementation details that match this page.
This page explains how runner keys control runtime access. Read it when you need to understand the runner-key requirements, licensing surface, and the runtime-access fields involved.
Cluster mode lets one LoadStrike run spread across multiple nodes. Use it when a single machine is not enough or when topology matters.
Build one basic request-step scenario around GET /orders/{id}, run it, and confirm the report before moving into correlation-specific features.
Keep moving with the most relevant follow-up pages.
Use this page as the public starting point for security and procurement review, then move into the licensing docs or contact the LoadStrike team when the evaluation needs deeper review.
