The blog

Built in public, written the same way: notes on the protocol, the architecture, and what we're actually shipping.

Developers

Imperal SDK: The API Surface for Building on Imperal

pip install imperal-sdk. Auth, billing, storage, and validation handled by the runtime, you write what your extension does, and get paid per action.

SDKDevelopersMarketplace
imperal.io Team · 4 min
Product

One Webbee, Every Surface: The Same AI Agent on Panel, Terminal, and Messenger

Panel, terminal, Telegram, one agent, one memory, one context. Switch surfaces and nothing gets left behind, because nothing was ever tied to the surface.

SurfacesTelegramPanel
imperal.io Team · 6 min
Product

Webbee Code: The AI Coding Terminal That Doesn't Forget What You Were Doing

Close the laptop, come back tomorrow, say 'continue', and she picks up exactly where she left off. Session state that survives the process, not just the prompt.

Webbee CodeTerminalCoding Agent
imperal.io Team · 5 min
Product

Bring Your Own LLM: Running Imperal on Your Model, Your Infrastructure

Platform default, your own API key, or your own OpenAI-compatible endpoint on your own hardware: BYOLLM is real, functioning, and Enterprise-gated today.

BYOLLMInfrastructureSelf-Hosting
imperal.io Team · 5 min
Security

AI Agent Safety: Why a Hallucination on Imperal Can't Actually Do Damage

Most AI guardrails are just prompt text a model can be talked out of. Imperal's kernel mechanically blocks writes until you confirm, a code path, not a promise.

SafetySecurityKernel
imperal.io Team · 6 min
Protocol

ICNLI Protocol: Why AI Needs a Standard for Operational Context, Not Just the Internet

Memory features are a patch on an amnesiac design. ICNLI is the open, licensed protocol that actually specifies what an AI needs to know before it acts.

ICNLIProtocolArchitecture
imperal.io Team · 6 min
imperal.io