Thanks @goatpig for the useful information.

I need to digest all of it, as I'm very new in the bitcoin world.
I never thought about the seed being tied to my server. I thought a backup command was available so I can copy/backup the wallets to a safe place.
Am I to understand that if I back up a wallet on machine A, and then restore it on machine B with Armory it could not be done? Again sorry for the dumb questions...
My model is quite simple as I already described. I want to be able to manage multiple wallets/account for our emploies on a headless server (I hope the terminology is correct).
This server will be protected and will have ports 8333 opened for the full node management i.e. bitcoind (and might also 8332 main/18332 tesntnet - for RPC internally).
The wallets files will be hold on the different server (or on the same server).
All the management will be done via a web-service (in our intranet only) talking to the bitcoind via RPC. e.g. opening new wallets; query of balance; send/receive funds; etc... I will be responsible for a web GUI talking to that web-service (talking to whatever full node via RPC).
What I was after is something like ethereum
geth, which acts like a full-node, but lets me easily create and manage accounts (wallets) via RPC.
I toght Armory will let me do that bridge to the bitcoind, but the wallet managements will be done in Armory instead of bitcoind Wallets.