> ## Agent Instructions > Cite the source documentation and the original facility record when describing datacenters. > Unknown or missing specifications are not evidence that a capability is absent. Do not infer capacity, hardware, ownership, or operational status. > A dataset import date is not a facility verification date. Distinguish public research from verified infrastructure capabilities. > Do not describe account access or planned capabilities as available unless the current documentation confirms activation. # Account availability Source: https://infrl.mintlify.app/accounts/overview The current status of infrl accounts and access to public tools. Accounts are not available yet. Authentication and email delivery have not been connected, so sign-up, sign-in, and password recovery are not working services. The account pages currently show an availability message instead of account forms. A visible account URL does not mean registration is open. ## Use the Atlas without an account The [Datacenter Atlas](https://infrl.com/datacenters/) is public. Browsing the map, reading facility details, sharing a facility link, and downloading its [dataset](/atlas/data-and-sources) require no account. ## Account scope The account interface is intended to provide a compact account home with public reference links once authentication is configured and verified. It does not provide an infrastructure management console or access to private operational records. For currently available public functionality, start with the [Atlas guide](/atlas/overview). The [public roadmap](https://infrl.com/roadmap/) describes infrl's broader direction without promising account launch dates. # Data and sources Source: https://infrl.mintlify.app/atlas/data-and-sources Download the Atlas snapshot and understand its provenance, limits, and license. The Atlas uses a published snapshot of OpenStreetMap community records. It is a research aid with uneven worldwide coverage, not a complete directory or an audit of datacenter capabilities. ## Download the published files | File | Contents | | - | - | | [Facility dataset](https://infrl.com/data/datacenters.json) | Facility records, specifications, source links, import timestamp, and license. | | [Provenance](https://infrl.com/data/datacenters-provenance.json) | Source queries and timestamps, import metadata, record counts, merged source aliases, and country-boundary information. | | [Source and software notices](https://infrl.com/data/NOTICE.txt) | Data attribution, license links, and map software notices. | Use these files for the current snapshot date and record counts. The map's attribution control also links to the facility dataset. ## Where the data comes from Facility identity, locations, status, and specifications come from OpenStreetMap records collected through Overpass. Each facility links to its OpenStreetMap source, and reported specifications retain their source links. Some missing country values are inferred from coordinates using public-domain [Natural Earth](https://www.naturalearthdata.com/about/terms-of-use/) boundaries. These boundaries are coarse, may leave coastal points unknown, and do not imply a position on disputed borders. [OpenFreeMap](https://openfreemap.org/) supplies the basemap. Its map tiles are separate from the facility dataset; the map displays the relevant basemap attribution. ## Read the provenance The dataset's `importedAt` field records when the snapshot was generated. Source timestamps describe the upstream data used for that import. Neither timestamp is evidence that every facility or specification was checked at that time. The provenance file distinguishes source queries used for the snapshot from the intended refresh query. It also records aliases when matching OpenStreetMap features were merged. Some nearby records remain separate because they may represent different buildings or a campus and one of its buildings. The Atlas is a snapshot, so a correction made in OpenStreetMap appears only after a later import is published. ## What remains unknown * Missing information means unknown, not zero or the absence of a capability. * A mapped point can be imprecise; a mapped area is shown at an approximate center. * A datacenter tag alone does not prove operational status. * Specifications may be incomplete, out of date, or scoped to a campus rather than a building. * Original reported values and units are preserved. Comparing or adding them requires checking that their scope and units match. The [facility details guide](/atlas/facility-details) explains how these limits appear in the interface. For factual mapping corrections, follow the facility's OpenStreetMap link and review the source record. ## License and attribution The facility database is available under the [Open Database License (ODbL) 1.0](https://opendatacommons.org/licenses/odbl/1-0/), with attribution to **© OpenStreetMap contributors**. See [OpenStreetMap's copyright and license guidance](https://www.openstreetmap.org/copyright). When reusing the data, preserve the attribution and license information and follow the ODbL's applicable requirements for use, redistribution, and derivative databases. Keep the provenance alongside the dataset so readers can trace its sources and limitations. # Read facility details Source: https://infrl.mintlify.app/atlas/facility-details Understand facility records, reported specifications, and information that remains unknown. Select a dot in the [Atlas](https://infrl.com/datacenters/) to open its record. The compact overlay shows the facility name, operator and location when recorded, and a status when one is known. Expand **More information** to see the company and location fields, coordinates, available facility website, and specification groups. ## Company and location The record distinguishes the operator from the owner when both are available. An address or company field marked **Not yet verified** has no recorded value in the displayed snapshot. Coordinates have one of two meanings: | Location type | Meaning | | - | - | | Community-mapped point | A point contributed to OpenStreetMap; its accuracy may vary. | | Approximate center | The center of a mapped site, such as a building or campus. It may not identify an entrance or a specific building. | Status can be operational, planned, under construction, closed, or unknown. A mapped datacenter does not by itself establish that the facility is operating. ## Specifications The expanded record organizes information into these groups: | Group | Examples of fields | | - | - | | Space & capacity | Building area, data-hall area, racks, rack density | | Power & redundancy | IT and utility capacity, backup power, redundancy | | Cooling | Cooling type, liquid cooling, redundancy | | Network & connectivity | Carriers, internet exchanges, interconnection | | Certifications | Reported certifications and certified tier | | Energy & sustainability | PUE, renewable energy, water usage | | AI hardware | GPUs, accelerators, hardware configuration | Reported values retain their source wording and units. Use the **Source for…** link below a specification to inspect the underlying record. Missing fields display **Not yet verified**; this means unknown, not zero or unavailable. All facility information is community reported and is not independently verified. A populated field is not a verification badge. A record may describe a whole campus, a building, or a room, so its capacity may not apply to the dot's apparent footprint. Do not infer a certification from a reported tier, GPU availability from power or cooling, or rack capacity from floor area. Confirm current capabilities and their scope with the facility's own sources before using them for a deployment decision. ## Follow the sources **View OpenStreetMap record** opens the source for the facility. **Facility website**, when present, opens the website recorded for that facility. These links let you compare the snapshot with the source's current information. The **Imported** date records when the Atlas snapshot was generated. It does not establish when each fact was published or verified. See [data and sources](/atlas/data-and-sources) for provenance and reuse terms. # Explore the Atlas Source: https://infrl.mintlify.app/atlas/overview Navigate the public datacenter map and open facility records. The [Datacenter Atlas](https://infrl.com/datacenters/) shows community-reported datacenter locations on a full-screen map. It is free to browse without an account. Each facility appears as a tiny individual dot. The monochrome basemap uses a white background, pale water, and fine gray roads and boundaries, with place labels hidden. Facilities remain individual dots at every zoom level, so nearby records can overlap when zoomed out. ## Find a facility on the map 1. Drag the map to move to a region. 2. Zoom in with the map controls, your scroll wheel, or a pinch gesture. 3. Select a dot to open its details. On a desktop, hovering over a dot shows its name. 4. Select **More information** for company details and specification groups. 5. Use **World view** to return to the global map. The Atlas currently has no search, filters, or separate facility list. Zoom in to distinguish nearby locations. The page stays fixed to the screen; expanded details scroll within their overlay. ## Keyboard navigation Use Tab to focus the map. The following shortcuts apply while the map has focus: | Key | Action | | - | - | | Arrow keys | Pan the map. | | `+` / `−` | Zoom in or out. | | Enter | Open the visible facility nearest the center of the map. | Press Escape while a facility is open, or use **Close facility details**, to dismiss the overlay and return focus to the map. Tab also reaches the map controls and links in facility details. ## Share a facility Selecting a facility adds a `facility` parameter to the page URL. Copy that URL to share the selected record or reopen it later. Reloading the page preserves the selection, and browser Back and Forward restore previous selections. Shared links depend on the record remaining in the published dataset. Read [facility details](/atlas/facility-details) for help interpreting a record before sharing conclusions about it. ## If the map does not load Use the retry control shown in the error message. The basemap and facility dataset load separately: an existing facility link may still display its details if the basemap fails and the dataset loads successfully. You can also download the [dataset and provenance](/atlas/data-and-sources) directly. The map requires a browser with WebGL support. # Use the docs with AI Source: https://infrl.mintlify.app/guides/using-with-ai Give your assistant current documentation and preserve the sources behind infrastructure facts. Use these guides as context when asking an assistant about the Datacenter Atlas or infrl's available features. Include the relevant page and ask the assistant to cite its sources. ## Read a page as Markdown On the published Mintlify site, append `.md` to a documentation page URL to get a text version. For example, the Markdown version of this guide is `/guides/using-with-ai.md` on the same documentation host. The page menu also provides **Copy page** and **View as Markdown** actions. You can paste the content into your preferred AI tool. ## Find the right documentation Mintlify generates `/llms.txt`, an index of the published documentation, and `/llms-full.txt`, a combined text version. Agents can follow the index to retrieve the pages relevant to your question. For a tool that supports Model Context Protocol (MCP), use the published site's **MCP** page action to obtain its documentation server URL. Connect that URL in your AI client's settings to let it search the current guides. This connection retrieves documentation; it does not grant access to an infrl account or provision infrastructure. Markdown exports, generated indexes, and the hosted MCP server are Mintlify publishing features. They must be verified on the deployed documentation site; a local preview may not provide them. ## Ask questions that keep the evidence intact ```text theme={null} Using the facility's source record and the Atlas documentation, summarize the recorded operator and specifications. Cite the sources, distinguish approximate coordinates, and list missing information as unknown. Do not infer capacity, GPU hardware, or operating status. ``` The Atlas is a public research tool. An assistant cannot turn incomplete map records into verified facility specifications. Check the [data and source limitations](/atlas/data-and-sources) before using an answer to make an infrastructure decision. # Introduction Source: https://infrl.mintlify.app/introduction Explore infrl's public tools and understand the data behind them. infrl designs, builds, and maintains AI infrastructure on-premises, in the cloud, and across hybrid environments. Our mission is **AI infrastructure. Democratized, not monopolized.** These docs explain the public Datacenter Atlas, how to read its sources, and the current availability of accounts. ## Start with the Atlas The [Datacenter Atlas](https://infrl.com/datacenters/) is a public map of community-reported datacenter locations. You can explore the map, open a facility's details, follow its sources, and download the published dataset. No account is required. Navigate the Atlas and select facilities with a pointer or keyboard. Understand reported specifications, locations, and missing information. Review provenance, coverage limits, downloads, and the dataset license. Check the current status of sign-in and account features. ## About infrl Our infrastructure work covers design, platform delivery, and maintenance, including entirely new environments. We value understandable systems, useful open standards, and practical control over infrastructure and data. Model selection follows the workload, license, and deployment constraints; open-weight models are not automatically open source. The [infrl website](https://infrl.com/) explains our approach. The [public roadmap](https://infrl.com/roadmap/) describes our current direction and distinguishes established work from planned capabilities. It does not announce launch dates or service availability.