Deployment models
Choose the model that matches your account ownership, billing, security, and operational requirements.
Clients register in the control panel and launch on HFTCloud-operated resources. HFTCloud owns the underlying cloud account boundary and provides one invoice.
Clients register in the control panel, provide scoped API access, and launch the runtime in their own AWS account while keeping direct infrastructure billing.
Clients register in the control panel, download the package, and operate the runtime inside their own environment. This is the highest-control model and usually requires earlier review.
Control panel workflow
Register once, then use the same control panel to launch, authorize, or download depending on the operating model.
Register the team and set the first benchmark scope.
Choose Managed Cloud, Customer Cloud, or Self-Hosted before rollout.
Provide scoped AWS access for BYOC or download the package for self-hosted rollout.
Move from benchmark result to production launch without changing the benchmark logic.
Who owns what
| Decision area | Managed Cloud | Customer Cloud (BYOC) | Self-Hosted |
|---|---|---|---|
| Account ownership | HFTCloud | Customer AWS account | Customer environment |
| Who pays infrastructure providers | HFTCloud | Customer | Customer |
| Who pays HFTCloud | Customer | Customer | Customer |
| Control panel action | Launch on HFTCloud resources | Enter scoped API access and launch | Download package and deploy internally |
| NDA timing | Later if needed | Earlier in some cases | Usually early |
| Operational burden | Lowest | Medium | Highest |
Security & NDA path
Initial qualification can begin with public-safe information. Sensitive venue, provider, route, and deployment details are introduced under NDA when required.
Public-safe qualification can begin without an NDA. Venue-sensitive details are introduced when the rollout scope requires them.
Scoped access, customer AWS policy, and direct provider relationships often move the NDA step earlier.
Package review, internal deployment constraints, and software distribution usually require the earliest NDA stage.
Confidential details are shared only within the qualified project workflow and under the applicable NDA.
Select the Deployment Model
Review the measured recommendation, then select the model that matches your team’s control and operating requirements.