You are essentially trying to ensure you get some kind of a commercial monopoly on your software when sold as a service.
The best license for this use case is the AGPL IMHO. It is not exactly what you are looking for, but no free and open source license would prohibit commercial licensing and offering services.
The AGPL does not restrict commercial usage and does not restrict creating and selling software as a service, but it provides a strong incentive for commercial free riders to share back in this context: "performing" the software over a public network essentially triggers the AGPL copyleft clause.
A good example of its usage would be MongoDB. In their case, they go one step further by providing drivers under the Apache license, and the back-end DB under AGPL, therefore making it easy to integrate in commercial and floss software with limited obligations.
In their context, unmodified usage typically does not trigger the AGPL copyleft. Modified usage would. Offering MongoDB as a service commercially using the unmodified version would be fine without much restrictions. Modifying it would require the service provider to redistribute its changes.
If I were in your context with your parameters, AGPL would be my license of choice. (I am not you and I may not use AGPL, but this is not relevant here ;) )
As a side note, I consider that the CC-NC family of licenses are a poor choice for software in general. You would be better off using a plain commercial license with "visible" sources. The CC licenses were designed for content and not for software.