Pricing & deployment models

Start with a benchmark sprint. Then choose the rollout contour that fits.

Every production plan begins with measured placement, route notes, and a tuned host recommendation. Then the runtime is deployed on HFTCloud-operated infrastructure, in your AWS account, or inside your own environment.

Annual agreements Support scoped separately Managed / BYOC / Self-hosted

Benchmark sprint

Every production plan starts here

The benchmark sprint is the common entry point across all deployment models.

What is included

  • One exchange and one workload profile
  • Benchmark alongside the current setup
  • Candidate ranking summary
  • Route notes and tuned host recommendation
  • Clear next step for rollout

What it is not

  • Not a forced infrastructure replacement
  • Not a public benchmark leaderboard
  • Not a universal latency guarantee
  • Not a request for full production scope on day one

Choose your deployment model

The benchmark is constant. The runtime location changes.

Where the runtime lives determines billing, account ownership, and control boundaries.

Fastest path to live deployment

Managed Cloud

Deploy on HFTCloud-operated infrastructure and launch through the HFTCloud control panel. HFTCloud provisions, tunes, and operates the runtime so the team gets the shortest path from benchmark to production with one operational counterpart and one invoice.

  • HFTCloud-operated cloud resources
  • Placement-driven deployment and host tuning
  • One commercial relationship with HFTCloud
  • Best fit for first production rollouts

Your AWS account. Our runtime.

Customer Cloud (BYOC)

Deploy into your own AWS account while keeping HFTCloud placement logic, orchestration, and tuned deployment workflow. You keep ownership of cloud spend, access policy, and third-party infrastructure contracts. HFTCloud is billed separately.

  • Customer-owned AWS account and policy boundary
  • Scoped API onboarding through the control panel
  • Direct cloud and connectivity billing
  • Best fit for platform-led teams

Inside your perimeter

Self-Hosted

Install the HFTCloud package inside your own environment and operate within your internal security boundary. This is the highest-control model for teams that require self-hosted deployment, tighter review, and stricter change management.

  • Customer-hosted package
  • Earlier NDA and technical review
  • Separate annual software and support agreement
  • Best fit for stricter internal control models

Comparison matrix

Compare ownership, billing, and rollout friction

Use the matrix below to choose the operating model that fits your desk.

Item Managed Cloud Customer Cloud (BYOC) Self-Hosted
Where the runtime livesHFTCloud-operated environmentCustomer AWS accountCustomer environment / internal perimeter
Who owns the cloud accountHFTCloudCustomerCustomer
Connectivity contractsIncluded through HFTCloud where applicableCustomer-managed where applicableCustomer-managed
Billing modelSetup fee + monthly fee paid to HFTCloudSetup fee + HFTCloud monthly fee, plus direct infrastructure billsSetup fee + annual software/support agreement, plus direct infrastructure bills
How the team launchesThrough HFTCloud control panelThrough HFTCloud control panel with customer AWS accessDownload package and deploy inside your environment
Time to first runFastestFast after access setupSlowest, review-led
Benchmark eligibilityDefault starting pathAvailable after qualificationLimited, technical review first
NDA timingLater if neededEarlier for some scopesEarly, usually before package review
Customer operational burdenLowestMediumHighest
Control and isolationStandardHighHighest

Support & engineering

Deployment model and support level are scoped separately

This keeps infrastructure ownership and engineering effort from being mixed into one opaque tariff.

Included with every plan

Standard Support

Onboarding into the selected deployment model, product support, platform updates, and normal rollout guidance.

Optional add-on

Extended Support

Faster response windows, deeper operational coordination, and more structured change planning.

Optional add-on

Engineering Retainer

Custom integrations, environment-specific tuning, and advanced performance work beyond standard product support.

FAQ

Commercial questions that come up early

Is the benchmark sprint free?

Qualified teams can start with a 5-business-day benchmark sprint at no charge. Production rollout moves to an annual commercial agreement once the scope is validated.

Do teams need to replace their current infrastructure to start?

No. The benchmark can run alongside the current setup so teams can compare the current path against feasible candidates before broader changes.

Can teams move between deployment models later?

Yes. Many teams start in Managed Cloud to validate quickly, then move to Customer Cloud or Self-Hosted when procurement, security, or scale requires it.

What is billed separately from the deployment model?

Extended support, custom integrations, and non-standard engineering are scoped separately from the deployment model.

When is an NDA required?

Higher-control models and venue-sensitive rollout details may require an NDA earlier in the process.

Start with a benchmark sprint

Choose the pricing model after the measured result exists

Begin with one exchange, one workload profile, and one benchmark question. Then pick the rollout contour that fits your desk.