What is Imperal Cloud?
Imperal Cloud — the first ICNLI AI Cloud OS. Webbee 🐝 is its native agent: cloud-modular and Web 3.0-native, spanning your life and work.
If you're brand new, this page tells you the whole story in plain language. No jargon yet.
Here's the simplest way to understand Imperal Cloud: today your life is scattered across a dozen apps — mail, money, projects, notes, calendar, even whole servers — each with its own login and its own learning curve. Imperal Cloud is the one place you connect all of it into. From that moment on, you stop clicking through dashboards and start just saying what you want, in your own native language — and it happens. The technology is still there, doing serious work underneath; Imperal simply hides it behind the one interface every human already has: words.
Not a chatbot. Not "an AI assistant for business." An operating system for the AI era — where the user lives in natural language and the OS runs the rest of the user's work and life through a cloud-modular agent. The first ICNLI AI Cloud OS.
You write "send the Q3 report to Sarah" — Webbee sends it. You say "what was our biggest customer last month?" — Webbee answers from your real data. You ask "book me a flight to Berlin Friday morning, cheapest under $400, aisle" — Webbee books it across mail, calendar, payment, and travel APIs in one move.
It works because of three things: the agent (Webbee — Web 3.0-native, cloud-modular, persistent across surfaces), the web-kernel (the OS layer that orchestrates intent, action, audit, and recovery), and extensions — Python packages that hand Webbee new superpowers.
What's an extension?
An extension is a Python package that does one job well. Some examples:
Read inbox, send messages, search threads, draft replies.
notes
Create notes, organize folders, search content.
calendar
See your schedule, book meetings, find free slots.
sql-db
Run queries against the user's database, return rows.
web-tools
Lookup DNS, scan websites, fetch URLs.
spotify
Play music, queue tracks, control playback.
Each extension declares what it can do (in a manifest), and how to do it (in Python handlers). When a user types something, Webbee figures out which extension(s) to call, with which arguments, and runs them.
Where do extensions run?
You type:
"send the report to sarah"
↓
Imperal Panel UI (panel.imperal.io)
↓ HTTPS
Auth Gateway (auth.imperal.io) — checks who you are
↓
Webbee web-kernel — the brain
↓ runs your extension
mail extension → sends the email
↓
Webbee replies to you in chat: "Sent. ✅"You don't manage any of this — you write the extension code, publish it, and Webbee picks it up.
Who's "Imperal Cloud"?
Imperal, Inc. builds Webbee. Imperal Cloud is the platform where Webbee runs and where extensions get installed. As a developer, you interact with Imperal Cloud through three surfaces:
| Surface | What it's for |
|---|---|
| panel.imperal.io | End-user app. Where users chat with Webbee, manage settings, install extensions. |
| panel.imperal.io/developer | Developer Portal. Submit your extension, see usage, get paid. |
| docs.imperal.io | This site. Where you learn how to build. |
| auth.imperal.io | OAuth + federation. You'll use this when your extension needs to talk to third-party APIs (Google, Spotify, etc). |
What about "ICNLI"?
You'll see this acronym in some docs. ICNLI = Infrastructure Contextual Natural Language Interface — the open protocol behind Webbee that maps natural-language intent to context-aware infrastructure actions. Published at icnli.org under CC BY-SA 4.0.
You don't need to know ICNLI to build extensions. It matters when you want to understand the deep architecture or build a Webbee-compatible client of your own.
What does "federal-grade" mean here?
You'll see this phrase a lot. It means the platform takes guarantees seriously:
Tenant isolation
One user's data never leaks to another. Enforced at the web-kernel layer, not just by convention.
Audit chokepoint
Every action that touches user data is recorded with a federal retention class.
Runtime guarantees
The platform enforces a large set of runtime guarantees — tenant isolation, audit, anti-hallucination — and blocks changes that would weaken them.
Anti-hallucination
The platform protects chat from fabricated IDs, ungrounded data claims, and fake tool calls.
For you as an extension author, this means: the platform handles security, multi-tenancy, and audit for free. Your job is to write the business logic.
What you'll do next
Components showcase
Every Fumadocs UI component used across the Imperal Cloud docs, shown in action on one page — cards, callouts, tabs and more to copy-paste when authoring.
Quick Start — build an extension in 5 min
Build a Webbee extension in 5 minutes — install the Imperal SDK, write a typed handler, generate the manifest, smoke-test, and publish a deployed Hello World.