Selected work by our team during its LuckyTruck engineering tenure, 2021–2024. The case describes that contribution; LuckyTruck’s current product has continued to evolve.
Documents connected to operations
Certificates of insurance need to connect the correct insurance information with a usable document and the team handling the request. Our work included certificate services, PDF generation and a Zoho CRM certificate widget. These connected document tasks with the surrounding customer and operations workflow.
The implementation used pdf-lib in Node.js services and a separate Java signing service using iText and GlobalSign. A React signing library supported the product interface. These are distinct parts of the document lifecycle: preparing a PDF, collecting the user’s interaction and applying the signing integration.
GlobalSign integration
The signing work included a Java service packaged for AWS Lambda, PDF processing through iText, and certificate/signature handling with Bouncy Castle. The code also contains timestamp and certificate-validation components used by the integration.
For a buyer, the useful question is what a signed document needs to prove and how it will be checked later. That determines identity, signing, storage and verification requirements. The presence of a signing library alone does not establish every legal or regulatory requirement for a new deployment.
Public motor-carrier data from SAFER
Our SAFER services worked with US Department of Transportation / FMCSA motor-carrier information, including company summaries, inspection and crash summaries, and review information. The archive contains Lambda handlers and a service for collecting and structuring those records.
Public carrier information can help populate or contextualize a business record. It should retain its source and retrieval context. It is not a substitute for carrier underwriting, current policy information or private claims records, and a crash count does not by itself establish fault.
- Match information to the correct motor-carrier identifier.
- Keep missing or inactive records distinguishable from a successful match.
- Retain source context when using public data alongside customer-supplied information.
- Let the responsible team resolve discrepancies before a consequential decision.
Driver-license extraction with a review path
Our in-house OCR work turned document images into structured driver-license fields and connected them to the product. The review flow let operations staff check extracted information instead of starting every record with manual transcription.
That work is documented in the separate Document OCR case. A useful evaluation for a new workflow separates field correctness, required-field completeness and the proportion of documents sent for review. It should include poor images and missing fields, not only clean examples.
Technologies in this part of the platform
| Area | Technologies used |
|---|---|
| Certificate generation | Node.js, pdf-lib, Zoho CRM widgets |
| Digital signing | Java, iText, Bouncy Castle, GlobalSign, AWS Lambda |
| Product integration | React, REST/GraphQL services, AWS S3 |
| Public carrier information | SAFER / FMCSA data, Node.js services, Lambda and container workloads |
