> For the complete documentation index, see [llms.txt](https://doc.exoway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.exoway.io/overview/our-features.md). # Our Features **Features that save your time:** * **Building the schema through drag-and-drop :** With its whiteboard system, visualize your entire infrastructure and spot potential issues at a glance, even before deployment. * **Catalog of resources from your cloud provider :** Exoway integrates all the components from the cloud provider into its catalog. The two steps of schema in diagram and then building the architecture are now one and the same step! * **Schema consistency check :** By integrating rules specific to each cloud, the platform allows you to avoid potential compatibility issues between components during deployment. * **One project, multiple environments :** One blueprint = one schema = one environment for development, QA, staging, training, production. Your project can contain multiple blueprints, for better management of permissions and changes. * **Modification history :** Need to roll back? Exoway keeps a complete history of changes to your infrastructure. With just one click, you can restore the version that best suits your needs. * **Detect possible errors and failures :** The platform provides you with real-time feedback on compatibility issues, errors, and potential failures in your infrastructure and code repositories. * **Control the financial cost per hour :** Exoway directly integrates the official catalog of each cloud provider. The tool provides you with real-time information on the cost of your infrastructure. * **Check the carbon footprint of your infrastructure :** Exoway has developed an algorithm based on ADEME studies to calculate the carbon impact of your infrastructure according to the resources used from each cloud. * **Add annotations and comments :** For added flexibility, the solution allows you to annotate each component of your schema. A useful feature for better collaboration with your peers. * **Control the roles of each user :** Assign differentiated roles for each user to avoid errors (it's human!) with [Role Based Access Control](#user-content-fn-1)[^1]. * **Export your schema as an image :** Need to present your architecture to your manager or client? Download a preview of the schema in JPG format, to integrate into your presentation. * **Deployment event log :** Track the status of your deployment in real time. View statistics for each of your projects. Quickly identify anomalies. * **Integration of observability statistics :** With the integration of your monitoring tool, track your metrics: CPU usage, memory usage, disk read/write, network I/O, Kubernetes pods, etc. * **Simplified tracking of logs on your infrastructure** : Follow the logs on your infrastructure at a macro level with the integration of your preferred log management tool. * **Automated security analyses on code repositories :** A security analysis is automatically triggered for each code repository. A report is sent to the user to detect any existing system vulnerabilities. * **Secure authentications :** We have integrated all the necessary features to ensure the security of your architecture => mandatory two-factor authentication, recovery codes, and a history of account logins. [^1]: Role-based access control (RBAC) refers to the idea of assigning permissions to users based on their role within an organization. It offers a simple, manageable approach to access management that is less prone to error than assigning permissions to users individually. --- # 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://doc.exoway.io/overview/our-features.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.