Get Started with Biztraak
Biztraak is a developer-first platform for building, deploying, and managing applications with security and governance workflows connected to delivery. This guide walks you through the first milestones, from project creation to production rollout.
What is Biztraak?
Start faster. Launch from templates or repositories, generate infrastructure automatically, and keep project workflows connected from the beginning.
Stay closer to delivery. Development environments, builders, deployments, and review workflows sit inside the same project context.
Keep review context attached. Available audit-oriented signals and operational visibility stay near the work instead of becoming a separate afterthought.
Prerequisites
Before you start, make sure you have a Biztraak account, a linked Git provider account, and an active workspace created during onboarding.
1. Create your first project
From the Dashboard, click New Project and choose the way you want to begin. You can start from a reusable template, import an existing repository, or prepare for AI-assisted scaffolding as that workflow rolls out.
Template-first setup is the fastest path when you want a pre-shaped foundation. Repository import is ideal when you already have code and want Biztraak to wrap deployment and platform workflows around it.
Start from AI uses a natural-language prompt to scaffold a project (coming soon).
2. Deploy a Component
Each project is made up of components such as frontend apps, backend services, APIs, and databases. Once a component is ready, Biztraak can connect it to infrastructure and push it through a deployment workflow.
You choose the target, review the generated infrastructure and pipeline behavior, and then follow the rollout from the same project view. Logs, outputs, and deployment state stay attached to the component rather than scattered across separate tools.
The key value here is visibility: provisioning, pipeline progress, and deployment outputs all stay in one operational trail.
3. Open your Cloud Dev environment
Components can be paired with development environments so coding work stays close to the deployed system and the wider project context.
You can open browser-based tooling, launch the workspace apps exposed by the environment, and work with the dependencies already provisioned for the project. That reduces the setup gap between project creation and productive development.
The goal is continuity: code, tooling, and delivery workflows remain connected instead of becoming separate tracks.
4. Build and Extend
Once the project is live, Biztraak gives you more than deployment. You can shape frontend experiences through the UI Builder, model backend flows through the API Builder, and extend the project with reusable platform assets.
Builders are meant to accelerate structure, not hide it. They sit near the real project so teams can move visually when it helps while staying grounded in the application they are actually delivering.
5. Go Live
When you are ready for production, Biztraak keeps release workflows tied to review, promotion, and visibility rather than treating them as separate handoffs.
Use Build Reviews for staging and review workflows, promote builds into production deployments, attach a managed subdomain or an enabled custom domain, and follow rollout activity through logs, audit trails, and project status views.
Going live should feel traceable, not opaque. Configured build and deployment workflows surface operational context around the release.
Next steps
Start with a Template
See how template-based project creation works and what it prepares for you up front.
Import from Repository
Bring an existing codebase into Biztraak and connect it to platform workflows.
Explore Core Concepts
Understand projects, components, providers, deployments, and the core platform model.
Set Up Compliance Automation
Learn how Biztraak connects operational activity to compliance-aware workflows.