Low-code and no-code platforms let teams build applications, forms, workflows and integrations with visual tools instead of conventional programming. Organisations use them for internal tools, process automation, citizen development and quick prototypes that connect existing systems.
These platforms are sovereignty-sensitive because one vendor combines three things: the application logic, the data it manages and the connectors to other systems, often with stored credentials for them. What you build is usually expressed in a proprietary model that only the vendor's runtime can execute, so leaving means rebuilding rather than moving. Check what can be exported, whether the runtime can be self-hosted, and which environment holds the connector secrets.
When evaluating a European option, look for open or documented formats for application definitions, a standard database underneath, an API for every object, audit logs, and a licence that lets you keep running the applications you built. Open-source platforms reduce dependence further, but consider who maintains them and how updates are delivered. Governance matters too: decide who may publish an app that touches personal data, and who reviews it.