Same thought, I am absolutely blown away by how much vercel overcharges. I host a similar application on netcup (like hetzner) for 3$ per month, and when it was on HN, it easily handled over 10k requests per hour
Hey, thanks for the info, I didn't know that there is a wait period. The version I posted back then was still very much in its alpha stage, compared to now. I would say it is a major difference, but I also get that HN doesn't want too many product updates posted
It is a budgeting tool that allows you to create budgets and visualize them as interactive Sankey diagrams. You can configure smart "pockets", which can automatically send excess cash or take missing cash from other pockets. It also allows you to invite other users to shared budgets, so you can use it to plan budgets with roommates or your partner. Currently I am thinking about ways to make it into a viable business, but it is still not quite there yet where it needs to be for that.
It's very nice and clean and functional. Budgets are some of the most boring and universal tech ever, and I think your project is very worth continuing. Kudos for having a collaborative (if not fancy and needlessly realtime) feature from the start!
Looks great man! I think we are doing something different conceptually, my app intentionally doesn’t have expense tracking, and is purely about budget planning.
But I like the idea of automatically generating a sankey from your expenses, good job on that!
Hey thanks for the feedback!
The default budget on the home page does not have the add pocket/flow buttons, those are on the pages where you add your budgets are listed. But it totally makes sense to have them there as well, just added them! Thanks for noticing!
The naming is really hard, the where first called "nodes", but that was hard to understand for many. I habe to analyze this again, maybe you are onto something by just naming them income/expense/account/grouping etc.
The idea to take or send a percentage is very interesting, basically a generalization of how it currently works.
I think entities or nodes can be categorized as incoming, outgoing, and internal transfers.
Once you get this right, the natural next step is to take time into account. The current chart is the ideal moneyflow, but from months to months I’ll deviate from it. Taking time into account means that these deviations are saved and analyzed. It also means one can analyze or prospectively test new allocations: given average annual returns on investments, what would my savings look like in the future? How did it evolve over time?
That’s just my thoughts on it
Great to hear this! Gives me a lot of confidence that it is worth continuing to work on this. The AI integration Idea is interesting, could be a good starting help for everyone who is just starting out. Thanks man!
It's weird, sometimes they are slow for me, too. But everything is done with native CSS transitions. Definitely have to look into that again, thanks for the heads up
