> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/readme.md). # Eximee Low-Code Platform > **Eximee Low-Code Platform** a low-code platform of the **enterprise** designed with the specific needs of the banking sector in mind. ### **Purpose and idea of the platform** The world of banking is developing at a pace that traditional IT processes often cannot keep up with. Creating new products, implementing regulatory changes, or adapting customer experiences to digital channels requires ever greater flexibility.\ **Eximee Low-Code Platform** was created precisely for this purpose - to shorten delivery time, reduce dependence on development teams, and ensure full control over the lifecycle of business applications. The platform provides tools that allow product teams, analysts, and low-code developers to independently create, develop, and maintain applications - visually and without writing code. {% embed url="" %} ### **Why low-code for banking** Solutions built on Eximee meet all the requirements of banking environments: * they comply with security and audit requirements, * they support omnichannel architecture - one process can run in online banking, mobile banking, and in a branch, * they integrate with the bank's existing systems through integration components and API, * they take into account WCAG accessibility standards and regulatory requirements. Thanks to this, Eximee enables banks to deliver **coherent and regulation-compliant digital services**, without the need to build them from scratch. ### **What problems does Eximee solve** The platform was created as a response to the most common challenges of banking projects: * long software development and testing cycles, * process fragmentation across different channels, * high maintenance costs of many parallel applications, * lack of tools that enable quick response to business needs. Thanks to its flexible architecture, shared components, and graphical process editors, Eximee allows **to reduce the implementation time of new solutions by even several dozen percent**. ### Areas of use The Eximee Platform is used primarily in the banking sector, supporting various business processes both on the customer side (*front-office*), as well as within the organization (*back-office*). The main areas in which Eximee Low-Code Platform is currently used in banks: * Digital onboarding and KYC, * Bank product sales, * Self-service banking and after-sales service, * Internal processes and regulatory compliance (back-office), * Tools supporting the work of bank employees, * Surveys and satisfaction studies (NPS, CES, CSAT), * Special projects and inter-institutional integration. More on this topic can be found in the chapter [Areas of use of Eximee Low-Code Platform.](/documentation/documentation-en/wprowadzenie/obszary-zastosowania.md) --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.eximee.com/documentation/documentation-en/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.