For Developers
Full source code.
Clean architecture.
Laravel 13. Action classes. Eloquent models. Blade templates. Standard PHP stack. No magic, no vendor lock-in, no build tools in production.
Stack
Built on a standard Laravel stack.
No proprietary frameworks. No compile steps in production. Your team already knows this stack.
Laravel 13 + PHP 8.4+
Clean architecture with Action classes for all write operations. Eloquent models, form requests, middleware. Standard Laravel conventions.
Tailwind CSS 4 + Alpine.js
Responsive UI with Tailwind utility classes. Interactive components with Alpine.js. No heavy JS framework.
SQLite or MySQL
SQLite by default for zero-config installs. MySQL 8.0+ for production scale. ULIDs as primary keys. No auto-increment IDs.
Blade PDF templates
Three PDF templates as standard Blade views. DomPDF rendering. Modify or add templates with PHP and CSS.
Security baseline
CSRF, rate limiting, bcrypt hashing, signed URLs, XSS prevention. Security headers middleware. Session idle timeout.
13 languages + RTL
Standard Laravel lang files. Arabic RTL support. Customer-facing PDFs and emails respect language preference.
Architecture
Built to extend.
Action classes
All write operations go through Action classes. Controllers are thin. Custom workflows can reuse the same Actions.
Domain events
DocumentCreated, DocumentFinalized, DocumentSent, DocumentPaid, PaymentRecorded. Hook into the lifecycle with standard Laravel listeners.
UBL 2.1 XML export
EN 16931 compatible XML export for every finalized invoice. Peppol fields ready in the schema for future network delivery.
Role-based access
Four roles: owner, admin, accountant, employee. Permission-gated screens and actions. Spatie permissions with ULID primary keys.
FAQ
Common questions.
Yes. Buyers receive the Laravel source code, Blade templates, Actions, migrations, and language files. Developers can adapt the installation for their own business or client workflow.
Yes. PDF templates are standard Blade views rendered with DomPDF. Modify the existing three templates or create new ones in /resources/views/pdf/custom/.
v1.0 enforces single currency (your company currency) at the validation layer. The schema already supports multi-currency. Enabling it is a validation rule change, not a migration.
No. The release package includes pre-compiled frontend assets. No npm, no Vite, no Redis, no external queue. Standard PHP hosting.
Upload the release ZIP to storage/app/update-packages/ and install from the admin Update page. Migrations run automatically. Custom PDF templates and language overrides survive updates.
Get started
Own the code. Own the data.
Full Laravel source code. Standard PHP stack. Deploy on any server.