PUBLIC ALPHABiztraak is now in public alpha. Share feedback
Biztraak

Infrastructure Overview

In Biztraak, infrastructure is first-class.
Project components can connect code deployment to the infrastructure resources exposed by the selected workflow, such as compute, databases, storage, networks, or IAM.

Biztraak automates this using Terraform-backed templates, executed in secure isolated runners managed by Biztraak.
Where a provider workflow provisions resources in your account, you retain ownership of that provider account while Biztraak manages the configured automation.

Infra vs Code Deployments

It’s important to understand the distinction:

  • Infrastructure Deployments

    • Independent processes that provision or update cloud resources.
    • Run in Biztraak-managed isolated runners, not via CI/CD.
    • Usually less frequent, since infra should remain stable.
    • Provide outputs (IDs, URLs, roles, secrets) that feed into code deployments.

  • Application (Code) Deployments

    • Triggered by commits or pull requests, run through the configured source-control pipeline in your cloud account.
    • Happen frequently, supporting rapid iteration.
    • Consume infra outputs as environment variables.

⚠️ Infra deployments and code deployments are not triggered together, they are independent but connected.
Infra gives you the stable foundation. code can iterate quickly on top.

Key Concepts

  • Service Providers: use the provider and workload paths exposed by the selected configuration. See Capabilities and Availability for the current matrix.
  • Terraform Templates: each component comes with provider-specific templates.
  • Virtual Machines: VMs are infrastructure-backed components with runtime operations and optional VM-hosted workloads.
  • Ownership: infra is provisioned in your accounts, not shared Biztraak infra.
  • Governance baselines: modifying templates may change the controls, evidence, and operating assumptions you started with.

Customization & Compliance

  • You can customize Terraform templates through the UI editor.
  • Modifying templates means you take on compliance responsibility.
  • Enterprise customers can enable the GRC Add-On, which:
    • Can collect available infrastructure records for review.
    • Generates audit documentation.
    • Connects custom templates to the governance structure your team uses.

Roadmap

  • Git-Backed Templates: infra definitions tracked in Git for history and collaboration.
  • Policy Gates: compliance/cost rules that block unsafe infra changes.
  • Marketplace Modules: share and reuse infra modules from the Marketplace.

Why Biztraak Infra Matters

  • Secure: IaC with RBAC and secrets baked in.
  • Multi-Cloud: consistent workflows across providers.
  • Flexible: customize Terraform while keeping audit logs.
  • Traceable: infra changes are tracked alongside code deployments.

Next steps

Biztraak treats supported infrastructure workflows as code-oriented, configurable, and reviewable. Validate the provider path and governance requirements for your workload.