Skip to content
Documentation

Introduction

Loor is a unified control plane for shipping software — operator-grade DevOps plus a Claude-powered browser IDE on the same physical infrastructure.

Welcome to the Loor docs. Most of what's here you can skip — Vibe Chat will walk you through it inside Studio. These pages are for when you want to understand what's happening, pin a particular knob, or share a link with a teammate.

What is Loor?

Loor is two things wearing one badge:

  • Loor Studio — a browser IDE with an AI teammate (Vibe Chat), file editor, terminal, source control, and a deploy button that actually works.
  • Loor DevOps — the control plane underneath: bare-metal aware, plugin-based services (MongoDB, Redis, R2), automated TLS, branch previews, and a single declarative manifest in loor.json.

Both live on the same physical infrastructure. You can ignore one and use the other; most people end up using both.

How it's different

Other tools split your day across five tabs. Loor merges them:

  • The IDE and the production environment share the same machines — no "works on my laptop" gap.
  • The AI teammate has shell, file system, and deployment access — not just code suggestions.
  • Configuration is one manifest checked into your repo, not click-paths through five dashboards.

Start here

Two paths, depending on how much you want to read first:

Browse by section

Everything in the sidebar, grouped:

Get help

Stuck on something? A few options:

  • Press ⌘ K anywhere on the docs to search.
  • Ask Vibe Chat directly — it has these docs loaded.
  • Email [email protected] or ping us on X.