> For the complete documentation index, see [llms.txt](https://docs.deref.io/exo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deref.io/exo/using-exo/concepts.md). # Concepts ## Workspaces Maps an Exo projects to a directory on your filesystem. Most projects have one workspace rooted at the same directory as their checked out code. This is how `exo` knows what project you're working on based on your current working directory. If run in an unmapped directory, `exo gui` will offer to create a workspace for you. You can determine the current workspace with `exo workspace`, initialize a new one with `exo init` or delete the current workspace with `exo workspace destroy`. ## Manifests A file describing all of the components in a project. In addition to Exo's prefered [exo.hcl](/exo/manifests/manifest.md) format, Exo also supports [procfiles](/exo/manifests/migrate/procfiles.md) and [compose files](/exo/manifests/migrate/compose.md). Use `exo apply ./path/to/manifest` whenever your manifest changes to make your workspace match. Components will be added or removed accordingly. ## Components An abstract definition of resources managed by exo. Presently, the only supported type of components are *processes*. Each component has a unique name within a workspace. Components are manipulated by applying manifests (see below), or with CRUD operations such as `exo ls`, `exo new`, and `exo rm`. ## Resources Resources are the underlying stateful entities managed by components. Usually, there is a one-to-one relationship a component and its managed resource. The distinction matters for some future scenerios, such as zero-downtime deployments. ## Daemon A background service that manages components and supervises processes. Most commands start this service automatically. You can start it explicitly with `exo daemon` and terminate it with `exo exit`. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.deref.io/exo/using-exo/concepts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.