Users
?
Total accounts currently tracked by the backend.
Separate frontend + backend in progress
A clearer face for certificate operations.
The live Laravel app remains stable while this new frontend workspace becomes the dedicated interface for users, admins, renewals, notifications, and domain workflows.
Runtime Snapshot
Current structure
Monolith live
Transition
CA environment
Unavailable
backend
Mail sender
Unavailable
frontend
Domains
?
Registered websites across manual DNS and HTTP validation flows.
Certificates
?
All certificate versions recorded in sslbag.
Active versions
?
Latest stored certificate versions currently marked active.
sslbag
Manual validation
Guided DNS-01 and HTTP-01 challenge flows with real certbot-backed issuance.
sslbag
Certificate storage
Versioned filesystem storage for private keys, certs, chains, and metadata.
sslbag
Admin operations
User controls, domain suspension, notification resend, failed-job retry, and audit visibility.
Architecture
Split the UI from the certificate engine.
The backend stays focused on auth, jobs, ACME execution, storage, notification logic, and admin policies. The frontend becomes a dedicated product surface with its own routing, components, and design system.
unknownruntime unavailableoverview unavailable
backend
- Laravel auth and policies
- Certificate workflows and ACME jobs
- Filesystem storage and downloads
- Scheduler, queue, audit logs, settings
frontend
- App shell and design system
- User and admin dashboards
- Form-heavy domain and certificate flows
- Cleaner product presentation and navigation
Next
Next frontend steps for sslbag
Step 01
Keep the backend in /backend and frontend in /frontend with stable JSON contracts.
Step 02
Forward authenticated dashboard data into the new user and admin shells.
Step 03
Replace the current Blade-heavy UI gradually, without interrupting live certificate workflows.