PUBLIC ALPHABiztraak is now in public alpha. Share feedback
Biztraak
Core Concepts
Projects Components Component Settings Service Providers Deployments Domains Build Reviews Federated Apps

Service Providers

Service providers are the cloud or hosting targets Biztraak uses when a workload needs real infrastructure to run. They matter because provider choice influences how a component is provisioned, configured, and operated.


What this page covers

Use this page to understand how provider choice fits into Biztraak. Think of service providers as the execution layer under your components and deployments, not as a separate product area you manage in isolation.

Projects and components define what you are shipping.

Providers define where those workloads or supporting resources run.

Deployment workflows determine how application and infrastructure changes reach those targets.

Deployment and provider workflow context
Provider choices sit underneath project and deployment workflows, shaping where workloads are provisioned and released.

How to Think About Provider Support

Provider support should be read in terms of real end-to-end workflows, not just visible names in the product surface.

When choosing a provider, keep the following in mind:

  • Biztraak includes provider-aware deployment and infrastructure concepts.
  • Actual workflow depth varies by provider and workload type.
  • If a workflow matters for a live project, validate the target provider path against the current deployment flow rather than assuming all providers behave the same way.

Provider capabilities vary by provider and workload. Review the target provider workflow before planning a live deployment.

What providers Influence

Provider choice typically affects:

  • where compute and supporting infrastructure are provisioned
  • how runtime resources are configured for a component
  • which environment outputs and resource identifiers are available to downstream workloads
  • what operational and deployment assumptions apply to the component

In other words, provider selection is rarely just a hosting checkbox. It shapes the resources and runtime context around a component.

Availability and limits

Provider options do not all offer the same capabilities. Some are better suited to specific workloads or workflows and may have different levels of support.

If your team is choosing a provider for a real rollout, use this page alongside:

That will give you a more accurate view of how provider choice affects the actual workflow you are about to use.

Next steps

Deployments

See how provider-backed workloads move through review and release workflows.

Infrastructure Overview

Understand how resources are provisioned and managed beneath your components.

Virtual Machines

Learn where provider choice becomes especially visible in VM-hosted workflows.

Projects

Reconnect provider decisions to the project model where they are actually used.