The core chapter of the Neblla guide — the SDK's base contract. Mandatory: every other chapter assumes what is here. # Neblla — core ## What it is **Your idea. Let's make it. Build your game, app or website in minutes, for free.** The backend and back office for your game, your app or your store: users, data, payments, real-time multiplayer rooms, community, AI and a dashboard to run it all. **You write the app, Neblla handles everything behind it** — the parts that would otherwise need a server of your own: user accounts that work across every Neblla app, saved data, payments, user-published content, friends, AI, a back office and, when more than one device is involved, rooms with a clear authority. Multiplayer is one of those modules, not a requirement. Loaded with one ` ``` When the page loads, `onNeblla` runs with the SDK already connected. The script tag does NOT need `type="module"`. If the SDK cannot start, `onNeblla` does not run and you are told once: define `window.onNebllaError = (detail) => { ... }` or listen for the `neblla:error` DOM event (same `detail`). `detail.code` is `unreachable` (Neblla could not be contacted) — also when the SDK tag itself fails to load (`detail.stage` is `tag`): on pages Neblla serves the tag already carries that `onerror`; on a site of your own put `onerror="window.onNebllaError&&window.onNebllaError({code:'unreachable',stage:'tag'})"` on your `