PUBLIC ALPHABiztraak is now in public alpha. Share feedback
Biztraak
Get Started
Start with a Template Start from Repository Use Cases

Start with a Template

Templates are a way to kick off a new project in Biztraak. Instead of wiring up every starting component yourself, you can use a prepared foundation and then review it for your needs.

Templates may include infrastructure, code, CI/CD, and governance starting points. the contents and provider support are specific to each template.

Browse the Marketplace →

1. Find a Template

From the Biztraak Marketplace, select the template you’d like to deploy.
You can filter by the options exposed by the current catalog. Review the template’s documented provider and deployment requirements before installing it:

  • Use Case: SaaS app, ecommerce, analytics, CMS
  • Framework: Angular, React, .NET, Node.js
  • Requirements: access, governance, or tenancy needs documented by the template

2. Deploy to Biztraak

Choose from the cloud provider and region options exposed by the selected template, then start the installation flow.

Biztraak handles:

  • Provisioning the infrastructure included by the template
  • Initializing repositories or workflows included by the template
  • Applying the template’s available deployment configuration

3. Explore your Deployment

Once deployed, you’ll see a detailed status page with:

  • Outputs: IDs, repo URLs, deployment URLs, IPs, ports
  • Live Logs: install, build, deploy status
  • Component State: infrastructure health + compliance signals

4. Start Building

  • Clone Your Repos: each component uses the repository connected through the project’s selected source-control integration. In the managed GitLab workflow, this is a private repository in the configured GitLab instance. See Capabilities and Availability for the available integrations.
  • Open in Cloud Dev: one click to launch VS Code in the browser, preloaded with extensions.
  • Use the UI Builder: drag-and-drop your frontend layout.
  • Extend with the API Builder: wire services and APIs visually.
  • Install Extensions: pull from the Marketplace, including federated apps, integrations, and custom addons.

Why Templates?

  • Faster Setup: minutes, not weeks.
  • Governance starting points: a template may include control or evidence structure, but it is not an assurance or certification.
  • Integrated: UI Builder, API Builder, Cloud Dev, Marketplace.
  • Customizable: extend infra, fork repos, and scale components.

Next steps

Templates are a launchpad: review the included components, permissions, provider path, and external dependencies before treating the generated project as production-ready.