Community accounting with real operational auditability

Run users, approvals, reports, and traceability on top of a REST-first platform that already works today.

Abhackus already covers secure login, role-based access, approval/rejection accounting flows, exportable reports, and admin operations through web, CLI, and TUI. The web layer is still being consolidated, but the backend and operational base are already in place.

Stable today
In consolidation
Next stage

Stable today

REST API, auth, audit trail, reports, and core operations.

In consolidation

Operational web UI, onboarding, and UX consistency.

Next stage

Basic mode, end-to-end demo, and legacy cleanup.

Active architecture

Modules that support the current production direction and REST-first operation model.

10-minute quickstart

Short path to boot a test environment, validate login, and walk through the minimum accounting flow.

  1. Step 1

    Clone the repository and define `DATABASE_URL`, `ABHACKUS_JWT_SECRET`, and `ABHACKUS_METRICS_TOKEN`.

  2. Step 2

    Start PostgreSQL and migrate: `make db-up && make migrate`.

  3. Step 3

    Run the REST API, validate `/api/health`, and test login from the web UI.

  4. Step 4

    Execute the critical `auth_accounting_reporting_flow_with_ephemeral_db` flow before merge or release.

Operational trust signals

Controls and evidence that reduce operational risk and improve auditability.

  • Revocable JWT sessions and rate limits on login, recovery, and reset flows
  • Accounting audit trail with reason and UTC timestamp for approvals and rejections
  • Role restrictions on sensitive endpoints plus self-approval blocking
  • Tests, coverage, smoke checks, and operational evidence as release gates

Core capabilities

  • JWT authentication with revocable sessions, recovery, reset, and password change
  • superadmin/admin/participant roles enforced per endpoint
  • Configurable membership: member, student, unemployed, friend, paused, retired
  • CLP accounting with admin approval for dues and contributions
  • Members can submit quota payments directly (pending until approved)
  • Telegram bot: /status /deuda /cuota /cuotas /miembros /banco /userinfo /user
  • Approval and rejection audit trail with actor, reason, and UTC timestamp
  • Personal and club reports in HTML, PDF, and monthly ODS export
  • Self-service profile: users manage their Telegram and password
  • Entry attachments, persistent accessibility preferences, and project settings

Executive roadmap

PHASE 01

Close web/auth and onboarding

Finish the active web/auth slice, reduce login friction, and provide a more gradual onboarding flow.

PHASE 02

Make the web the primary interface

Bring dashboard, users, reports, and basic/advanced modes into a more consistent web experience.

PHASE 03

Remove legacy ambiguity

Align docs and architecture around the active stack: REST + Web + TUI + PostgreSQL.

Human use cases

Concrete scenarios to show who uses Abhackus and what it solves in practice.

Board

Monthly close with evidence

Board members review pending items, approve or reject sensitive income, validate balances, and download club reports for treasury and assembly work.

Administration

Daily user and dues management

An admin creates users, adjusts roles, reviews usage status, handles quota-change requests, and keeps project settings aligned with operations.

Community

Clear follow-up for members

Each participant can review personal history, upload proof attachments, request quota changes, and consult personal reports without relying on manual support every time.

Real workflows

Short sequences that show how work moves between people, system behavior, and audit trail.

Income and expense control

  1. 1 Register a movement or import it from ODS.
  2. 2 Attach proof and payment method when needed.
  3. 3 Approve or reject sensitive income from the admin inbox.
  4. 4 Reconcile the period and export evidence for the closed month.

Notifications and confirmations

  1. 1 An admin sends an internal notice to a chosen audience.
  2. 2 The notice may require read tracking or explicit ACK.
  3. 3 Users see alerts on entry and mark them as read/acknowledged.
  4. 4 Admins review read and confirmation metrics.

User management

  1. 1 Create a user and assign an initial role.
  2. 2 Adjust permissions, active state, and project identity settings.
  3. 3 Monitor usage and persistent accessibility preferences.
  4. 4 Recover access with recovery/reset flows when needed.

What you can manage

Income, expenses, and default dues

CLP accounting, project-level breakdown, monthly quota allocation, and periodic reconciliation.

Users, roles, and access

Account creation, superadmin/admin/participant/friend roles, revocable sessions, and password recovery.

Notifications and internal communication

Internal messages, contact-admin flows, planned Telegram/SMTP integrations, and read/ACK tracking.

Reports and audit trail

Personal and club HTML/PDF reports, monthly ODS export, and approval traceability with reason and UTC.

Suggested screenshots for this landing

Screenshots currently available under `public/screenshots/`, already optimized for web delivery.

Main Abhackus dashboard

Hero dashboard

General overview with accounting summary, pending items, and operational status.

User and role management

User management

Admin list with roles, active state, and management actions.

Accounting approval inbox

Approval inbox

Pending income entries with approve and reject actions.

Income or expense detail

Income/expense detail

Movement detail with payment method, attachments, and relevant breakdown.

Approval and rejection audit trail

Accounting audit trail

Timeline or table with actor, reason, state change, and UTC.

Exportable system reports

Exportable reports

Club/member report or evidence of HTML, PDF, or ODS export.

Internal notifications for the community

Internal notifications

Admin send flow with audience, requires ACK, and read metrics.

Project settings page

Project settings

Project identity, default dues, and operational parameters.

Download and run

Access source code, OS/module binaries, a compilation manual, and community collaboration entry points.

Source

Download source code

Clone the full repository to inspect, audit, and adapt each module in the stack.

Open repository

Binaries

Download binaries by OS and module

Operating-system and module guide to locate, validate, and run prebuilt artifacts.

Open binaries guide

Manual

Compilation manual

Recommended local build path, test/coverage validation, and packaging workflow.

Open technical manual

DB

Database and connection parameters

DATABASE_URL format, recommended PostgreSQL version, and commands to obtain host/port/user/database values.

View PostgreSQL page

Security

JWT secret per project

How to generate, store, and rotate ABHACKUS_JWT_SECRET safely for each environment/project.

Open JWT guide

API

OpenAPI + Swagger

Official REST endpoint contract with authentication and response details in an interactive explorer.

View API docs

Observability

Metrics, alerts, and monitoring integration

Prometheus endpoint, baseline alert rules, and guidance to connect Grafana/Alertmanager.

Open observability page

Efficiency

Rust efficiency and ecological impact

Why Rust helps reduce runtime resource usage and how to measure it objectively in Abhackus.

Open efficiency analysis

Community

Open collaboration

Contribution path with quickstart guide, prioritized issues, and merge request flow.

Go to community