edictIn development

Budgeting and expense tracking

An example app for private budgets, expense logs, receipts, recurring costs, and budget alerts.

Example app Built from planned modules. Not a customer. Not a supported app today.

Illustrative rule: alert when a category nears its budget

AgentEdit edict.yaml+10illustrative
1modules:
2+ rules:
3+ category_budget:
4+ sum: expenses.amount
5+ per: month
6+ group_by: category
7+ emits_at: 80_percent
8+ notifications:
9+ triggers:
10+ - on: category_budget.threshold
11+ send: budget_warning

Placeholder values and unfinished syntax. Not a released feature.

What is the Budgeting and expense tracking example app?

A user records what they spend, sorts it into categories, and sets a monthly budget for each. They photograph receipts and attach them to entries. Bills that repeat are added automatically. The app warns the user when a category is close to its limit.

This category is a design target. It is not a claim that Edict already supports a complete budgeting app.

What backend does the Budgeting and expense tracking example need?

  • Private user data.
  • Relational records.
  • Aggregations.
  • Scheduled operations.
  • File storage.
  • Alerts.

How do the planned modules compose in the Budgeting and expense tracking example?

Financial records are sensitive, so ownership matters first. Authentication and the database are designed to keep each person’s records private through a user-owned rule. The relational model links expenses to categories and budgets, and the planned query support covers totals by category and month.

Files is designed to store receipt images, owned by the same user as the expense they belong to. Background jobs are planned to create recurring entries on schedule. Business logic is designed to watch the running total and emit an event when a threshold is reached, so push notifications can send the alert.

What would an illustrative rule look like in the Budgeting and expense tracking example?

The configuration above sums expenses per category each month and raises an event at a chosen share of the budget. The key names and the syntax are placeholders and are not final.

What is example and what is planned in the Budgeting and expense tracking example?

All modules named here are planned and in development. Edict is not a bank connection, and this example does not imply integration with any financial institution. Your app owns the categories, the currency handling, and how you meet the privacy and financial rules of the places where you operate. Edict does not provide financial advice, and it makes no security guarantee at this stage.

See the Database and Files module pages for the planned design, and join the beta waitlist to follow progress.

These share the most modules with this one.

See all example apps

Get an invitation when the beta opens.

Joining gets you email updates while Edict is built, and an invitation to the hosted beta when it opens.

Building now. No launch date yet.