An OEM integration puts Runstamp behind a software company's own customer experience. The order and architecture must state:
- local, managed, or private execution topology;
- tenant isolation, credentials, data flow, retention, and deletion;
- allowed operations, profiles, formats, application versions, and capacity;
- any negotiated embedding and redistribution terms for identified commercial components and services; Apache-2.0 rights remain governed by their licenses;
- artifact, evidence, webhook, and incident interfaces;
- Runstamp and customer support boundaries;
- change control, version support, service levels, security review, and exit plan.
The default Enterprise allowance is zero until an executed order sets the organization's entitlement. VPC deployment, SSO/SAML, SCIM, residency, 24x7 support and service credits are not implied by the Enterprise name.