> ## Documentation Index > Fetch the complete documentation index at: https://docs.devias.io/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > The docs are served at https://docs.devias.io. Every path in these docs is relative to that root: /llms.txt is https://docs.devias.io/llms.txt. > Devias is an open-source platform that works as an operating system for a business: a core (records, views, workflows, agents, permissions) with installable modules. > Pages are typed by folder. concepts/ explains what things are, guides/ gives procedures, reference/ is exhaustive (SDK, CLI, HTTP API), operate/ covers hosting. Use /start/glossary for exact terms. > Every id in a module (module, object, field, view, action, workflow, step, connection, variable, event, policy) is a uuid. Generate them with `devias id `. Never invent dotted or readable ids. > Run `devias plan` and read its output before `devias apply`. Apply only what the plan says. > The OpenAPI document, including the routes of the modules in the reference setup, is at /reference/api/openapi.json. > Devias is young and changes quickly. If a page and the source repository (github.com/devias-io/devias) disagree, the repository is right. # What Devias is > Devias is an open-source platform that works as an operating system for a business. A core provides records, workflows, agents and permissions, installable modules add areas such as CRM and invoicing, and it runs on your own server. Devias is an open-source platform that works as an operating system for a business. A **core** provides records, views, workflows, tasks, documents, agents and permissions. **Modules** add areas of the business on top: customers, quotes, invoices, payments, expenses, products and stock. Everything runs on one server, in a database you control, and everything shares the same records. ![The Devias studio: a Home dashboard with money in, pipeline and tasks, and the assistant panel open with an approval card for a comment on a deal](https://mintcdn.com/devias/TzMNPlq81mH0Qrj7/images/studio-assistant.webp?fit=max\&auto=format\&n=TzMNPlq81mH0Qrj7\&q=85\&s=3073199d4f4ae3f42cb4e8a6b3e184a7) The Home page of the studio, with the assistant asking before it changes a deal. ## Parts of Devias | Part | What it is | | - | - | | Core | Records, views and layouts, workflows, tasks, documents, notifications, agents and skills, roles and permissions, connections, the HTTP API, the SDK and the CLI. | | Modules | Packages that add one area of the business: objects and fields, views, actions, workflows, connections, agents. Examples: CRM, Quotes, Invoicing, Payments via Stripe. | | Studio | The React web app people use. | | Server | An HTTP API with a data engine over Postgres. | See [Architecture](https://docs.devias.io/concepts/architecture.md). ## Properties * **Modular.** Each area of the business is a module. Modules are installed from a reviewed plan, and a workspace can build its own. See [Modules](https://docs.devias.io/concepts/modules.md). * **Data defines the product.** Objects and fields are stored as data, so a field added in Settings and a field a module ships behave the same, and a change needs no rebuild. See [Data model](https://docs.devias.io/concepts/data-model.md). * **Agents with limits.** An agent acts with the role of the person who asked. Each of its tools runs freely or asks first, and every change is logged. See [Agents](https://docs.devias.io/concepts/agents.md). * **Open and extensible.** The platform is under the AGPL-3.0. The SDK, the UI kit and the CLI are MIT. There is a React studio, TypeScript modules, a typed SDK and an HTTP API described in OpenAPI. * **Self-hosted.** It runs on your own server with Postgres, or with an embedded database to try it. A hosted cloud version is planned and has no price yet. ## When Devias fits * A business process does not fit a standard CRM or ERP, and the data, rules and hosting should stay under the company's control. * A team or agency builds operations software for clients and wants a base to build on instead of an empty repository. ## When Devias does not fit yet * The need is a fully mature, hands-off product today. Devias is young and changes quickly, and some areas are rough. * Nobody can write TypeScript, and the need goes beyond what Settings and the assistant can configure. * Other agents, such as Claude or ChatGPT, must use Devias directly. Connecting them through MCP is planned. Today the agent inside Devias uses the same actions as the app. ## Find a page by need | Need | Page | | - | - | | Run it on one machine | [Quickstart](https://docs.devias.io/quickstart.md) | | Learn the ideas | [Architecture](https://docs.devias.io/concepts/architecture.md) and [Data model](https://docs.devias.io/concepts/data-model.md) | | Look up a term | [Glossary](https://docs.devias.io/start/glossary.md) | | Work in the studio | [Navigate the studio](https://docs.devias.io/guides/studio/navigate-the-studio.md) | | Build a module | [What a module is](https://docs.devias.io/guides/modules/what-a-module-is.md) | | Call it from code | [HTTP API](https://docs.devias.io/reference/api/overview.md) and [TypeScript SDK](https://docs.devias.io/reference/sdk/client.md) | | Host it | [Deploy](https://docs.devias.io/operate/deploy.md) | | Read these docs as an AI agent | [Use these docs with AI](https://docs.devias.io/start/use-with-ai.md) | This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.