Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

financial report #27

Open
andrewharvey opened this issue Jan 6, 2020 · 3 comments
Open

financial report #27

andrewharvey opened this issue Jan 6, 2020 · 3 comments

Comments

@andrewharvey
Copy link

I see there is now some fundraising happening https://opencollective.com/openaddresses.

Is there a financial report or any further details of the expenses for OpenAddresses?

@iandees
Copy link
Member

iandees commented Jan 7, 2020

Now that money is flowing through Open Collective there will be. I can build some reports in the near future, but from memory:

Income

We received a donation from Mapbox a couple years ago.

Expense

  • Expenses are almost entirely a monthly AWS bill of ~$250. There have been a few months where single users have used an abnormal amount of bandwidth, pushing bills up to ~$2,000 a couple times.
  • To defend against these users, we've been using BunnyCDN as a CDN in front of the primary S3 bucket. That costs ~$20/month.
  • We paid a contractor a total of < $500 to help with some data prospecting for a couple months.
  • I pay $12/mo to Google for email from my own credit card.

@andrewharvey
Copy link
Author

Thanks. Any idea on the breakdown of compute, storage and bandwidth costs? I know you recently looked into reducing storage costs but I think there's still room for optimising compute and storage usage more to reduce these costs and just trying to understand if it's worth trying to pursue that further or not.

@iandees
Copy link
Member

iandees commented Jan 7, 2020

Here's a breakdown per month last year for the AWS bill:

image

The vast majority is S3. Within S3, there's about $90/mo of storage and the rest is data transfer out of S3.

image

You can see that non-S3 usage is fairly slim. We have an RDS database and an instance that's on 24/7 along with the instances that run to do periodic work. We removed a bunch of stuff that was sitting around doing nothing earlier last year, too, to save money:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants