Projects
A Biztraak project is the main operating space for an application, service, or internal platform initiative. It is where your delivery workflow, runtime configuration, supporting infrastructure, and collaboration model come together.
What a Project Represents
Start from a template when you want a pre-shaped foundation for a common application or architecture pattern.
Start from a repository when you already have code and want Biztraak to wrap deployment, runtime, and platform workflows around it.
Operate in one place by keeping components, deployments, domains, settings, and build reviews tied to the same project boundary.
What Lives Inside a Project
A typical project includes the application parts you are shipping and the supporting context required to operate them through connected docs pathways.
Components
Frontend apps, APIs, databases, background services, virtual machines, and supporting workloads.
Deployments
Build reviews, production releases, deployment status, and operational signals tied to the project lifecycle.
Domains
Biztraak-managed subdomains are available for deployed workloads. custom domains require the team-domain workflow and entitlement.
Development Workflows
Cloud Dev, repo-linked coding workflows, builders, and environment configuration for the system you are shipping.
Compliance Context
Audit logging, control-aware activity, and related evidence signals attached to the same work surface.
Team Access
Roles, member access, ownership, and billing responsibility attached to the project boundary.
Creating a Project
You can create a project in two common ways.
Template-first creation is the faster path when you want infrastructure, project structure, and supporting defaults to be laid out for you from the start.
Repository import is the right fit when your code already exists and you want Biztraak to become the place where deployment, domain, review, and environment workflows are managed.
In either case, the goal is the same: move from an initial code or template choice into a project surface where the rest of the lifecycle can happen.
Project Lifecycle
A healthy project usually moves through the same broad phases:
- Create the project from a template or repository.
- Define or add components that represent the deployable parts of the system.
- Configure providers, domains, and settings needed for runtime behavior.
- Use build reviews and deployments to validate and release changes.
- Operate the project through logs, configuration, runtime visibility, and team workflows.
- Extend it over time with federated apps, marketplace assets, or additional services.
Projects are meant to keep those phases connected, so the path from setup to live operations is easier to follow.
When a Project Model Helps Most
Projects are especially useful when you need one place to coordinate multiple concerns that usually get split across different tools.
- teams building more than a single repo or single runtime
- products that need repeatable release and review workflows
- environments where domain, infrastructure, and access management need to stay visible
- organizations that want compliance and operational signals attached to delivery work
If your team is trying to reduce context switching between code, deployment, environments, and governance, the project model is where Biztraak adds the most value.
Next steps
Components
Understand the pieces that make up a project and how they relate to one another.
Deployments
See how changes move through build reviews, rollout, and production workflows.
Domains
Connect public routing and custom domains to the workloads inside your project.
Build Reviews
Preview changes in isolated environments before they become long-lived releases.