Regarding pricing, you can find it here: https://www.firebase.com/pricing.html
Pricing is difficult and we're trying to get it right. Your feedback would be great.
If I were to consider using this for something important, my first order of business would be to establish how I could ensure I could remove my dependency on you in the case of problems. The more perceived effort that would require, the less chance I'd go ahead.
Nothing specific to you here - that's how I'd approach building a service around running on e.g. AWS too, or making use of any proprietary API.
Also, what happens if you exceed the 1000 concurrent user limit? For example, your site is momentarily popular and gets 1500 people trying it out for a few hours then goes back down under 1000. Is there burst pricing? Do connections get dropped? Is there a grace period, like the way 95th percentile bandwidth billing works?
It seems like the type of thing that'd do great with the option of a self-hosted server, and it also seems like the type of thing that'll see open source clones of pretty quickly, though. But I'd actually be vastly more comfortable paying Firebase to host my apps if I knew there was an open source fallback for their server component.