>"the largest market" always reminds me of "Bin Ladens right hand"

People need promotion.

>Personally, I'd rather see a more aggressive AGPL where REST calls are considered linking and trigger virality

That's why I never understood the point of SSPL. Is this exactly what AGPLv3 is supposed to be for?

IANAL

I believe AGPL expands the definition of distribution not of linking. So if GCC was AGPL and I made a web page where you could upload source code and then download the binary, that would count as "distributing" GCC and thus I would have to make the changes I made available (because privately made change to GPL code do not have to be shared if the binaries aren't shared).

I thought Grafana was doing great with its managed offerings. Personally I'd prefer you consider BSL before SSPL since it's usually clearer to most people.

at grafana labs, we are still pretty torn on what our go forward licensing regime should be.

bsl is interesting, but license proliferation and familiarity is a big factor to consider.

now that both elastic and mongo are both using sspl, it is more appealing. i think tsl from timescale is also a great and well thought out license.

Interesting. I got the impression from the recent announcement that Grafana Labs had something of a revenue sharing model with the new AWS managed offering of Grafana. Given that, I wouldn't think the SSPL restrictions would be as important.

we do indeed have a partnership with aws around grafana. but the cloud landscape goes beyond aws, and the grafana labs landscape goes beyond grafana itself.

it's definitely a nuanced discussion internally.

I like Grafana and I wish you the best. Source-available to me is basically FOSS unless I want a free ride off your hard work.

The biggest difference is that the post doesn't come with the upvoting rings. So unfortunately OP won't ever find his product featured here

It's theoretically the same idea at the node level instead of the application level except that the WireGuard curve25519 keys now cannot be verified since they are published by a 3rd party that you have zero control on. This 3rd party can simply connect to your machines anytime by injecting its public keys into your nodes and have complete access into your private network. That's the power of owing your own CA as opposed to letting others injecting peer public keys as if there is nothing to verify.

Wow. What is this tool used to make these animations?

That's what happens when you don't use a container orchestrator.

Perhaps the SS Kubernetes would’ve done a better job with these containers.

Did anybody make a test to compare CRI-O vs Docker especially when it comes to overall node memory usage for let's say 30-50 containers per node? I guess CRI-O would save a lot of memory but I don't have numbers.

I wonder if BSL becomes the new standard for open source commercial products. It's a good trade-off between freedom and real world business pressure.

Doubt it. Lots of aversion to the license given its limited use and some ambiguous terms/education around the various windows.

I think it can be, I know a few other potentially successful examples like CockroachDB and ZeroTier. The BSL license makes the entire project basically FOSS for you and me, but not for the big sharks. Which I guess is much better for the world compared to open-core and of course proprietary SaaS.

Customer support teams would, easily, to manage shared inboxes. Competition includes Salesforce Desk ($75/mo), HelpScout ($35/mo), Zendesk ($89), and so on.

And if Front's shooting for the broader business email market, well, you have Superhuman ($30/mo) at least closer to that price range.

Lets say you have an engineering employee with a base salary of 150k. His total cost to the company when you factor supporting roles is perhaps 300k. Assume this person needs to generate 2x that in value for the company, so lets say 600k a year. So that's 0.01% of the job he needs to do. If the tool is even somewhat useful that seems like a very fair price.

I am not sure how an engineering employee with a base salary of 150k would eventually cost 300k and why a customer should pay for that engineer to make 2x his pay for the investors gluing a couple of 3rd party APIs and making a dashboard.

Comments like these are a great reminder of how disconnected HN comment section can be from reality. That pricing is nothing.

At that price, if it helps close 1 incremental sale a month per seat it pays for itself.