Household finance platform

Tallyfolk

Private Beta

A Cloudflare-first household-finance platform built around private personal ledgers and a shared household workspace.

01. THE PRODUCT PROBLEM

Household money work does not fit one personal account.

Personal finance tools often assume one person, one ledger, and one reporting need. Real households mix private spending, shared obligations, recurring costs, receipts, debts, goals, and monthly review work.

Tallyfolk was shaped around that split: keep private financial records private, then give the household a shared workspace where collaborative finance work can happen with clear permissions.

02. PRODUCT MODEL

Private ledgers and one shared household workspace.

01

Private personal workspaces for individual finance records.

02

One shared household workspace for coordinated budgets, transactions, transfers, member management, and splits.

03

Financial records covering transactions, transfers, budgets, recurring entries, debts, goals, receipts, and reports.

04

CSV exports and printable month-close packages for review and household administration.

03. WORKSPACES AND FLOWS

The current beta covers the daily and month-close work.

Current product support includes transactions and transfers, budgets, recurring entries, debt tracking, goals, receipt uploads, household splits, reporting, CSV exports, printable month-close packages, notifications, and member management.

04. SECURITY AND AUTHORIZATION

Authorization is part of the product model.

The important boundary is not just login. Tallyfolk needs to distinguish private workspace access from shared household access, then apply those checks to financial records, reports, member actions, exports, notifications, and attachment retrieval.

  • Opaque database-backed sessions and first-party authentication.
  • Server-enforced authorization with workspace membership checks.
  • D1 for relational data and R2 for private file storage.
  • Authenticated attachment access for receipt uploads.
  • Turnstile support and rate-limiting support for abusive traffic controls.
05. CLOUDFLARE ARCHITECTURE

A Cloudflare-first system for data, files, and controls.

The architecture uses Cloudflare Workers for application control paths, D1 for relational finance records, and R2 for private receipt storage. The application keeps attachment access authenticated and routes workspace-level decisions through server-side checks instead of trusting the client.

06. CURRENT BETA STATUS

Private beta, not a public launch claim.

Tallyfolk is in private beta and still requires final production configuration and broader authenticated end-to-end testing before a wider launch.

07. WHAT AXIOM LABS BUILT

The useful proof is product shape plus system discipline.

Product model for personal and shared household finance spaces.
Ledger, transfer, budget, recurring transaction, debt, goal, and receipt workflows.
Reporting surfaces, CSV exports, printable close packages, and notifications.
Cloudflare-first application architecture with D1, R2, and Workers-backed controls.
Related services

Useful if your product combines records, permissions, and recurring workflows.

CTA

Talk through a secure shared-workspace product

Next Case Study

SlitherTime: specialist infrastructure