E.g a service tax for servers on all incoming funds. I know it would annoy users but ultimately it keeps the service stable.
Charging fees from incoming payments (i.e. deposits made by advertisers) is very bad idea. Advertisers, not publishers create income stream for the CoinURL and if they feel any inconvenience, it could have negative impact on the revenue.
Currently I am trying to get enough income by forcing publishers, who withdraw funds, to donate some share to the service.
Realistically you should be able to make an easy 100USD a month and just put the site onto a cloud VPS? Saves a lot of hassle.
Right now CoinURL is located on the virtual server with dynamic resources (total 16 CPU cores and 12 GB RAM) for about $20/month. If there is little load on the hosting's server from other customers, CoinURL shows excellent performance. But in some days (absolutely randomly, occurs about 1 time per few weeks) overall load on the server becomes extremely high and hosting's administrator imposes temporarily limits for me (he told that other hosting's customers complain for the poor performance and they have no other choice that limit resources for me, because CoinURL is the most resource-consuming site they host). In this case you see this annoying "max_user_connections" error.
I tried to measure performance on the dedicated XEN VPS with single core 2.4 GHz and 1 GB RAM. Result: very far from enough!
If I would start accepting non-Bitcoin users, I expect growth for tens of times in short time, server resource consumption most likely will rise so dramatically that $10-20k mainframe will be required.