EAWF

EAWF Business Management System

Return to EAWF Main Page

1. 1. Purpose

The EAWF Business Management System (EBMS) is a collection of self-hosted business applications designed to support EAWF operations.

The system is intended to provide:

• Customer Management
• Student Management
• Billing and Invoicing
• Bitcoin Payment Processing
• Knowledge Management
• Help Desk Operations
• Hosting Management
• Training Management
• Reporting and Analytics

All critical business functions are designed to remain under EAWF control without dependence on SaaS providers or subscription-based business systems.

---

1. 1. Design Philosophy

The EBMS shall prioritize:

• Self-hosting
• Open source software
• Data ownership
• Long-term maintainability
• Minimal external dependencies

The EBMS shall avoid:

• SaaS platforms
• Vendor lock-in
• Subscription business software
• Third-party billing systems
• Cloud-hosted management platforms

Preferred technologies:

• Linux
• Apache
• MariaDB
• PHP 8
• Bitcoin Core
• MediaWiki
• osTicket
• Roundcube
• FPDF

All critical business data shall remain under EAWF control.

---

1. 1. Current Projects

1. 1. 1. Billing System

Customer billing, invoicing, payment tracking, and Bitcoin payment processing.

EAWF Billing System

1. 1. 1. Help Desk

Customer support and ticket management.

EAWF Help Desk

1. 1. 1. Knowledge Base

Documentation, procedures, training materials, and internal reference information.

EAWF Knowledge Base

1. 1. 1. Hosting Management

Domain, hosting, email, and infrastructure management.

EAWF Hosting Management

1. 1. 1. Training Management

Classes, students, instructors, attendance tracking, and course materials.

EAWF Training Management

---

1. 1. EAWF Billing System

1. 1. 1. Documentation

• EAWF Billing System/Security
• EAWF Billing System/Database
• EAWF Billing System/Invoices
• EAWF Billing System/Payments
• EAWF Billing System/Bitcoin
• EAWF Billing System/Watcher
• EAWF Billing System/Reports
• EAWF Billing System/Roadmap
• EAWF Billing System/Philosophy

1. 1. 1. Current Design Status

Status: Planning

Core Components:

• Users
• Clients
• Invoices
• Invoice Lines
• PDF Generation
• Bitcoin Integration
• Customer Portal
• Reporting

---

1. 1. System Architecture

1. 1. 1. Public Infrastructure

Server:

• talon

Responsibilities:

• Customer Portal
• Billing
• Invoices
• Payment Pages
• Documentation
• Help Desk

1. 1. 1. Private Infrastructure

Server:

• Home Bitcoin Node

Responsibilities:

• Bitcoin Core
• Mining
• Address Monitoring
• Payment Detection
• Confirmation Tracking

No public Bitcoin Core services are exposed.

All communication is outbound from the home node.

---

1. 1. Security Model

Security levels determine page access.

| Level | Description | | ----- | ------------- | | 0 | Guest | | 1 | User | | 2 | Client | | 3 | Student | | 4 | Reserved | | 5 | Instructor | | 6 | Clerk | | 7 | Manager | | 8 | CFO | | 9 | Administrator |

A higher level inherits all lower-level permissions.

See:

EAWF Billing System/Security

---

1. 1. Development Roadmap

1. 1. 1. Phase 1

• Users
• Clients
• Settings
• Invoices
• Invoice Lines
• PDF Invoices

1. 1. 1. Phase 2

• Payments
• Audit Log
• Invoice Events
• Client Notes
• Documents

1. 1. 1. Phase 3

• Bitcoin Drawers
• Address Derivation
• Payment Pages
• QR Codes

1. 1. 1. Phase 4

• Home Watcher
• Bitcoin Core Integration
• Automatic Payment Detection

1. 1. 1. Phase 5

• Customer Portal
• Email Receipts
• Reporting

1. 1. 1. Phase 6

• Optional Lightning Support

---

1. 1. Guiding Principle

When a choice exists between:

• Self-hosted versus SaaS
• Open source versus proprietary
• Owned infrastructure versus rented infrastructure

The preferred solution is the one that maximizes EAWF ownership, control, portability, and independence.