How can an open-source database maintainer ask for technical feedback without turning Stack Overflow into promotion?

I maintain a GPLv3 open-source SQL database project. I started it because some customer workloads have become difficult to serve with conventional MySQL/PostgreSQL deployments. The affected workloads combine large datasets with search, filtering, permission checks, sorting, pagination, exact counts, and analytical queries over continuously changing data.
In selected real workloads, we have reduced query times substantially. However, I understand that repeatedly mentioning my own project in answers could be considered self-promotion, especially because I may eventually provide paid consulting or maintenance services around it.
I would like to ask the community how to handle this responsibly.
Would a separate, clearly disclosed question asking experienced developers about production adoption requirements be appropriate anywhere in the Stack Exchange network? The questions I would like to ask are about:

• which capabilities are non-negotiable before evaluating a new SQL database;
• what evidence developers would trust, such as reproducible benchmarks, independent testing, production references, compatibility suites, or support commitments;
• whether a partial migration for search, filtered lists, dashboards, or analytical reads is a realistic first step;
• what backup, rollback, durability, observability, security, and operational requirements would have to be met;
• and what kind of commercial support would make a GPLv3 database viable for a business-critical workload.

I would disclose my affiliation clearly, avoid asking for votes or GitHub stars, and avoid linking to the project unless it is directly relevant to a response. The purpose would be to learn about adoption barriers, not to promote the database through unrelated technical questions.
Would this be considered on-topic for Meta Stack Overflow, or should this kind of discussion remain outside the Stack Exchange network? If it is not appropriate, what would be the least disruptive way for an open-source maintainer to request this kind of feedback?
For transparency: I am the maintainer of the project and could benefit commercially from its adoption. I am specifically trying to avoid using Stack Overflow as an undisclosed marketing channel.