[Sir_Substance]

Why is it necessary for me to sign up? Is it only for your metrics?

Could this have been designed in a fashion that doesn't require me to roll another bloody account?

Not so interested that I feel like opening one, sorry.

[lastbackend]

Hmm.. Why do you think so? Maybe we can discuss it by e-mail or skype. We need to know what's the reason you thinking so.

[Sir_Substance]

It's really quite simple. I'm on an anti-account binge, and have been for a while.

Primarily, I just hate accounts. I have hundreds of them man. It's absurd. I don't bother trying to log in to most of them any more, if it's not a service I use every day I go directly to recovering the username and password, because I'll never get it in the three or five or 10 tries I'm allowed before the account is locked/they start giving me captchas. Often enough, that system breaks, and then I'm left having to email admins and beg them to help. That's always a fun coin to toss.

So I don't make 'em any more, unless I literally have to. Quite seriously, the only new account I recall opening in the last two years is with the Australian government, because it was mandatory to do my tax return via that system. Maybe there's one or two others, I don't know. e: I remember the other one, it's this one! tada, own goal!

I'm currently locked out of the government system, because their secret question/answer system didn't like my answers. I have to call them during business hours to fix it. I moved to another country recently, so that's going to be cheap and stuff.

Secondarily, I'm starting to critique peoples use of accounts. Lots of people implement a username/password system when they don't need it, because it's easy to do so. As a developer myself, I am taking a stand against lazy development.

Maybe I don't fully grasp your product (I'll be honest, the instant I saw "sign up now" my shutters went down), but it seems like a graphical docker container configuration management tool is less effective as a web app than a desktop app, and doesn't need an account system either way.

For example, if you're using the accounts for saving flow setups, could that not be done with a combination of URL parameters (encoding customer specific data like IP addresses) and page ID's to a key-value database (with the benefit of data de-duplication), thus allowing me to save my work with a simple ctrl-d to bookmark it? As a side benefit, I can share it just by emailing it to people.

Hey, maybe I'm wrong, maybe your system really does need accounts, but I'm still not going to make one. I have to draw the line somewhere if I want this endless account sprawl to end.