Am I supposed to ditch docker compose?

Hello, I read some comments that I shouldn't use docker compose in production. I know that's true for most cases, but it feels like my case is different. Should I be doing something else?

Our company keeps all of its enterprise data in portable and has a client portal for most interactions.

We have one app we call the "picker" app. Picker syncs data from air table nightly. Customers pick components using the Picker and then the Picker constructs a payload and sends it back to airtable for processing.

Picker is a monolithic web app running Django, postgres, next, and nginx via socker compose. Each of our customers gets a single-tenant VPS installation of the Picker.

It's stateless and we can destroy and create the Picker instances at will. There is no need for any data persistence in the Picker so upgrades are easy. We don't even have migrations, because we don't need to keep the data so we just destroy and recreate.

To me this seems elegant. Why would we need to split up the monolith or to use a managed db? I'm kind of new to the infra side of things, so any confirmation or advice here is most welcome!