The studio
A live-in engineering block. Residents are why a site being proved moves faster than a site being visited.
Edge · Xalant Edge · Solutions → Remote Development Center
Edge · Solution
Remote Development Center
A repeatable off-grid site: a live-in engineering studio, an edge-in-a-box data center, a satellite ground station and on-site power.
What it is
A repeatable off-grid site — live-in engineering studio, edge-in-a-box data hall, satellite gateway and on-site power inside one fence line.
A repeatable off-grid site. Live-in engineering studio, edge-in-a-box data hall, satellite ground station and on-site power, inside one fence line.
It is the flagship because it is the unit that proves the rest of the ladder. Three systems that are usually three separate projects — accommodation, compute, and the power and connectivity that carry them — are designed here as one parcel with one approval path and one commissioning sequence.
Nothing on site is designed to depend on a public utility. Compute is designed to stay local, and only results and control traffic are designed to cross the uplink.
The land gates are published as design criteria rather than kept in a deck, so a landowner can tell whether their parcel is a candidate before anyone gets on a call.
Specification
What is settled, and what is not
The list below is what the unit is. The figures that go with it are held back until each one has a named basis and an as-of date — Xalant is pre-formation with no live sites, so a number here would be a design target dressed as a measurement. Each row appears on this page the day its figure clears.
What the specification will describe
- Studio
- Live-in engineering block
- Data hall
- The containerized unit, unchanged
- Ground station
- Satellite gateway pad on the same parcel
- Power
- Generation and storage inside the fence line
- Land use
- Most of the parcel stays undeveloped
- Utility
- Nothing on site is designed to depend on one
- Compute
- Designed to stay local
- Repeatability
- The same kit and the same approval pack, again
- Site areaThe whole parcel, most of which stays undeveloped and carries the energy plant.
- Developed areaThe part that is actually built on — the studio core, the data yard and the comms pad.
- Site electrical loadWhat the on-site generation is designed to carry, studio and data hall together.
- People on siteEngineers and support staff living on the campus, which is what makes it a development center rather than a dark site.
- White spaceThe data hall inside the fence is the containerized unit, unchanged.
Design rule
Nothing on site depends on a public utility.
Generation, storage, cooling and the path off site are all inside the fence line, which takes the interconnection queue off the critical path entirely. Compute stays local: only results and control traffic are designed to cross the uplink.
Design intent, not an operating record
Three coupled systems
One parcel, one approval path
The data hall
The containerized unit, unchanged. Nothing about the enclosure is special-cased because it is on a campus.
Power and connectivity
Generation, storage and the satellite gateway pad, all inside the fence line and all on the critical path together.
Site zones
Four zones inside one fence line
The studio core, the edge data yard and the comms pad cluster in one corner; the energy parcel takes the rest and stays largely open. The areas are in the specification above, not on the drawing — a dimension drawn on a plan of a site nobody has surveyed is a number pretending to be a measurement.
Land gates
What makes a parcel a candidate
Published as design criteria so a landowner can rule themselves in or out before anyone gets on a call. No parcel has been acquired and no site exists, so none of these is a requirement anyone has been held to yet.
- Parcel
- One contiguous parcel, most of it left undeveloped
- Developed ground
- A small buildable core for studio, data yard and pad
- Access
- All-weather road access rated for module delivery
- Setback
- Distance from the nearest dwelling, for generation noise
- Sky view
- Clear view for the gateway pad, no terrain shadow
- Ground
- Buildable for the energy parcel, no wetland or floodway
- Zoning
- A route to industrial or a conditional-use path
- Utility
- Not required — nothing on site is designed to depend on one
Replication
The first build proves it. The rest repeat it.
The first build in South Oregon takes up to nine months; every site after it is a repeatable ninety days plus local approval time.
Reuse the kit
The same enclosure, the same generation package, the same gateway pad. Nothing is redesigned between sites.
Repeat the approvals
The same drawings, the same studies, the same application pack. The second jurisdiction is a different reader, not a different document.
Run it as a program
Sites are planned in sequence with one team carrying what it learned forward, rather than as separate projects that each start from nothing.
Questions
Asked and answered
- What is a Remote Development Center?
- A self-contained campus where a small engineering team lives beside the compute it is building on. It couples three systems on one parcel — a live-in studio, an edge-in-a-box data hall, and the power and connectivity stack that carries both.
- Why put people on the site at all?
- Because the first sites are being proved, not operated. A resident team shortens the loop between something not working and someone with their hands on it, and it is the reason the second site is expected to be quicker than the first.
- What does off-grid mean here?
- Nothing on the pad is designed to depend on a public utility. Generation, storage, cooling and backhaul are all inside the fence line, and the interconnection queue is therefore not on the critical path.
- What land does a site need?
- The published land gates are design criteria rather than a shopping list — parcel size, road access, a setback from the nearest dwellings, buildable ground for the energy parcel, and a clear sky view for the gateway pad. They are published so a landowner can rule themselves in or out before anyone gets on a call.
- Is a site built yet?
- No. Xalant is pre-formation with no live sites. The first build is planned for South Oregon and everything on this page is design intent.
- How long does one take?
- The first build in South Oregon is planned to take up to nine months of controlled build. Every site after it is planned as a repeatable ninety days, plus local approval time.
Reference render
Site & capacity · Request