- cross-posted to:
- support
our June 2023 financial update.
obligatory preface: we’re 100%-user funded and everything you donate to us specifically goes to the website, or any outside labor we pay to do something for us.
because of the unique circumstances of this month i won’t report an expected yearly expense like i did last time. that’ll probably come next month, when our finances are closer to a useful baseline.
overall expenses this month: $566.98
this is a mighty looking expense, but only $371.98 of it is infrastructure (and even less of that is actually site hosting).
$312.54 for Digital Ocean hosting, which can be further subdivided into
- $241.47 for hosting the site itself
- $48.29 for backups
- $11.87 for site snapshots
- $10.91 for bandwidth overage (1091.10GB @ $0.01/GB)
$15.28 for Hive, an internal chat platform we’re trying to set up (also being hosted on Digital Ocean, but distinct enough to break out from overall DO hosting)
- $13.89 for hosting Hive
- $1.39 for backups
~$39.16 for email functionality, which can be further subdivided into
- $35/mo for Mailgun (handles outbound emails, so approval/denial/notifications emails; also lets us not get marked as spam)
- ~$4.16/mo ($50/yr, already paid in full) for Fastmail (handles all inbound emails)
$5/mo for 1TB of backup storage with BackBlaze (redundant backup system that’s standalone from Digital Ocean)
the remaining $195 of this month’s expenses have gone to paying @UrLogicFails@beehaw.org for his community icons. we do so at a rate of $5 per icon and he’s done 39 of them for us (36 of which are live so far).
overall: we definitely think we’re able to downsize infrastructure costs going forward. we’re already investigating how best to do that (both in terms of host and overall cost)–there’s no ETA for a few reasons, but this month should not be representative of many more subsequent months.
overall contributions this month: $3,870.44
we also have an incredible amount of support, so that really helps things as far as “being able to take time to get everything right”. according to OpenCollective, we currently have approximately:
- 97 monthly contributions, totaling $549.58
- 9 yearly contributions, totaling $254.99
- 149 one-time donations, totaling $3,065.87
between monthly and yearly contributions, this means we are still more-or-less breaking even and sustainable overall with this month’s costs. obviously, we would like to be substantially moreso though, through either lower costs, more donations, or a combination of both.
total end of month balance: $3,591.33
- yes yes, this is already out of date by a bunch. expect it to be like that, i use UTC for our reports lol.
expense runway, assuming no further donations
- assuming expenses like ours this month: we have about 6 months and 10 days of runway
- assuming just expenses like our infrastructure this month: we have 10 and a half months of runway
if you’d like to make the runway longer (and reward us for even having this site up today after yesterday’s complete fiasco), now is a good time to donate :)
Wow, I never thought I’d see this level of transparency! Thanks for sharing all this info!
Same, good to see all the donations!
What’s wrong with a cryptic loading bar?
/s
Glad y’all aren’t in the red. Appreciate the work.
I was so worried this was going to be a “We desperately need financial support” and was pleasantly surprised to find it to be “More financial support would be extremely beneficial to ensure continued success, but things look okay.” Once I know what my month’s finances are, I will be signed up for an annual donation
This is a post that I didn’t know I needed. Haven’t considered donating to Beehaw previously much, but your transparency made me submit a monthly contribution. I encourage everyone to do so, you can set it up very easily with amounts as little as 1$ a month to keep the federated future alive.
Man I need to, I was part of the reddit migration which I’m sure created a bunch of work for the admins here. Yeah, I need to donate
When can I buy Beehaw merch? I want a polo shirt with a tiny Beehaw logo embroidered on the top left.
There is unfortunately no Merch 😓
Maybe later but this is pretty hard to do and we’re spread way too thin to do more at the moment.
I suppose they might be able to have them made themselves locally. Using files or something. Just an idea.
We’ve discussed this in the past, and it’s something we’re open to the idea of, but we’d like for the merch to be sustainable and to provide resources for people that need it, rather than large companies. If someone on this website happens to run a small business making some kind of merchandise and can handle the volume they’d likely see, we’re more than open to working with them, but it’s way down low in terms of priorities.
Love the transparency, I set up my monthy contribution already, glad to pay for this, wouldn’t pay a cent to corporate re**it.
This is real awesome lol! I love the transparency and an just want to say I’m really loving it here! So so glad someone recommended it because Lemmy almost turned me off of this whole federated thing and now I’m on Mastadon AND Beehaw 🤣
It makes it easy to justify signing up for monthly contributions when resources can be seen mapped against cash burn like this. Thanks!
I didn’t know this kind of transparency existed before today. Thank you for everything you do!
Just want to say I appreciate the transparency. Keep up the good work!
Appreciate the transparency. I’d also be interested to see what you guys have done infrastructure-wise to handle all the new traffic. Just increased the size of your server instance?
Initially, yes. Ongoing, no. Lots of various tuning, caching, performance checks, some code changes to Lemmy itself for our usecase, etc.
Interesting - what kind of code changes are required for this specific use case? Sounds like it’s been a lot of work!
@Penguincoder@beehaw.org has done so much work it puts everyone but maybe @alyaza@beehaw.org to shame. I practically do nothing around here compared to those two absolute idols. 💜
Thanks for sharing - interesting to see a breakdown like that. Very much interested to see what next month looks like too, accounting for the Reddit migrations.
In the event that the runway did end up shortening for whatever reason, do you think it’s likely that registrations would be put on hold as a way of capping expansion until more funding could be secured?
Registrations themself don’t factor into the infrastructure cost of Beehaw. What does matter, is number of concurrent users and maximizing the efficiency of the service, to handle the load better.
I would rather move to a lower cost provider than to just stop all registrations due to server load. Helix, Remington and I are working hard to increasing the performance of Lemmy and our backend to handle more users. We don’t want to or expect to keep throwing money at this problem.
Autoscaling also helps a bunch with this, so you don’t end up paying for beefier instances during times when you don’t really need them. Naturally it’ll make cost harder to predict, but at least an upper bound is easy to calculate and with some data you’ll also see what your average cost is
In the event that the runway did end up shortening for whatever reason, do you think it’s likely that registrations would be put on hold as a way of capping expansion until more funding could be secured?
i’ll defer to @Penguincoder@beehaw.org and @Lionir@beehaw.org here but i think it’s more likely we’d just switch to a cheaper host or something (which we’re already probably going to do).[1] most of our issues if that runway gets shorter presumably won’t be with people signing up so much as just general traffic.
Digital Ocean is fine for most of our purposes but it’s on the expensive end long-term and we hit the point of diminishing returns with our last upgrade. we already don’t use most of what we’re paying for, strictly speaking–it really only has some side benefits it shouldn’t in the first place because Lemmy is weird. ↩︎
Please feel free to reach out to us users in case you want more help on the technical side.
I’m a platform engineer but I’m sure there are plenty other IT professional here that would be glad to lend an hand even if just to discuss technical aspect in a short of “bounce back ideas to find a good solution”.
If you or anyone else reading this wants to get involved, join the matrix or discord. They both have operations channels where we openly discuss ongoing issues with the server and changes being made. Offer your input or time and it will not go unnoticed.
I know you didn’t ask but give a look at Contabo as host.
It costs much less because it’s just that, vpc provider, not an accelerator or anything else but if you have the people with the skill set to take care of the ingress side of things, it’s a lot more sensible in terms of expenses.
Hetzner is also nice
Hetzner is incredible!
Thanks for sharing! Alway appreciate the transparency!
I see that there’s a “Support Lemmy” option over there, but is there a way to specifically send a donation to Beehaw, or does it just go to Lemmy in general?
Noting that this “Support Lemmy” option does not send us any money. It’s for the two main developers of Lemmy.
I see that there’s a “Support Lemmy” option over there, but is there a way to specifically send a donation to Beehaw, or does it just go to Lemmy in general?
it’s the post’s submission link here, and can always be found on the front page sidebar
Now I see it, thanks!
Nice to see you guys have some reserves too. It is a little bit of a crazy time knowing what ongoing costs will be so reserves can be really helpful.
Truly appreciate this level of transparency and glad to see the generous contributions and support.
