You don't need to be a programmer to think about building a cryptocurrency - but you do want to be mathmatically inclined. Or prepare to be burned. Specifically within the field of cryptography.
One of the "best" open source tools available is likely to be "decred". Being built by most of the original bitcoin team when they left due to unreconcilable issues with directions the project was taking. I've not looked into that too heavily, yet, and AFAIK that has problems minimally in as much as it lacks widespread adoption.
At a casual glance, that "cryptonote" doesn't allow you to create a whole new cryptocurrency, as much as re-use an existing one and give it a different name. I predict problems through that alone, and would hold concern for ease of abusing the identifier "used for network packages in order not to mix two different cryptocoin networks" in order to specifically mix two different networks, even if the aim is only to cripple it. It also has some concerning claims to it's features, like a blockchain which resists analysis - which leads to questions about how the blockchain ledger is authenticated and processed and their model of continually increasing entropy would surely make it so processing this ledger after the coin has been used for fifty previous transactions to take more electrical energy to do so than the coin itself was worth(or at least, from my interpretation).
It does seem to address a few problems with bitcoin. I'm to understand it's yet to reach "feature parity" with bitcoin.
4. expansion of the scratchpad would require an increase in iterations, which in turn implies an overall time increase. "Heavy" calls in a trust-less p2p network may lead to serious vulnerabilities, because nodes are obliged to check every new block's proof-of-work. If a node spends a considerable amount of time on each hash evaluation, it can be easily DDoSed by a flood of fake objects with arbitrary work data (nonce values).
Is something that would fill me with full confidence in deploying it.
But lets say it's good, and it's deployed... And users start generating these "asgardcoin". Then what? How do you propose to convert that into goods, serivces, or other currencies... Who would accept it as payment? why?
I don't see why it should require two servers, either. But if you hit up scaleway(sub company of OVH) you can get some cheap VPS or ARM-powered "dedicated" cloud for "cheap" to test it.