Inside the buildSystems engineering
Building a system you can actually operate
Inside the Modulus platform that connects files, speech tools, reporting, monitoring, and recovery—and the decisions that make those parts manageable.
See the workflow
A recording becomes a useful file
A recording enters the transcription service.
A durable job waits for an available worker.
The worker processes the recording and reports progress.
The finished transcript can be exported into Files.
- Platform architecture
- Application integration
- Recovery design
A recording needs transcription; its text needs somewhere useful to land. A report needs understandable status.
Modulus Lab connects those tasks through an internal dashboard, Files application, speech tools, reporting controls, and backup verification.
Give each service a clear job
The dashboard organizes the environment around Overview, Apps, Projects, Agents, Files, and Settings. Separate services handle measurements, file operations, transcription jobs, and report workflows.
The file browser does not need to know how a speech model loads. Reporting controls can trigger defined operations without unrestricted server access.
Architecture at a glance
- 01WorkspaceDashboard, files, and project controls
- 02ServicesExplicit APIs for each job
- 03StateQueues, file metadata, and run records
- 04RecoveryVersioned copies and restore checks
Status returns to the workspace. Recovery is a separate path that must be checked.
Follow a recording through to its result
The lecture transcriber connects directly to Files. An uploaded recording enters a durable queue, runs in a separate worker process, and can export its finished transcript into the library. Reconciliation retries missed exports.
Files adds folders, search, previews, downloads, and trash with restoration. Its logical file tree uses SQLite metadata; a separate transport handles network storage access.
Connecting processing to a discoverable result turns separate tools into a usable workflow.
Make status answer the actual question
The collector gathers measurements, storage information, activity, and device status for the dashboard. Reporting has more specific controls: Herald can request a report, resend it, check sources, and inspect operation state against n8n.
“Is the process running?” and “Did the report go out?” need different evidence. The platform keeps those questions close to the service that can answer them. The reporting bot also stays separate from the general server assistant, with a deliberately smaller set of operations.
Check what recovery can really restore
Backup tooling creates bundles of selected application data and configuration, computes hashes while streaming, and checks for required files. Companion tools verify bundles; restore checks inspect recovered content, including selected databases. Versioned mirrors and a NAS backup tier provide additional storage paths.
A readable archive does not establish that every service and external integration can be restored. Naming what each check proves keeps the remaining recovery work visible.
The business capability is connecting requests, durable work, usable results, and operational controls—so people can follow the work and intervene when needed.
About the cover illustration
Keep reading.
All articlesEngineering notes
The report is the last step
Inside an analytics reporting system that connects platform data, validates what the numbers mean, and makes delivery an observable part of the workflow.
Product engineering
A small key. A complete speech system
Inside Quill, a Windows dictation tool that connects native desktop controls, local speech models, and careful fallback behavior.
Bring us the work behind the work
A recurring report, a tool your team needs, or a process spread across too many systems. Start with the job you want to make easier.