Identity and purpose
Connect the environment to a human, team, workflow or agent and record the outcome it is meant to deliver. Accountability remains visible after creation.
Acumy Workspaces
The governed unit of non-production cloud.
A Workspace binds every deployment to the owner, purpose, access, budget and lifecycle conditions that make it accountable.
Workspace · ATL-204
ActiveProject Atlas / model validation
Preflight complete8 / 8 controls
Template approved
Access in scope
Automatic retirement
Context by design
Everything needed to govern the environment
Workspaces give technical and financial teams one durable record of what was requested, what was approved and what must remain true. They turn governance from a collection of disconnected checks into an operating contract for the environment.
Budget and approval
Set a financial boundary before provisioning, route exceptions to the appropriate decision maker and keep the accountable owner visible as usage changes.
Schedule and expiry
Define when an environment should run, how long it may exist, what happens at expiry and when a renewal needs explicit approval.
The Workspace record
The context that travels with the infrastructure
A Workspace is more than a project folder or cost label. It is the shared record used by Engineering, CloudOps and FinOps to understand the environment and make consistent decisions throughout its life.
Requester and owner
Identify who asked for the environment, which team is accountable and whether the initiating actor was human or automated.
Workload and template
Record what is being deployed, the approved pattern being used and the business or technical purpose behind the request.
Cloud scope
Define the permitted cloud, account, region, services and other boundaries relevant to the requested environment.
Access and policy
Attach the access model, applicable guardrails, approval outcome and any authorised exception to the Workspace.
Budget and usage
Connect the approved financial limit to ongoing consumption so the figures retain their operational meaning.
Schedule and lifecycle
Set run windows, lease duration, renewal rules and the final action at expiry, including reclamation or termination.
Policy preflight
A decision before infrastructure exists
Each Workspace request is evaluated against policy, risk, access and financial guardrails before cloud resources are created. Standard requests can proceed quickly, exceptions can reach the correct approver and prohibited requests can be stopped at source.
AllowRequire approvalBlock
01
Request with intentSelect a governed workload or template, declare the purpose and identify the accountable owner.
02
Evaluate before provisioningCheck identity, role, cloud scope, services, access, budget, schedule and time boundary against policy.
03
Operate in contextTrack the environment against what was approved, then renew, reclaim or terminate it through a deliberate lifecycle decision.
See Acumy in operation