PUBLIC ALPHABiztraak is now in public alpha. Share feedback
Biztraak
Cloud Dev Code Editor Extensions

Cloud Dev

Cloud Dev keeps development work closer to the live project context by giving teams a browser-based workspace tied to the code, environment, and platform workflows around a component.


What Cloud Dev is for

Use Cloud Dev when you want to work inside a project-connected development environment without rebuilding the full setup locally first. The main value is continuity: code, repo context, and delivery workflows stay attached to the same project surface.

Open a workspace from the project context instead of managing the entire setup separately.

Stay near the real project by keeping code, deploy context, and linked resources easier to trace.

Move back into delivery quickly because the workspace belongs to the same application lifecycle you are already managing.

Cloud development environment in Biztraak
Cloud Dev keeps coding work close to the project surface, rather than breaking it off into a disconnected setup path.

What users typically do in Cloud Dev

A Cloud Dev environment is most useful when you want to:

  • inspect or update project code inside a browser-based workspace
  • work against a repo that is already part of a Biztraak project workflow
  • iterate on changes before moving into build review or deployment paths
  • reduce the friction between project creation and productive development

Cloud Dev focuses on the experience of developing in a project-connected workspace. the underlying workspace implementation is managed by Biztraak.

Practical Expectations

Cloud Dev is a project-connected development workflow. Editor and workspace options can differ by environment and provider.

The usual workflow is:

  • the environment is intended to keep development close to the project surface
  • editor and workspace experiences may vary depending on the current flow and component context
  • for deeper editor-specific behavior, review Code Editor alongside the relevant project workflow

Editor and workspace behavior may vary with the current flow and component context.

How Cloud Dev Fits Into the Platform

Cloud Dev is not the end state. It is a working phase inside the larger lifecycle.

  1. Create or import a project.
  2. Open a workspace tied to the component you want to work on.
  3. Make code or configuration changes in that connected environment.
  4. Move changes into build review, deployment, or other project workflows.

That connection to the wider platform is the main reason Cloud Dev belongs in Biztraak instead of being treated as a standalone browser IDE.

Next steps

Development Tools

See how Cloud Dev fits alongside builders and other product-side development workflows.

Code Editor

Go deeper on the coding workspace and editor-facing experience.

Build Reviews

Move from coding work into preview and validation environments.

Deployments

Connect workspace changes back to rollout and operational workflows.