Comaney 💸

Budgeting that actually fits into your life.
Check it out now!

Try it without signing up

The demo account is a public sandbox. Do not enter personal, sensitive, or illegal data. It is reset automatically once a week.

Custom themes, configurable in your account settings. Download exemplary backdrop files.

Full documentation is available at https://comaney.app/docs.

---

What is Comaney?

Comaney is a personal budgeting app available as a hosted service at comaney.app or self-hosted on your own server.

Track your spending

Log expenses with a title, amount, date, and category. Tag them however you like and search or filter across your whole history in seconds. Export everything to CSV at any time.

Stay on top of recurring costs

Set up scheduled expenses (subscriptions, rent, insurance) once and Comaney generates them automatically. Get notified when a payment is coming up or overdue.

See the big picture

The modular dashboard lets you build your own overview from scratch: spend-by-category charts, running totals, custom lists, and more. Each card is fully configurable and can link through to the matching filtered expense list.

Add expenses fast

AI express entry lets you jot down a quick note like "strawberries for date night with Ann, 4 EUR" and Comaney turns it into a properly categorised and tagged expense. Snap a photo of a receipt and it splits it into individual line items automatically.

Know what something really cost

How much did the bathroom renovation cost in the end? Put every expense that belongs to it (tiles, plumber, paint, the rented tile cutter) into a project and Comaney adds it all up for you, no matter how many months it took. Projects don't need anyone else: they're a place to collect everything that belongs to one undertaking, alongside your normal monthly budget. See Projects below.

Let AI assistants do the work

Comaney runs an MCP (Model Context Protocol) server, so AI assistants can read and write your account directly. Each assistant gets its own agent key. See User manual: AI Assistants (MCP).

Connect your own tools

A REST API lets scripts and other apps read and write your data, for example to import bank transactions. See User manual: REST API Access.

---

Projects: group and organize your expenses

A project is an expense container tied to a specific goal, event, or ongoing situation. Projects work fine on their own as a way to keep expenses organized, and they scale up to full multi-person shared budgets when you need them.

Examples:

• Repairing a motorcycle (just you, solo tracking)
• Beach trip 2025 with friends
• Tracking monthly flat expenses with housemates

Solo projects

A solo project is just you. It is a clean way to bucket all expenses related to a specific goal without mixing them into your main expense list. The debt diagram and settlement tools are hidden because there is no one else to settle with.

Multi-member projects

Add other people to a project and it becomes a shared budget. A project can include any mix of:

• Real users: other Comaney accounts, invited by email. They see the project, approve expenses created for them, and confirm settlements.
• Offline members: people who do not use Comaney. You manage their records yourself. You can link their real account to an offline entry later so the full history carries over.

Logging shared expenses in a project

When creating an expense, set the assignment to Project and pick the project. For multi-member projects you then set:

• Who paid upfront: you, or any other member.
• Who participated: all members, or a custom selection.
• How the cost is split: drag sliders to set percentages, or use Equal shares for an even split.

If a connected user is set as the one who paid, the expense is created in their account and they must approve it before it counts toward the balance.

Debt diagrams and balances

The project page shows two debt views based on all approved shared expenses:

• Raw debts: an arrow from each person who owes money to the person they owe, with the exact amount.
• Simplified: the minimum number of payments needed to settle everything. Comaney chains debts together where possible. If Alex owes Bailey 10 and Bailey owes Casey 10, the simplified view shows a single arrow: Alex pays Casey 10 directly.

The Your balance section gives you a plain-language summary of who you owe and who owes you.

Settling up

Use the Pay someone back form on the project page to record a payment. The amount is pre-filled with what you owe, but you can enter any value.

• For a connected user: they receive an email and must confirm receipt. The balance only clears once they confirm.
• For an offline member: the project admin confirms receipt on their behalf.

The project admin can also settle the entire project at once: Comaney calculates the simplified debt breakdown and creates one settlement per debtor-creditor pair in a single action, then notifies everyone by email.

Admin controls

Every project has one admin. Only the admin can invite and remove members, trigger a group-wide settlement, archive or delete the project, and transfer admin rights.

Archiving and removing members

Archiving freezes the project. No new expenses or settlements can be created, but in-flight settlements can still be confirmed. Archived projects remain accessible for review but no longer appear in expense form dropdowns.

Removing a real user keeps their name as a read-only offline entry so past expenses still reference them correctly.

Removing an offline member moves their shared expense history to Achim Archive rather than deleting it, keeping all balances intact.

---

Contacts: one-on-one sharing without a project

If you want to split costs with a single person, you do not need a project. The Contacts feature gives you the same split-pay mechanics directly between two people.

Adding a contact

Click Contacts in the navigation.

• Offline contact: someone without a Comaney account. Enter a name; only you track the balance and log expenses for them.
• Connected user: send an email invitation. Once they accept, both of you can see the shared balance and log expenses against each other.

You can link an offline contact to their real Comaney account later so the full history carries over.

Sharing an expense

Create a new expense and set the assignment to Contact. Choose the contact, set who paid and the split, then save.

Settling up

From the Contact Expenses page, use the Pay someone back form. For a connected user, they must confirm receipt before the balance clears. For an offline contact, it is confirmed automatically.

Approving expenses created for you

If a connected contact logs an expense with you as the one who paid upfront, it appears in the "Did you pay for this?" section on Contact Expenses. Approve it to move it into your regular expense list; reject it to delete it entirely.

---

Achim Archive

When you remove an offline member from a project or your contacts, Comaney does not delete their shared expense history. It moves that history to a placeholder called Achim Archive so all balances stay correct.

Multiple removed offline members all fold into the same archive. You can permanently delete the archived expenses at any time; Comaney shows you exactly what will change before asking you to confirm. This cannot be undone.

---

Self-hosting

Comaney runs as a Docker container backed by MariaDB.

Minimal docker-compose.yml

services:
  web:
    image: leonetienne/comaney:latest
    restart: unless-stopped
    ports:
      - "80:8000"
    depends_on:
      - mariadb
    environment:
      # Generate: python -c "from django.core.management.utils import get_random_secret_key; print(get_random_secret_key())"
      DJANGO_SECRET_KEY: "change-me"
      DB_HOST: mariadb
      DB_PORT: 3306
      DB_NAME: comaney
      DB_USER: comaney
      DB_PASSWORD: "change-me"
      SITE_URL: "http://localhost:80"
      ALLOWED_HOSTS: "localhost"
      CSRF_TRUSTED_ORIGINS: "http://localhost"
      ENABLE_REGISTRATION: "TRUE"   # disable after creating your account
      DISABLE_EMAILING: "TRUE"      # set up SMTP for full functionality
      GUNICORN_WORKERS: 1
      # Optional: AI features. AI_PROVIDER picks the service, its settings start with
      # AI_PROVIDER_<NAME>_ (see Admin Manual: AI Providers). Example, a self-hosted model:
      # AI_PROVIDER: local
      # AI_PROVIDER_LOCAL_BASE_URL: "http://host.docker.internal:11434/v1"
      # AI_PROVIDER_LOCAL_MODEL: "qwen3.8:27b"
      # AI_TRIAL_USAGE_LIMIT: 10      # per user and month, in US cents; 0 = no limit
    volumes:
      # Required: all uploaded images (avatars, backgrounds, project pictures) live in /app/data
      - ./comaney/data:/app/data

  mariadb:
    image: mariadb:lts
    restart: unless-stopped
    environment:
      MARIADB_DATABASE: comaney
      MARIADB_USER: comaney
      MARIADB_PASSWORD: "change-me"
      MARIADB_ROOT_PASSWORD: "change-root-too"
    volumes:
      - ./comaney/mariadb:/var/lib/mysql

All options and production setup: Admin Manual: Deployment.

Important: the /app/data mount is required. Comaney stores every uploaded image (avatars, backgrounds, project pictures) under /app/data inside the container; without a persistent mount there, they are lost whenever the container is recreated, and the app shows a configuration error page instead of starting normally. Point the left side at any host directory you back up.

First-run steps

1. docker compose up -d
2. Register your account via the web UI at http://localhost/register/, or create one from the command line:

   docker exec -it comaney-web-1 python manage.py create_user you@example.com
   

3. Set ENABLE_REGISTRATION: "FALSE" and restart.

To change a user's password at any time:

docker exec -it comaney-web-1 python manage.py set_user_password you@example.com

Required cron jobs

# Every 5 minutes: notifications, recurring expense generation, auto-settle, end-of-month allowance handling
*/5 * * * * user docker compose -f /path/to/docker-compose.yml exec -T web python manage.py run_cron

# Monthly: reset AI trial budgets
0 0 1 * * user docker compose -f /path/to/docker-compose.yml exec -T web python manage.py reset_trial_budgets

Key environment variables

Full reference: Admin Manual: Environment Variables

---

For developers

Building front-end assets

./build/build-assets.sh

Runs npm install && npm run build inside a node:25.9.0-slim linux/amd64 container. Never run npm directly on the host; see Dev Manual: Building Assets.

Building the documentation

./docs/build/build-docs.sh

Builds the mkdocs site to docs/build/site/, then served by Django at /docs/.

Running tests

# Stack must be running: docker compose up
# Mailpit at :8030, app at :8080
pip install -r requirements-test.txt
pytest ./tests/ -vsx

See Dev Manual: Testing for full details.

Local AI model

The dev stack can run against a self-hosted model on your machine (AI_PROVIDER=local), with or without authentication. On a Mac the model server runs natively for GPU access; plain docker compose up -d is unchanged. See Dev Manual: Local AI in the Dev Stack.

Building the Docker image

docker buildx build \
  --platform linux/amd64 \
  -f Deployment/Dockerfile \
  -t leonetienne/comaney:<version> \
  --build-arg APP_VERSION=<version> \
  --push \
  .