The path from package to review

Five governed steps, in order.

Every workload BECCA runs follows the same sequence, regardless of package tier. Nothing skips ahead of approval, and nothing runs without a connected, certified node. Select a step below to see what happens at that stage.

Plan your capacity

Select a package by capacity class and BCC allocation. The platform reserves your allowance and issues onboarding credentials — nothing runs yet.

Preview selection

BCC allocated

Package reserved

Connect your workstation or Edge Node

Pair a dedicated Windows workstation or Edge Node. Device trust is established through a provider-issued certificate before anything else can happen.

Certificate issuance provider-disabled

Workstation

Certificate

Edge Node

Send workloads for approval

Submit a workload for review. It stays queued until a named approver clears it against your organization's policy — no workload skips this gate.

Approval required

Workload queued

Approver clears it

Run the approved workload

Only once cleared does BECCA move a session into an active, credit-metered state. Execution remains off for anything that has not been approved.

Execution disabled by default

Session active

Metered execution

Measure your BCC usage

Read back what each session consumed — compute, inference, storage, network, deployment and support — against your BCC balance.

Live metering provider-gated

BCC drawn

Usage recorded

1. Plan

Choose a package. Capacity and BCC are reserved, not running.

2. Connect

Pair a node. Certificate-based trust is required first.

3. Approve

A named approver clears the workload against policy.

4. Run

Execution moves to an active, credit-metered state.

5. Measure

BCC draw and outcome are written back for your review.

Why the order is fixed

No step is optional, and none run out of order.

The same sequence applies whether you're running a single workstation or an Enterprise Edge fleet. That consistency is what makes the audit trail meaningful: an auditor reviewing any session sees the same five checkpoints, regardless of tier.

See how each checkpoint maps to security controls on the security page, or how BCC is actually drawn during Run and Measure on the BCC credit page.