Remote View

2y ago

the UPDATED financials of Beehaw as of June 2023 (and how you can help our website stay up and be more reliable)

Beehaw - Open Collective

hey folks, here's another meta-post. this one isn't specifically in response to the massive surge of users, but the surge is fortuitously timed because i've been intending to give a good idea of what our financial stability is like. as a reminder, we're 100%-user funded. everything you donate to us specifically goes to the website, or any outside labor we pay to do something for us.

thanks to your generous support, we're pretty confident we have passed our current break-even point for this month, at which we wouldn't eventually need to pay out of our own pockets to keep the site running. that point in our estimation is about $26 a month or $312 a year. (please ignore OC's estimated yearly budget--we don't determine it lol)

our expenses are currently:

$18/mo toward our host, Digital Ocean. (yesterday we upgraded from DO's $12 tier to its $18 tier to mitigate traffic issues and lag, and it's really worked out!)
$2/mo for weekly backups
$4/mo for daily snapshots of the website, which would allow us to restore the website in between the weekly backups if need be.

for a total of at least $26/mo in expenses. this may vary from month to month though, so we're baking in a bit of uncertainty with our estimation.

we currently have, for the month of June:

$70/mo in recurring donations (at least for June)
$200 this month in one-time donations

for a total of $270 this month. our total balance now stands at $331.31.

that balance means we now have about a year months of reserves currently, if we received no other donations and have no unexpected expenses.[^1] the recurring donations put us well into the green at this point.

this is good! everything past our break-even point each month is, to be clear, money we can save and put toward scaling up our infrastructure. there is no downside to donating after we've already met our "goal" of basic financial stability. doing so will have pretty straightforward practical implications for you: fewer 500s, 503s, better image support (this takes a lot of space!), and the website generally being run on more than potato hardware.[^2] if you'd like to do so in light of this information, our OpenCollective page is this post's link. thanks folks!

[^{1]: we will have at least one upcoming expense but its size is TBD, and so is how we'll pay for it
[}2]: especially during times like now, where we've likely been getting thousands or tens of thousands of hits an hour

Beehaw Support @beehaw.org

alyaza [they/she] @beehaw.org

2y ago

the hopefully final June 2023 financial update for Beehaw (lol)

opencollective.com /beehaw

Beehaw Support @beehaw.org

Gaywallet (they/it) @beehaw.org

2y ago

Beehaw Yearly Recap

opencollective.com /beehaw

Beehaw Support @beehaw.org

Chris Remington @beehaw.org

3y ago

Please, consider making a financial contribution to Beehaw

opencollective.com /beehaw

12 comments

minor PSA: we splurged a bit thanks to your donations and got slightly better hardware. you've probably noticed a more fluid website that's erroring way less accordingly. enjoy! i'll update this post's numbers tomorrow to give you a reflection of the new break-even. thanks for using the site folks
- It will be interesting to see how many users stick around. It's busy right now but in a month you may be able to backtrack to the previous hardware.
  
  well, in a month we might be dealing with a second wave of users (and i think we won't be short on people who will stick around), but yeah point taken lol. it does help we're also not using a complex set-up, so "scaling up" isn't a big commitment right now
- I would like to know to what extent you are able to scale up the hardware. Is there a theoretical limit in the number of users that can handled?
  
  There is room to scale the VPS immensely. However, we made a small bump to the next tier yesterday and things are working very well now.
  Is there a theoretical limit in the number of users that can handled?
  Maybe...I don't know.

At the risk of sounding like Roy from Ted Lasso.... This is FUCKING REFRESHING. This is how it should be! Thank you so much for the transparency, and for all the work you're doing to implement this instance. I'll definitely be sticking around, and hopefully contributing whatever I can. This is amazing. Please keep it up!

I discovered this whole thing just a few days ago (of course from that reddit post) and I love how this has such strong early-internet vibes! I mean where anymore do you ever read the owner of a site casually go "Yeah, since we are a couple hundred dollars in surplus, I was able to splurge on new hardware so that you'll see loading errors a little less often because the server is no longer powered just by my child being strapped into an oversized hamster wheel"?
- Do you think you could link me to that Reddit post? I'm out of the loop
  
  Here it is
  https://reddit.com/r/apolloapp/comments/13ws4w3/had_a_call_with_reddit_to_discuss_pricing_bad/

I'm new to BeeHaw but its really encouraging to see such transparency and, frankly, competent admin communication. Thanks for sharing this!

Massively appreciate this level of transparency on the instance's finances. To me, that's a promising sign

Scaling up can become quickly cost-prohibitive with large-scale servers. I've noted that the most affordable option with Digital Ocean, at $12/month, offers only a basic droplet with 1 vCPU, 2GB of RAM, and 50GB of SSD storage. When you consider a higher-end configuration with 16GB of RAM, 8 vCPUs, and 320GB of SSD storage at $96/month, it may not seem economical, especially as storage and backup needs increase with server scaling.
As an alternative approach to minimize costs while scaling, consider purchasing used servers from platforms like eBay and setting up a small-scale hosting operation in your garage. While this route does introduce overheads like business internet services and electricity costs, along with regular maintenance such as HDD replacements, it could be more cost-effective in the long run.
For instance, you could acquire a server on eBay for about $300, offering 20 CPU cores, 64GB of RAM, and 8TB of SAS HDD storage. Comparatively, a similar setup on Digital Ocean would cost around $544/month or $6528/year, making the used server a strong competitor against cloud services.
Just some food for thought if you're contemplating scaling in the future.
- Digitalocean is pretty expensive. For example on hetzner.com you can get 8 vCPU for 15 euros per month. OVH should be similar. So thats really affordable if you have hundreds or thousands of users and a couple of donors.
- While I'd be more than happy to purchase and use actual server space for doing this kind of thing, I'm not nearly tech saavy enough to actually run that. I would also worry about bandwidth considerations and other issues. Perhaps there are people willing to contribute to the cause to find affordable ways to run a website like this, but being accessible by multiple people to do things like power cycle the server, not being concerned about our personal IPs being attacked, and having access to support I think is worth the extra cost.
  There is a point at which something akin to this needs to be done for financial reasons, but I think we're pretty far from that being a reality and while it relies on slightly more donations from our lovely userbase, even at $96/mo that's not that much money to collect when we have the thousands of users that would require that kind of hardware.
  
  I appreciate your thoughtful response to my comment. There are indeed several strategies that can be employed to decrease bandwidth and storage costs. Leveraging a Content Delivery Network, such as the free service provided by Cloudflare, can help mitigate these costs by caching your webpages and images. As for the cost of internet service, it greatly varies based on your location. If you're located closer to the internet backbone, the likelihood of finding a more reasonably priced business internet plan increases.
  While it may seem premature at this stage, I firmly believe in the success of this website, even in the face of numerous failures in this space.
  Edited to add -
  You've correctly highlighted the potential threat of attacks on your server. Cloudflare is known for its prowess in mitigating substantial distributed denial-of-service (DDoS) attacks and could be an excellent security asset in this context.
  Regarding the value of professional support, I acknowledge that the cost can often be justified. My suggestions are merely alternatives, providing you with additional options should you require them.
- I did that in my garage a few years back to tinker around with linux servers. Just don't make the same mistake I did and buy the cheapest SSD on eBay. My friend group still hasn't forgiven me for letting our minecraft server get corrupted lol.
  
  Absolutely, and at a minimum, I'd suggest implementing the 3-2-1 backup strategy, widely regarded as the "gold standard" for maintaining data integrity. This involves keeping a total of three backups: two stored locally, but on different devices, and one off-site backup (ideally kept in a secure location such as a bank safe deposit box, with hard drives rotated every two weeks).
- What about just autoscaling on AWS
  
  Auto-scaling comes with its trade-offs. It can lull users into a false sense of security, leading them to believe that all configurations will seamlessly scale up. However, even with managed databases, there are inherent limitations and the need for architectural changes to support a larger-scale infrastructure. While auto-scaling provides a robust system for managing overhead and mitigating the efforts involved in scaling, there are potential risks and hidden costs.
  One significant risk is the misjudgment of traffic or the inadvertent scaling up caused by a software bug. This could escalate the demand for more computing servers indefinitely, limited only by your budget. In contrast, self-hosting, despite its higher administrative complexity, offers more opportunities to cut costs associated with cloud usage.
  As with most things, different approaches have their pros and cons. I am simply offering alternative ideas for those interested in exploring other options.
  
  I'm not sure they want to depend on Amazon services?

Thanks for the quick approval!
Really hope this becomes the new reddit!

Started a small monthly contribution, hopefully will help scale to what will likely be a lot of increased usage

It's going to be entertaining seeing the new numbers after you update this post.

That's... surprisingly low! Nice! Now i find myself wondering about the financials of something like the biggest Mastodon instances...

I’m now contributing a little bit. :)

super happy I set up a recurring donation last week - I had a feeling you guys were going to get hammered at some point!
I'm coming in at about 78$ a month for mydroplet; a s-4vcpu-8gb and a singular 250gb volume, including taxes. I still think paying someone to host it remotely is a better deal - but I also live on an island and we lose power multiple times a year and I don't want my inability to power things impact my users.

Is it possible to donate Cryptocurrency? I'd love to give XMR (Monero) so I don't have to reveal any details about myself, etc.
- Is it possible to donate Cryptocurrency?
  at least currently we're tethered to OpenCollective (and not really in a position to extend ourselves across even more stuff to maintain) so if they don't accept it then no, that's just a limitation we'll have to live with. that said, i believe OpenCollective allows for anonymous donation--we have many Guest contributions--so that may be suitable for your purposes if you can do crypto to fiat conversion

That's great to hear! I'm still trying to wrap my head around the federation concept itself so if you don't mind, I have a question for you. In the event the site did go under (which it seems like is not the case, yay!) what happens to our account? Will we have to create a new account on another instance? If so, will we be able to use the same username?
- I like the email analogy.
  When you want to use email, you sign up for an account. It doesn't matter if you go to gmail or hotmail or something else, you can still communicate with anyone else that has email.
  Now if your username for email is fred@hotmail.com and then that server went down, you would no longer have access to your account, people couldn't contact you. If you then decided to set up a gmail account, you would only be able to get the account fred@gmail.com if no one else had taken it. The name "fred" is not reserved for you across all email providers.
  Federated platforms like Lemmy (which Beehaw is part of) work the same way. Your account is not @CobolSailor but @CobolSailor@beehaw.org. If Beehaw went under and no longer existed, you can go and sign up on another server, e.g. lemmy.ml. But you could only use @CobolSailor@lemmy.ml if it was not taken by someone else, it's not reserved for you across all servers - and can't be, because there is no central server keeping track.
  Does that explain it?
  
  The email analogy just made the whole federation click in my brain. Thank you for the well explained response!
  
  @Mersampa @CobolSailor
  As someone who has like 1 hours worth of experience here, that cleared a lot up for me about how this works actually. Cheers!
- In the event the site did go under (which it seems like is not the case, yay!) what happens to our account? Will we have to create a new account on another instance?
  yes, although luckily doing so is... pretty trivial compared to some other circumstances. i believe most instances also have open registration, so it'd be less rigorous than our registration.
  If so, will we be able to use the same username?
  provided it wasn't taken on that other instance, yes (which for most people shouldn't be the case, since lemmy is very small relative to other fediverse alternatives and its instances even smaller)
  
  Hopefully it doesn't ever come to it, but good to know I can create an account with the same name on another instance if I had to. Appreciate the response!

12 comments

Thanks for the quick approval!