DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to self-host the scan server on your own GPU or Modal with Openreality

Run the full Open Reality server on your own GPU box or Modal account, with no account needed.

Credentials. The token printed at first start is your login to the server, so store it securely and never paste it into a shared chat or repo.

Who it is forA developer or team that wants to keep scans of private spaces on their own infrastructure.

The problemSending scans of private spaces to a third-party hosted service may not be acceptable for some projects.

The outcomeA running server you control, reachable by your MCP client through OPENREALITY_URL and a token.

What you need first

  • Node.js and npx, so the openreality-mcp package can run
  • An MCP-capable AI assistant such as Claude Code, Codex, Cursor, or Claude desktop
  • A phone video of the space you want to scan
  • A browser to complete the one-time sign-in (hosted service)

Steps

  1. Clone the repo: git clone https://github.com/reality-opened/openreality.
  2. Enter the server directory: cd openreality/server.
  3. Start on your own GPU box with python -m server.selfhost --data-dir ~/openreality-data, or deploy to your own Modal account with modal deploy modal_selfhost.py.
  4. Copy the single token printed at first start, since it is your login.
  5. Point the MCP client at your server using OPENREALITY_URL and that token.

Prompt for your agent

In the openreality repo, follow server/docs/self-hosting.md to start the server at <path or Modal target> and connect the MCP client using OPENREALITY_URL=<your server URL>. Verify that the MCP client can reach the server and that the token printed at first start is not committed to any file in the repo.

Caveat. The self-host paths are described as young, and the reconstruction model the server downloads is licensed for non-commercial use only, so commercial use needs a separate license from its owners.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page