Most people spread their money over several banks: a salary account at one, a card at another, Revolut for travel. Each bank's app shows only its own slice. ebby reads them all, sorts every payment into a category, and plans your month around the day you actually get paid.

It runs on your own server, so your bank data stays with you. Friends and family can share one install, and each person sees only their own money.

ebby syncs on its own every six hours. That's about four times a day, roughly what banks allow an app to fetch while you're away. When you open the app it syncs again, at most every fifteen minutes. You can also press sync yourself.

Bank approvals expire after a while. When one does, ebby shows which bank needs reconnecting, so you can approve it again.

ebby reads keywords in the bank's description, Revolut's own patterns, the payee's name and, for card payments, the shop type (its merchant category code). If none of these settles it, the payment goes to Other and waits for you.

Some money isn't spending: income, transfers between your own accounts, investments and card repayments. ebby keeps these out of your totals. A debit-card payment that a bank reports twice is matched and counted once.

To move a payment, pick its new category. You can move just that one payment, or every payment to the same payee, past and future. ebby re-sorts your history right away, so last month's totals change too.

The Sorter, in the Assistant tab, collects payees left in Other over the last 90 days, biggest first. You can clear them in a few taps. With the assistant switched on, each one comes with a guess and the reason for it.

Pick a day, week, pay month or year. ebby shows the total, a chart by day, and each category against your usual: the middle value of your earlier periods. While a period is still running, it's compared with the same number of days of earlier periods, so the middle of the month never looks falsely calm.

Up to three highlights point out what stands out. That might be a category that jumped, one big payment, an expensive weekday, or a run of days with no spending.

Payments to the same business are grouped into a service, so card rows with slightly different descriptions read as one name. A service charged in at least three of the last six months is treated as a subscription. ebby shows its monthly and yearly cost and when the next charge is due, and flags the ones whose price varies or that seem to have stopped.

ebby sees cash leave the ATM but not where it went. You can tell the assistant what you spent it on, and it's logged in the right category without being counted twice.

Set your payday to the 1st for calendar months, to any day from the 2nd to the 28th, or to the last working day. If payday falls on a weekend, the month starts on the Friday before, because that's when the money usually lands. After your first sync, ebby suggests a payday from your deposits.

ebby suggests budgets from six months of your real spending. When income runs short, it trims the categories you can most easily cut first. On auto, the budgets follow your income and fixed costs. On custom, they keep the numbers you typed. Greek extra pay, such as the Easter, summer and Christmas bonuses, can be counted in the months it arrives.

The Today card shows what you've spent today, your daily average, and where the month is heading. Each category gets a pace: fine, ahead or over, with a plain-words line about the habit behind it. The year view puts every month side by side.

Say what you're saving for and by when. ebby works out how much that needs each week or month, and suggests cuts based on your last three months. Until you have savings set aside, it suggests a safety net first.

Commitments are costs you've promised in advance, kept apart from everyday spending. A commitment can be a monthly limit on certain payees, or a cost that comes every 3, 6 or 12 months. For those, ebby sets aside a monthly share, so the insurance bill doesn't wreck the month it arrives in.

Weekly habit rules come in four kinds: fewer visits, spend less, no-spend days, and wait before a big buy. Each one keeps a streak and shows the money saved against how you spent before.

Around them sit a few small tools: pay yourself first, no-spend days, yearly costs set aside each month, and the 48-hour wishlist. Add something you want, and two days later ebby asks if you still want it. You answer bought, skipped, or "make it a goal".

Ask in plain words: "how much did we spend on delivery since payday?" or "what changed this month?" The assistant looks up your payments, totals and plan to answer. When it suggests a change, like moving a payment, setting a budget or adding a goal, the change waits for you to tap Do it.

People who use the owner's key get a monthly allowance, which the owner sets for each person. People with their own key, and admins, have no limit.

The install owner invites people by email from Settings → People. They sign in with Google, set up their own Enable Banking application, and connect their own banks. The owner can turn anyone off at any time, and that signs them out at once.

Each person sees only their own accounts, payments, plan and goals, and that includes the owner. The separation isn't a filter in the app's code: the database enforces it on every row, so a mistake in a screen can't show one person another's data.

Bank and AI keys are encrypted before they're stored. Your bank data never leaves your server, except when you use the assistant: then the parts of your spending it needs to answer are sent to Anthropic.

A spending app for a household doesn't need queues, caches or a fleet of services, and every extra piece is one more thing to keep running. The few hard problems, like privacy between people, staying in sync across copies of the server, and numbers that never drift, are solved inside Postgres and the server. The rest of this section explains how.