Deployment models

One benchmark workflow. Three rollout contours.

Use this page to choose the operating model that fits your control boundary, billing policy, and internal deployment requirements.

View Pricing Open Control Panel
Managed Cloud Customer Cloud (BYOC) Self-Hosted

Fastest rollout

Managed Cloud

Clients register in the control panel and launch on HFTCloud-operated resources. HFTCloud owns the underlying cloud account boundary and provides one invoice.

  • Shortest path from benchmark to production
  • Lowest operational burden for the client
  • Best fit for teams that want a single counterpart

Client AWS account

Customer Cloud (BYOC)

Clients register in the control panel, provide scoped API access, and launch the runtime in their own AWS account while keeping direct infrastructure billing.

  • Cloud spend and policy stay with the customer
  • HFTCloud provides orchestration and tuning
  • Best fit for teams with existing procurement and platform policy

Inside your own contour

Self-Hosted

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.

  • Package deployment inside the client perimeter
  • Highest control and isolation
  • Best fit for mature internal operating models

Control panel workflow

The control plane stays consistent across all three models

Register once, then use the same control panel to launch, authorize, or download depending on the operating model.

1

Create the workspace

Register the team and set the first benchmark scope.

2

Pick the model

Choose Managed Cloud, Customer Cloud, or Self-Hosted before rollout.

3

Authorize or download

Provide scoped AWS access for BYOC or download the package for self-hosted rollout.

4

Launch the approved runtime

Move from benchmark result to production launch without changing the benchmark logic.

Who owns what

Account boundary, billing, and review path

Decision areaManaged CloudCustomer Cloud (BYOC)Self-Hosted
Account ownershipHFTCloudCustomer AWS accountCustomer environment
Who pays infrastructure providersHFTCloudCustomerCustomer
Who pays HFTCloudCustomerCustomerCustomer
Control panel actionLaunch on HFTCloud resourcesEnter scoped API access and launchDownload package and deploy internally
NDA timingLater if neededEarlier in some casesUsually early
Operational burdenLowestMediumHighest

Security & NDA path

Public-safe qualification first, private rollout detail later

Managed Cloud

Public-safe qualification can begin without an NDA. Venue-sensitive details are introduced when the rollout scope requires them.

Customer Cloud (BYOC)

Scoped access, customer AWS policy, and direct provider relationships often move the NDA step earlier.

Self-Hosted

Package review, internal deployment constraints, and software distribution usually require the earliest NDA stage.

Common rule

The benchmark stays public-safe by default. Sensitive route and venue detail is shared only within the qualified rollout process.

Choose the rollout contour

Start with the benchmark. Pick the model second.

Use the benchmark sprint to validate the runtime decision, then choose the operating model that your desk can actually support.

Request Benchmark View Pricing Open Control Panel