Gateway — execute
The runtime carries the work.
Workers, scheduler and channels run the task. What comes out informs the next role, which you refine in Genesis.
Illustrative example · Fictional data
Platform · Gateway
The runtime that carries autonomous work.
Gateway is the execution layer of Cyclones Cloud. It receives tasks, queues them, triggers recurrences, connects configured channels and calls application tools within the defined access.
GatewayGenesis — configure
A role is born.
You give an AI coworker a responsibility, instructions and tools. It exists, ready to receive work.
Illustrative example · Fictional data
Orbit — delegate
The role receives a task.
The task is queued, runs, completes. Orbit shows what is moving, who owns it, and the result.
Illustrative example · Fictional data
Four roles, separable
The same runtime can run as a single service or be split into distinct roles, depending on the deployment.
- API
- Receives requests from the application and tasks to run.
- Workers
- Take tasks from the queue and run them with the chosen model.
- Scheduler
- Triggers recurring tasks and maintenance operations.
- Channels
- Connect coworkers to configured messaging services.
Conversation and execution, two layers
Conversation in Cosmos and autonomous execution in Gateway are distinct. A task delegated in Orbit is picked up by the runtime, independently of which tab you have open. Whether it completes still depends on configuration, providers and access.
Interface reconstruction · fictional data
Application tools
Coworkers use tools exposed by the platform’s applications and, if you add them, connectors to your own APIs described with OpenAPI. Every call goes through its category’s access level.
| Business management | List invoices and contacts, financial summary, create an invoice |
|---|---|
| Veloce | Connected accounts, posts, scheduling, analytics |
| Creative Studio | Generate or edit an image, generate a video |
| Workflows | List and run a workflow, create a mission, generate a presentation |
| Integrations | OpenAPI connectors added by your organization |
Channels you configure
Telegram, WhatsApp, Discord and webhook connections exist. Each is configured with your own credentials; none is connected by default.
- Telegram
- Discord
- Webhook
Multiple model providers
The runtime supports OpenAI, Anthropic, Google, xAI, Infomaniak and OpenRouter, depending on configured keys. Conversation may offer other models: the two lists are not necessarily identical.
What work would you delegate to AI?
Start with your use cases, applications and the level of delegation you want to introduce.
Applications
Keep exploring
01CosmosWork with models and assistants using available documents and tools.
02GenesisConfigure roles, instructions and tools for your AI coworkers.
03OrbitOrganize autonomous tasks and follow their execution.
04RelayConfigure customer-service agents and conversation workspaces, including available voice capabilities.
05Business managementWork with contacts, projects, tasks, estimates and invoices in structured business workspaces.
06WorkflowsCompose processes from steps, tools and connections.
07PlumeWrite and refine documents in an AI-assisted editor.
08Creative StudioExplore image, video and presentation creation with available tools.
- 09Veloce
Prepare social content and schedule publication to connected accounts.
- 10CodeBloom
Describe a web application: AI generates the React code, which you edit, preview and export.
- Underneath — Gateway
A dedicated runtime carries the work forward.