Genesis — 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
Platform
Converse, configure, delegate, execute.
Cyclones Cloud separates four roles so work stays legible: Cosmos to converse, Genesis to configure your AI coworkers, Orbit to follow tasks, Gateway to execute them.
OrbitOrbit — 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
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
Converse, configure, delegate, execute.
Converse
Cosmos
The conversational workspace with available models and assistants.
Ask a question, attach a document, use connected tools and prepare an answer. It is also the everyday entry point to the environment.
Cosmos is not a universal search engine across all your data: it works with the documents and tools that are accessible.
Learn more — CosmosConfigure
Genesis
The workshop where specialized AI coworkers are created.
Define their responsibility, instructions and the tools they can use. Where configuration allows, organize them into teams.
Configuring a coworker starts no work: tasks are handed over afterwards, in Orbit.
Learn more — GenesisDelegate and follow
Orbit
The workspace for autonomous tasks.
Tasks, schedules, memories, skills, briefing, analytics and permissions: Orbit shows what has been delegated, to whom, and where the work stands.
Orbit displays and organizes execution; it is not what runs it.
Learn more — OrbitExecute
Gateway
The runtime dedicated to autonomous tasks.
Gateway takes queued tasks, triggers scheduled ones, connects configured channels and calls application tools within the defined access.
Gateway is not an application you open: it is the technical layer that carries the work.
Learn more — Gateway
Interface reconstruction · fictional data
How a task moves through the platform
- Person
You describe a need in Cosmos or configure a role in Genesis.
- Person
You delegate a task, or schedule a recurrence, in Orbit.
- Application
Gateway queues the task and runs it with the chosen model.
- AI coworker
The coworker uses the permitted tools: read, write or approval request depending on the setting.
- Person
The result comes back in Orbit, and on a configured channel if you have one.
What connects the four
Applications
Business management, Veloce, Creative Studio and workflows expose tools that coworkers can use, if you allow it.
Access
Each tool category has its level: off, read only, ask first or full access.
Models
Multiple providers are supported. Available models depend on the execution mode and your configuration.
What work would you delegate to AI?
Start with your use cases, applications and the level of delegation you want to introduce.