Compute your organization can point to, not just spin up.
Most cloud platforms hand you an anonymous instance and step back. BECCA Cloud instead attaches a governed identity to every workstation and Edge Node: a named owner, a capacity package, an approval chain, and a running BCC ledger.
A BECCA deployment starts as a request, not a running system. An administrator selects a package, and the platform reserves a capacity class and a BCC allowance against it — nothing executes yet.
Once a workstation or Edge Node is connected and its certificate is verified, workloads can be submitted for review. Only after approval does BECCA move a session into an active, credit-metered state. Customers don't manage infrastructure directly: they select a package, connect a node, submit for approval, and read back exactly what it consumed.
- 01Reserved, not running. Capacity is held against your package before any workload executes.
- 02Device-bound trust. Each node authenticates with a certificate scoped to one organization.
- 03Approval before execution. A named approver clears workloads and publishing requests.
- 04Usage you can read. Every session posts to the BCC ledger for your team to review.
Workstations and Edge Nodes relate to governance the same way.
A dedicated Windows workstation is where a person works directly. An Edge Node is unattended regional capacity — closer to where data or users are — used for inference, rendering, or scheduled jobs. Both connect upward into the same governance layer and draw from the same BCC balance.
Match the node to the work.
Dedicated Windows workstation
A named machine bound to one person or role inside your organization, for interactive desktop work, design, rendering, or development that needs a full Windows session.
Edge Node
Unattended regional capacity for inference, batch jobs and scheduled workloads. Edge Nodes can be grouped into fleets and still carry the same certificate and approval requirements.