Runtime hardening
Audited shared helpers and high-use endpoints for stricter null, array, request, and string behavior.
Vitalabs / Case study 01
Modernizing a mission-critical manufacturing portal.
Vitalabs needed its established product, compliance, asset, and administrative workflows to survive a major PHP and AWS modernization. Zyel stabilized the system in place and made production releases safer to operate.
ClientVitalabs
WorkLegacy modernization and cloud operations
PlatformPHP, MySQL, AWS, S3, CloudFront
The context
Years of decisions lived inside the portal.
Vitalabs is a private-label and custom supplement manufacturer with a public catalog, formulation services, fulfillment operations, and an authenticated management portal.
The portal supports the less visible work behind those services: product data, manufacturing records, compliance documents, digital assets, user administration, and operational approvals.
Replacing that system outright would have put embedded business logic at risk. The job was to preserve how the company worked while modernizing the runtime and cloud foundation underneath it.
The problem
The version number was only the beginning.
A move to a current PHP and AWS environment exposed assumptions throughout the legacy application.
Nullable values that older PHP versions tolerated began producing warnings or fatal type errors. Vendored libraries predated PHP 8 behavior. Production file access depended on older credential and metadata patterns. Authentication recovery, two-factor delivery, redirects, asset visibility, and deployment all needed to remain dependable while the system was being repaired.
The challenge crossed shared rendering, administrative lists, product screens, file uploads, Certificate of Analysis output, cloud credentials, and the release process itself.
The work
Modernize in place. Verify in production.
Cloud credentials
Reworked production S3 access around the server's managed role and the current instance-metadata security flow.
Asset operations
Moved delivery to private-origin CloudFront URLs and connected cloud files back to portal records.
Authentication resilience
Stabilized login, two-factor email delivery, redirects, password recovery, and controlled support access.
Release automation
Created a repeatable production process with environment preservation, checks, atomic switching, and verification.
Data-tolerant output
Hardened Certificate of Analysis rendering so legitimate nonnumeric or incomplete data could display safely.
The result
A portal that could keep moving forward.
- Production cloud storage restored and verified through the server's managed role.
- Direct visibility from cloud files to the products, panels, sources, and packaging records using them.
- Administrative and product-management screens verified under the newer PHP runtime.
- Certificate of Analysis output kept rendering when ingredient data contained unexpected values.
- Deployment moved from manual server changes to a repeatable, recoverable release workflow.
Why it matters
Legacy does not mean disposable.
Mature systems are often valuable precisely because they contain years of decisions, exceptions, and operational knowledge.
A safe modernization respects that value. Zyel's work with Vitalabs focused on removing runtime and infrastructure risk without discarding the workflows the business already depended on.