[kolektiv]

Can I just add a general plea to sites like this one which follow a "free while in beta" approach? It's great, and I love free, but I can't choose free without knowing if it's going to become $10/mo or $10k/mo. I'm sure I could probably have a guess at the ballpark pricing that they'll launch this at, but please try and give an indication.

I simply can't commit the time to roll something in to a product or platform which I may have to roll back out again later when there are alternatives that I can plan/budget/account for. There are a few things lately which I've thought "that could be great" but I haven't adopted or tested fully because I just can't know how their costs will scale as my products do. See Bridge for another example, though they did respond with extra clarity after a few people mentioned it.

[beastmcbeast]

We have committed to always having a free account, and the features you see today will always be available to free accounts.

We are currently thinking along the lines of charging for higher volume accounts.

[kolektiv]

Well, yes... That's semi-reassuring! Now I don't know what you mean by higher volume accounts. I may well be one, but I don't know that yet. It's like saying that Github will always have a free account - yes, maybe so, but it doesn't do what I need, hence paying $100/mo (as a higher volume user!). Are you different?

[cheez]

I'd say that they should charge in beta too. Pricing needs to be tested before you release.