Design, import, and review
datacenter fabric like code.
Before the change window.
RackTwin gives network, cabling, and infrastructure teams one model for the physical layer. Start from a cut-sheet or a new topology, catch drift and blast radius before technicians touch the floor, then generate the BOMs, labels, and work orders your build depends on. Request an invite to review RackTwin with your team. Real workspace access is invite-only while we onboard design partners directly.
Start from what you have.
RackTwin works for both greenfield and brownfield teams. The goal is the same either way: turn the physical fabric into something you can validate, review, and hand to operations without spreadsheet archaeology.
Import existing fabric
Upload a cut-sheet or observed state, infer structure, and get a project you can review instead of another one-off spreadsheet.
Design new fabric
Start from intent, expand into structure and materialized topology, and keep design choices reviewable before anything ships to the floor.
Review before the floor changes
Validate invariants, check drift, simulate cable failures, and generate artifacts from the same model the team just approved.
Model or import. Validate and diff. Export what the field team needs.
RackTwin keeps design, operations, and workload teams on the same artifact. The workflow is simple: create or import a project, review the risk, then export the outputs tied to that exact snapshot.
Model or import
Start from intent YAML or upload a cut-sheet. RackTwin turns both into a project with explicit structure, files, and reviewable state.
expand_intent() / import()Validate and diff
Run invariants, compare as-designed vs as-built state, and inspect the blast radius before a cable move becomes an outage.
validate() / reconcile()Simulate and export
Model failure scenarios, produce BOMs and labels, and hand operations a single set of outputs grounded in the approved topology.
simulate() / generate_artifacts()What teams actually review before a change window.
Brownfield import
Bring in cut-sheets and observed state, map devices to tiers and racks, and turn messy real-world data into a project you can audit.
Constraint validation
Catch structural problems, missing redundancy, and workload-specific invariants before a design review turns into a late-night rollback.
Drift Detection
Compare desired and observed state so missing, unexpected, stale, and conflicting links are visible before they surprise the next change window.
Failure simulation
Cut cables, degrade paths, or test bundle damage in software first so the team sees blast radius before the floor crew does.
Artifacts & BOM
Generate cut-sheets, BOMs, labels, face sheets, and work orders from the same topology the reviewers just signed off on.
2D + 3D proof
Use floor, rack, and cable views as evidence in the review workflow instead of relying on screenshots, tribal knowledge, or stale diagrams.
Traffic simulation
Model utilization and traffic behavior where it matters, then connect those results back to the same racks, rails, and ports operators will touch.
Scale without abstraction loss
Use the same workflow on a small pod or a hyperscale hall without collapsing the physical detail that makes review and operations meaningful.
Reviewable changes
Keep physical fabric changes in a diff-friendly workflow so architecture, operations, and workload teams can argue over one artifact instead of four versions of the truth.
Why platform and ML teams care about the physical layer.
Training schedulers and inference runtimes make assumptions about rails, planes, NVLink domains, and placement. RackTwin gives infra and workload teams one reviewable artifact to validate those assumptions before the deployment hits real hardware.
Rail & Plane Awareness
Tensor parallel, pipeline stages, and all-reduce paths assume a fabric shape. RackTwin models rails, planes, and lane assignments as data the team can query, not screenshots buried in a design deck.
Mate-key functions guarantee unique port pairs
Rail isolation validated at the graph level
Topology as review artifact
Infrastructure, network, and workload teams can review the same design and anchor comments to specific racks, rails, or connection patterns instead of trading screenshots and sidecar spreadsheets.
Comments anchor to rack / tier / rail / plane
Suggested changes mutate the intent in one click
Constraint Validation
Reviewers encode the invariants their workloads need — NIC counts, rail symmetry, NVLink domain shape, tier coverage — and RackTwin checks every snapshot against them before rollout.
MinSwitchesPerTier · EveryComputeConnected
Custom predicates hand-authored in Starlark
Placement impact before rollout
Change the intent, re-expand the topology, and see which racks, rails, and constraints move before a placement or capacity decision turns into an operational fire drill.
Before/after topology diffs at rack granularity
Constraint deltas surface the impact of the change
A small input. A concrete review surface.
The input can be compact. The output should not be vague. RackTwin turns intent or imported data into something a reviewer, technician, and workload owner can all reason about.
Open a sample, then make it yours.
The app ships with working examples so you can explore the workflow before you stage your own data.
From edge pods
to hyperscale halls.
The same workflow used for small examples holds at large scale. We keep full physical detail while still running expansion, graph build, simulation, and invariant checks in CI.
Request an invite.
Tell us what you're building.
RackTwin workspace access is invite-only.
Reach out when you want access for a real workspace, brownfield cleanup, or a topology that needs custom modeling, validation, and artifact generation tied to one reviewable source of truth.
We are onboarding design partners directly while the product and review workflow keep evolving.
- Brownfield cut-sheets and observed-state cleanup
- Validation and drift rules that match your change process
- BOMs, labels, face sheets, and work orders tied to one source of truth
- Rail, NVLink, or connector patterns that need custom modeling
Request received.
Thanks. We received your request and will follow up directly at the email address you provided.
If you need to reach us separately, email [email protected].