Skip to main content
ClrSlate
Request a demo

Solution · Provisioning

Environments and production changes

One request for an environment, decided where the limits are; production changes owned, incidents followed to their fix.

Request a demo

Env request, then Ana decides, then Ready.

Who decides · Ana Okafor · Head of platform · capacity above the standard quota

How it runs

A product team needs an environment and waits on four teams that do not know the others were asked. A change to production needs an owner, a window and an approval; an incident needs an owner, a cause and a follow-up on the backlog.

A seat is a role a person and an agent hold together; the escalation matrix says who decides above each limit, seat by seat.

  1. Person decidesMon 09:10
    Sofia raises one request for payouts staging
  2. Rules check09:14
    Fits the environment blueprint
  3. Agent carries09:20
    Identity, destination and pipeline created inside their standards
  4. Rules check09:22

    PLT-R04

    Quota above the standard is spend

  5. Person decides11:40
    Ana approves, with a review after a month
  6. Person decides11:46
    Sofia accepts and owns the environment
  7. Person decidesLater
    An alert fires; Joon Park decides the rollback
up the escalation matrix, by rule a person decides

Your alerting · payouts

P2

Payouts delayed

02:10 · Tuesday

Owner paged: Joon Park, on-call lead

Drawn as your tool shows it; ClrSlate adds the line that names the owner.

Illustration · Halden, a fictional company

Step by step

Who takes each step, in order.

For

Told end to end: A new environment for Halden’s payouts service. Halden is a fictional company.

  1. 01Sofia Brandt, environment ownerRaises one request for a staging environment; her agent fills in what the blueprint needs.
  2. 02Olu Adeyemi, DevOps practice leadConfirms it fits the environment blueprint (PLT-R01); four parts go to the seats that own them at once.
  3. 03The IAM practice’s agentCreates the identity client and roles inside the identity blueprint, and records them.
  4. 04The Kubernetes platform’s agentPrepares the namespace; the quota asked for is above the standard, so it goes up as spend (PLT-R04).
  5. 05The GitOps and CI/CD agentsCreates the delivery destination and the pipeline environment inside their standards.
  6. 06Ana Okafor, Head of platformDecides the capacity increase once, with the numbers in front of her, and a review date.
  7. 07Sofia BrandtAccepts the result and owns the environment from then on.
  8. 08Joon Park, on-call leadWhen an alert fires, decides the rollback (OPS-R03); the follow-up lands on the owning team’s backlog.

Where the decisions sit

Decision, who decides, up to where, and above that whom.

  • The request fits the environment blueprintDecides: the DevOps practice leadUp to: the blueprint as publishedAbove that: a recorded exception, with owner and review date
  • The namespace and its quotaDecides: the Kubernetes platform leadUp to: the standard quotaAbove that: the department head, as a capacity increase
  • A cloud projectDecides: the cloud platform leadUp to: the landing zone’s baseline policiesAbove that: the department head
  • The identityDecides: the identity team’s leadUp to: the environment’s identity blueprintAbove that: the Security practice lead
  • The result is acceptedDecides: the environment owner——
  • Rollback in productionDecides: the on-call leadUp to: the runbookAbove that: the department head

How much the agent decides, to start. Each platform seat’s agent provisions its part within the blueprint and the quota without asking. Fit, exceptions, spend and anything that touches production ask a person.

The record it leaves. One request, REQ-3310, four parts, four seats, one escalation: DEC-1104, Ana Okafor, approved with a condition. Everything created is linked from the request, and the condition has a date on it.

How it plugs in

No new inbox, no new tool to learn.

  • 01

    An app in your tools

    Connects to your repositories, trackers and chat as an app

  • 02

    A check, not a meeting

    Holds a decision as a check the owner clears

  • 03

    Where people already work

    Asks the owner where they already work, and carries out what was decided

REQ-3310 · payouts staging

Four parts, four seats

  • Identity client and rolesLars Nilsen and agentIAM practice
  • Namespace and quotaAbove the standard quotaNeeds Ana
  • Where it deploysDelivery destinationGitOps
  • How it deploysPipeline environmentCI/CD
One request, four parts, four seats.

The tools it runs through

We connect to the systems you run, and build the connection before the demo.

What it uses

Where it leads

Start with howyou run today.

Bring one piece of work that breaks at the handoffs: a pull request waiting on three reviewers, an initiative spread across twelve tools, a release nobody owns. We model the seats it crosses, give one of them an agent, and follow one decision to its record.

Request a demo