Hacker News new | past | comments | ask | show | jobs | submit login

We are working towards adding data replication as a feature in Wallaroo. To make that work, you need to allow for at least 3 servers so that was the bare minimum. We added the 24 cpu limit because we are trying to build a business and allowing someone to load up 3 massive servers and use all the enterprise features for free isn't good business.

We started with "low" numbers because we aren't sure what the right cut off will be and we would rather give people more in the future then realize we gave them too much.

If we decide that 5 servers/40 cpus is the right level then everyone who gets an increase will be happy. If we started at 5/40 and realized that the vast majority of use cases were fine at that level and wanted to lower that number, we'd be screwed and would ruin trust. So, we started with what we thought was a nice low minimum and as we go forward, we'll potentially raise the limits.

It was at least partially informed by a POC we did for one of the major US banks were we met their targets with 5 server and 30 cpus. It was the sort of application that we think is reasonable for us to get paid for (so we can keep building Wallaroo) so that also acted as an upperbound for our early discussions.

In the end, we want people to be able to use Wallaroo and get value out of it. And we want to be able to build a business and keep building this thing that we love. And as I said, we want to be cautious and make sure we are always in the position to give away more rather than having to take things away.

There are features that might eventually become 100% free and open source as we move forward. What we want to avoid is ever having to close the source on a feature.

I hope that answers your question. Sorry, its been a long few weeks polishing up the first release and it's been a very long day today so I'm a little tired and rambly.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: