Core Concepts
Biztraak is easiest to understand when you stop thinking about it as a single tool and start thinking about it as one connected product surface for delivery. Projects, components, deployments, infrastructure, development environments, and compliance records from enabled workflows can stay attached to the same working context.
How to Read Biztraak
Projects are the top-level working spaces for an application or initiative.
Components are the deployable parts inside a project, such as web apps, APIs, databases, and supporting services.
Deployments move infrastructure and application code through review, rollout, and operations workflows.
Platform tools like Cloud Dev, builders, marketplace assets, and enabled compliance views stay tied to those same objects instead of living as disconnected systems.
Projects
Projects are the main containers for work in Biztraak. A project brings together your components, deployment history, domains, environments, and team access model. compliance context or tracking is attached when an enabled workflow exposes it.
A good way to think about a project is as the operating boundary for a product or system. If your team needs one place to manage source code workflows, environments, runtime configuration, domains, and delivery status, the project is the place where that gets organized.
Read next: Projects
Components
Components are the parts that make up a project. A component might represent a frontend, a backend service, an API, a database-backed workload, a virtual machine workload, or an extension point such as a federated app.
Components matter because they are where deployment behavior, runtime configuration, repo linkage, and service relationships usually become concrete. They also make dependencies visible, so you can reason about which parts of a system rely on which other parts.
Read next: Components
Providers, Infrastructure, and Runtime
Service providers define where a component runs. Infrastructure workflows define how the underlying resources are provisioned and managed. Runtime pages explain how application workloads, domains, and supporting services behave once deployed.
These areas are closely related, but they are not identical:
- Service Providers answer where a workload is hosted.
- Infrastructure answers what supporting resources are provisioned.
- Runtime and deployment pages answer how application code gets built, released, configured, and operated on top of that foundation.
Read next: Service Providers, Infrastructure Overview, and Deployments
Deployments and Reviews
Deployments in Biztraak are about moving work through a delivery lifecycle, not just pushing code to production. The platform keeps build reviews, production releases, infrastructure execution, and operational visibility tied to the same project context.
Build Reviews create room for validation before rollout. Production deployments turn approved changes into long-lived environments. Infra-specific workflows handle the resources those workloads depend on.
Read next: Deployments and Build Reviews
Development and Extension Surfaces
Biztraak is not only a deployment surface. It also includes development workflows such as Cloud Dev, visual builders, API tooling, and reusable assets from the Marketplace.
This matters because the product is designed to keep setup, build, extension, and release work closer together. When an enabled workflow exposes compliance tracking, it stays in that same product context.
Cloud Dev
Use browser-based development environments that stay connected to your project workflow.
Builders
Use UI Builder and API Builder when visual structure helps teams move faster.
Marketplace
Bring templates, federated apps, and reusable assets into projects through the marketplace flow.
Federated Apps
Extend projects with plug-in style application modules that stay inside the product model.
Next steps
Projects
See how the main working container in Biztraak organizes your system.
Components
Understand the deployable building blocks inside each project.
Deployments
Follow the delivery lifecycle from review to production.
Cloud Dev
Explore the development workflows that sit next to delivery and operations.