System Atlas

Standard architecture: Cloud and GPU compute providers

Workflows that drive an outcome from step to step. Process steps that hand work to each other.

Standard architectureThe parts at least half of the organizations in Cloud and GPU compute providers have, as many as 6 of them run all together. Counted from public, sourced parts only; each organization below links to the parts it was counted on.

Organizations running it
6
Of their industry
33%
The pattern
What every instance has, in order
  1. Decisions
    Market and positioning
    in 100% of instances
    then
  2. Process
    Lead generation
    in 100% of instances
    then
  3. Decisions
    Pricing
    in 100% of instances
    then
  4. Process
    Product or service design
    in 100% of instances
    then
  5. Process
    Production or delivery
    in 100% of instances
    then
  6. People
    Customer service and support
    in 100% of instances
    then
  7. Data
    Regions and availability zones
    in 100% of instances
    then
  8. People
    Org structure
    in 100% of instances
    then
  9. Software
    Usage metering and billing
    in 100% of instances
    then
  10. Decisions
    Security and access
    in 100% of instances

Coloured arrows: a flow of that type seen between the two at instance organizations. Grey arrows: order only.

Structure
Element
Share of instances
Companies
Invariant 10
At least 90% have it
People2
Customer service and support
100%
6
Org structure
100%
6
Process3
Lead generation
100%
6
Product or service design
100%
6
Production or delivery
100%
6
Software1
Usage metering and billing
100%
6
Data1
Regions and availability zones
100%
6
Decisions3
Market and positioning
100%
6
Pricing
100%
6
Security and access
100%
6
Variant 17
20 to 80%: where they differ · Members
People3
Sales
67%
4
Site and operations engineers
67%
4
Account management
33%
2
Process9
Uptime and incident response
67%
4
Billing and invoicing
67%
4
Proposals and quoting
50%
3
Customer onboarding
50%
3
Hardware lifecycle
50%
3
Procurement
33%
2
Quality control
33%
2
Capacity planning
33%
2
Learning and improvement
33%
2
Software1
Network and interconnection
50%
3
Decisions4
Policies and culture
67%
4
Regulatory compliance
67%
4
Performance and pay
33%
2
Data residency and sovereignty
33%
2
Variant · where they differ
Member
Variants, couplings and instances

Every level, number, source and dimension: Member, $300 a year.

Couplings · what comes together
Member
Variants, couplings and instances

Every level, number, source and dimension: Member, $300 a year.

Entropy
Where it runs rough

Operating-reality findings at instance companies: workarounds, manual hand-offs, bottlenecks.

  • Uptime and incident response2 findings
    Dependency 2 · at 2 companies
  • Sales2 findings
    Dependency 1 · Manual hand-off 1 · at 2 companies
  • Hardware lifecycle1 finding
    Workaround 1 · at 1 company
  • Network and interconnection1 finding
    Dependency 1 · at 1 company
  • Product or service design1 finding
    Dependency 1 · at 1 company
  • Org structure1 finding
    Tacit rule 1 · at 1 company
  • Procurement1 finding
    Bottleneck 1 · at 1 company
  • Quality control1 finding
    Dependency 1 · at 1 company
Seen across
Where it holds
Size
  • 11-50 people17%
Region
  • United States50%
  • London, England17%
  • New York, Stockholm, San Francisco, London17%
Instances
The 6 companies it was seen at
Member
Variants, couplings and instances

Every level, number, source and dimension: Member, $300 a year.