..
So coins, if I had a database that I needed blockchain level protection, I could contract a service node to write my encrypted data to the blockchain and give me access when I needed? Just an example, I know it's probably more complicated and there are more functions, but would that be a realistic application?
Not 100% clear what you are asking.
Let's take a corporate company like an electricity utility.
If they want to run a blockchain so that they could communicate and transact with their supply chain, they may not want their internal users or their supply chains to run full nodes on their own networks.
Many corporate businesses have really congested networks - and in our example - electricity utility businesses are huge targets for cyber attacks. So running many full nodes would potentially add congestion and also create many challenges and problems for business users.
You also have many businesses using remote desktops systems as well as placing limits on who can run applications.
The easy option for infrastructure businesses like this would be to outsource their full nodes (to our Service Nodes for example) and give local users access via SPVs.
SME's have a slightly different dynamic, but need the same service provision model for different reasons. For SMEs, it's about accessing B2B payment tools to avoid bank fees and also have the capability to trade internationally, but they are already busy running their own business, they don't want the headache of having to run their own full nodes.
SME's would be at the lower end of our market pricing (Service Nodes actually set prices themselves, well that's one of our preferred models) but would generate more volume and sales as we would have greater numbers of customers who are more price aware and more likely to shop around for the lowest price provider.
This is essentially a cloud service model, a big growth area. Microsoft has bet the farm on the cloud services provision model.