Skip to content

Physical infrastructure. Managed.

The express track to hardware value#

Hardware, connectivity, and operations—brought together for your workload.

Discuss a deployment Explore pricing

---
config:
  flowchart:
    curve: linear
    nodeSpacing: 30
    rankSpacing: 35
---
flowchart LR
    start(("Project Start"))

    subgraph diy["DIY Hardware Bootstrap"]
        direction LR
        funding["CAPEX<br/>36M Terms<br/>Staffing"]
        facilities["Space<br/>Power<br/>Cooling"]
        networking["WAN<br/>LAN<br/>Out of Band"]
        operations["OS<br/>Monitoring<br/>Security"]
        funding --- facilities --- networking --- operations
    end

    subgraph rolling["Rolling Stock"]
        direction LR
        signup("Sign Up")
        deploy("Deploy")
        signup === deploy
    end

    start --- funding
    start === signup
    operations --- production(("Production"))
    deploy === production
    production --> tpu["TPU"]

    classDef express stroke:#5274c1,stroke-width:3px;
    class signup,deploy,production express;
    style rolling stroke:#5274c1,stroke-width:2px
    linkStyle 3,5,7 stroke:#5274c1,stroke-width:4px;

Cloud-native workloads

How does a cloud-native team test a hardware-only TPU?#

Connect your cloud environment to physical accelerators, with Yard Router and Yard Tower providing access and observability.

Explore Rack Unit Provided Hardware 

flowchart LR
    subgraph internet["Internet"]
        L[Laptop]
        A[AWS]
    end
    L <-->|Tailscale| R{{Yard Router}}
    A <-->|Site to Site| R
    subgraph service["Rolling Stock Service Network"]
        H["Rack Unit TPU"]
        T{Yard Tower}
        H <-->|Prometheus| T
    end
    R <--> H

    style internet fill:#e0525214,stroke:#e05252,stroke-width:2px
    style service fill:#5274c114,stroke:#5274c1,stroke-width:2px

    style R fill:#5274c114,stroke:#5274c1,stroke-width:3px
    style H fill:#5274c114,stroke:#5274c1,stroke-width:2px
    style T fill:#5274c114,stroke:#5274c1,stroke-width:2px
    style A fill:#e0525214,stroke:#e05252,stroke-width:2px
    style L fill:#2da44e14,stroke:#2da44e,stroke-width:2px

Laptop and AWS connect through Yard Router to the provided TPU hardware. Yard Tower connects to that hardware through Prometheus.

Compute at the edge

How does a logistics company make "Compute" a local site asset?#

Bring compute to your sites and connect it to the networks and cloud services your business uses.

Explore Rolling Stock Onsite 

block-beta
    columns 5
    block:tacoma_rsos
        columns 1
        tacoma_heading["RSOS"]
        tacoma["Tacoma, WA<br/>400 kW"]
    end
    space
    block:boise_rsos
        columns 1
        boise_heading["RSOS"]
        boise["Boise, ID<br/>120 kW"]
    end
    space:2
    space:5
    block:eugene_rsos
        columns 1
        eugene_heading["RSOS"]
        eugene["Eugene, OR<br/>280 kW"]
    end
    space interconnection{{"Managed<br/>Interconnection"}} space
    block:aws
        columns 1
        aws_heading["AWS"]
        aws_region["us-west-2"]
    end
    space:5
    block:redwood_rsos
        columns 1
        redwood_heading["RSOS"]
        redwood["Redwood City, CA<br/>80 kW"]
    end
    space
    block:greeley_rsos
        columns 1
        greeley_heading["RSOS"]
        greeley["Greeley, CO<br/>200 kW"]
    end
    space
    block:databank
        columns 1
        databank_heading["DataBank"]
        salt_lake["Salt Lake (UT)"]
    end

    tacoma_rsos <--> interconnection
    eugene_rsos <--> interconnection
    redwood_rsos <--> interconnection
    boise_rsos <--> interconnection
    greeley_rsos <--> interconnection
    interconnection <--> aws
    interconnection <--> databank

    style interconnection fill:#5274c114,stroke:#5274c1,stroke-width:3px
    style tacoma_rsos fill:#5274c114,stroke:#5274c1,stroke-width:2px
    style tacoma stroke:#5274c1,stroke-width:3px
    style boise_rsos fill:#5274c114,stroke:#5274c1,stroke-width:2px
    style boise stroke:#5274c1,stroke-width:3px
    style eugene_rsos fill:#5274c114,stroke:#5274c1,stroke-width:2px
    style eugene stroke:#5274c1,stroke-width:3px
    style redwood_rsos fill:#5274c114,stroke:#5274c1,stroke-width:2px
    style redwood stroke:#5274c1,stroke-width:3px
    style greeley_rsos fill:#5274c114,stroke:#5274c1,stroke-width:2px
    style greeley stroke:#5274c1,stroke-width:3px
    style tacoma_heading fill:transparent,stroke:transparent
    style boise_heading fill:transparent,stroke:transparent
    style eugene_heading fill:transparent,stroke:transparent
    style redwood_heading fill:transparent,stroke:transparent
    style greeley_heading fill:transparent,stroke:transparent
    style databank_heading fill:transparent,stroke:transparent
    style aws_heading fill:transparent,stroke:transparent
    style databank fill:#2da44e14,stroke:#2da44e,stroke-width:2px
    style salt_lake stroke:#2da44e,stroke-width:3px
    style aws fill:#e0525214,stroke:#e05252,stroke-width:2px
    style aws_region stroke:#e05252,stroke-width:3px

Illustrated deployment

5

RSOS sites

1,080 kW

Available power

Connected

AWS & DataBank

Managed Interconnection connects these sites to AWS us-west-2 and DataBank in Salt Lake (UT).

Start with your workload

Where does your infrastructure need to go?#

Tell us about your hardware, locations, and connectivity requirements.

Talk to Rolling Stock