Build chat for AI-native apps

A name you will meet in the SDK

Why does “floo” keep appearing?

Before floo was a package name, it was a handful of magic. In the Wizarding World, you scatter Floo Powder into a fireplace and ordinary flames flash emerald green. The hearth is no longer a hearth—it is a doorway, and somewhere beyond it an entire network is waiting.

Speak one clear destination and the hidden passages wake. Countless fireplaces become connected points on the same enchanted map; the network finds the right one, opens a route, and lets a traveller vanish here and step out there. Miles collapse into a moment. What matters is not how far the message must travel, but where it belongs.

That is the feeling behind the SDK's original codename. You do not step into the flames—you place a message in the SDK and name a user, group, or device. floo is the passage behind the fireplace: it crosses networks, finds the right destination, delivers the message, and keeps the way open for the reply. Names such as floo-web, floo-ios, and im.floo.floolib are traces of that magic preserved for compatibility, not a separate product or service.