No lock-in & portability

Open architecture. Open formats. Documented migration paths. You can leave.

Not because you have to. Because you can, and that's what makes staying a choice instead of a trap.

Concretely

  • Open-source foundation (Drupal, Mautic, Apache Unomi)

    The components your DXP is built on are community-governed, not proprietary code only Dropsolid can touch.

  • Open APIs, documented and stable

    Every integration is built against a published interface, not private, undocumented endpoints.

  • Standard data export formats

    Content, customer profiles, and configuration all come out in formats other systems can actually read.

  • Documented migration paths

    Leaving isn't a theoretical right; there's a defined process for it.

  • The model gateway lets you swap LLMs and embedding models

    Your AI use cases aren't wired to one vendor's model.

  • Full code ownership (Mautic Pro, Mautic Enterprise, And Drupal Managed Cloud)

    You own the code, not just a license to run it on Dropsolid's terms.

What "no lock-in" actually covers

Most vendors say "open" and mean "the CMS." That's not enough on its own, a modern platform has more places lock-in can hide. Dropsolid AI's freedom-to-leave commitment is designed to cover all five:

Layer What's covered
Platform Not just your Drupal site, the core components your DXP is built on
Infrastructure Move between Dropsolid hosting, your own infrastructure, or another cloud provider, including hybrid and Kubernetes-based setups
Data Customer profiles, segmentation logic, campaign and journey data, consent records, personalisation rules, not just page content
AI Prompts, guardrails, evaluation logic, and the model/vector-database choices themselves
Contractual Defined exit rights and migration support, in writing, not a goodwill promise

The reasoning: content portability alone isn't sovereignty if your customer data platform or your AI layer is still locked to one vendor. All five layers have to be portable, or you're still trapped somewhere.

The honest exception

Not every component is open source today. The CDP interface and parts of the orchestration layer are Dropsolid IP. For those pieces, the commitment isn't "it's secretly open," it's a defined contractual path:

A perpetual license to the then-current version of the proprietary components, for internal use, available for a defined fee

Exit services to help install, configure, and validate the stack on infrastructure of your choice

After that, you run and evolve your own fork, with the option to contract Dropsolid AI for further support if you want it

What stays with Dropsolid AI is the multi-tenant orchestration layer that runs many DXPs at scale, not something a single customer would take over anyway. What leaves with you is everything that represents your organisation's own data and intelligence: content, configuration, customer data, and AI assets.

Talk to an expert

Contact us