Core concepts / 4 minute overview
How Elyxis fits together
A practical map of Environments, Settings, Keystores, Plugins, Flows, Apps, and capabilities.
Last verified 2026-10-19Follow one example
Suppose you want to classify support tickets and return an urgency level. You describe the outcome to the Assistant. The pieces below give Elyxis a place to work, the right configuration, and the building blocks to make that outcome executable.
Environment: Sandbox
Settings: model choice, service endpoints, secret references
Keystores: credentials used by those references
Installed Plugins + Environment configuration
→ Flow → Draft App → App → callable capability
This is a guide to the relationships. Elyxis may reuse an existing compatible capability or App instead of creating each resource again.
Where each piece belongs
| Concept | In the support-ticket example |
|---|---|
| Environment | The Sandbox scope in which you create and run the work during the beta. |
| Settings | The approved model and other configuration entries for that Environment. |
| Keystore | A named store holding or connecting to the model provider credential. |
| Plugin | An installed building block that can call the model or connect to a service. |
| Flow | The definition of the processing steps and how data moves between them. |
| App | The runnable application produced from that definition and its configuration. |
| Capability | The function you call with ticket text to receive an urgency result. |
A sensible order for setup
Start by choosing an Environment you are allowed to use. Inspect the installed Plugins and their requirements. Prepare any Keystore references and Settings the selected integration needs. Then ask Elyxis to create or reuse the capability, run it with sample input, and inspect the returned result.
You can ask the Assistant to explain missing prerequisites as you go. Knowing a resource's name helps you target it; it does not grant permission to use it.
Understand Environments