CloudWinks · Foundation apps

WorkerBeeTechnical brief

WorkerBee is the CloudWinks AI engine. People and apps use it for AI chats, single agents and teams of agents that work together, on any registered AI model, with access to the world and to application data only through approved tools.

Read the business brief · PDF

1. Architecture in brief

WorkerBee is a Foundation app with personal and company ownership. Runs execute in a WorkerBee service in the C# API; SQL functions record runs, and Conductor starts timed runs. Chats, agents and swarms share one model: published versions are immutable, branches are GoldenRule decisions (a rule key or an inline condition), and swarms are built with limits on members, rounds, tokens and time. A model registry pins a primary model and fallbacks on each version and records the model used.

2. Service boundary and intake

People start chats and agents in the shared AI panel in any app; apps call agents by key; TheBoss queues AGENT steps; Conductor starts scheduled runs. Triggers stay with the apps and Conductor, and all field mapping uses TheIntegrator mapping definitions by key. Tools are AI models, allow-listed app functions and views (called server-side with the person bound), CosmosCall, BigTalk, registered MCP servers and GoldenRule decisions; there is no raw SQL MCP and no prompt URLs.

3. Data handled

The model holds agents, chats, swarms, versions, tool templates, the model registry with company allowed lists and budgets, runs and chat messages. Runs keep their outcome and an input hash; chat messages are kept for a retention period and then archived. A chat can be bound to any app record, with an optional BullChat link, history and a rolling summary. Agent templates include landman.valuation.avm, the DreamDrafter drafting, market-research and assumption-check agents and plan swarm, and platform.translate. Old seeds and package tables are archived.

4. Integrations and ownership

TheBoss hands off AGENT steps and approvals stay there; TaskMaster holds tasks; GoldenRule supplies branch decisions; TheIntegrator supplies mappings; Conductor times runs; CosmosCall and BigTalk are the outside channels; MediaMogul holds files. LandMan receives AVM estimates with a confidence range and cited comparables; DreamDrafter receives marked, cited drafts the owner accepts; TheReporter and DreamDrafter use the translation agent for Spanish and English output.

5. Security and access

An agent runs with the starting person’s KeyKook rights, narrowed to its declared tools. App functions are allow-listed per tool template and called server-side with the person bound, with KeyKook’s application check. Secrets stay in KeyKook. Companies set allowed models and budgets. AI chats are kept apart from people-to-people chats.

Competitive context

AlternativeIts focusCloudWinks product focus
Microsoft Copilot StudioAgents that choose tools, topics and other agents.Chats, agents and swarms on any registered model, acting only through allow-listed CloudWinks tools.
ZapierAutomated workflows and AI steps across connected apps.One AI engine and shared AI panel inside every CloudWinks app, bound to the starting person’s rights.

Read the business brief →

← More Foundation apps apps · All application briefs · How the framework works