Architecture
Technology Overview
Last reviewed: September 5, 2026
JoeLog favors server-rendered pages, explicit tenant boundaries, and restrained browser code. This overview describes the application as implemented in the current source; it does not identify a production host or promise an operating environment that has not been confirmed.
Application and interface
The server is written in Go using net/http. HTML templates and static assets are embedded into the application. Most interactions are server-rendered, with HTMX used for targeted page updates and Tailwind CSS utilities used for presentation. This keeps core recordkeeping workflows usable without a large client-side application.
Data boundaries and record history
MariaDB with InnoDB stores application data. Tenant relationships carry organization identifiers, and membership is checked before an organization's store is opened. Regulated-record workflows preserve versions and audit context instead of treating every correction as an untraceable overwrite.
These are logical application and database boundaries. They are not a claim that every datum is physically isolated or universally encrypted.
Identity and request protection
Passwords use Argon2id hashes. Authentication uses opaque server-side sessions with revocation, email verification, optional TOTP multi-factor authentication, and recovery codes. State-changing browser workflows use CSRF protection. Public responses add content security, referrer, MIME-sniffing, and framing headers.
Sensitive fields, documents, and mail
Sensitive Form 4473 response payloads use application-level encryption. Uploaded documents are designed for private S3-compatible object storage with server-side encryption requests and integrity verification. Service email is sent through SMTP with STARTTLS support. Provider names and deployment regions are omitted because the production choices are not confirmed here.
Verification and current limits
The repository includes Go unit and integration tests, MariaDB-backed checks, and automated browser accessibility checks. Their presence is not evidence of a completed independent audit, penetration test, certification, production uptime level, malware-scanning service, backup policy, or tested disaster-recovery process.
JoeLog is not currently an ATF-compliant electronic recordkeeping system and must not be used as one.
Operational disclosure
Send privacy, legal, support, technology, and security questions to aubergine@joelog.com. Formal safe-harbor and response commitments are not yet published. Do not email sensitive data, and do not perform unauthorized security testing.