Selected work: applications, integrations, infrastructure and security, described plainly.
Each record says what the client had, what VXSec built or repaired, and what changed.
Delivery records
The same facts in every record: the problem, the work, the verified change.
Delivery recordVX-01
Systems engineering for RayInTheDark's internal operations platform
- Client
- RayInTheDark, an ecommerce marketing agency that runs its client operations on an internal platform
- Built
- Engineering across the platform and its connected systems: application and data foundations, the client roster and specialist tools staff use every day, advertising, store and Discord connections, operational AI for monitoring and staff questions, and a reviewed process for releasing changes
- Runs on
- Next.js, TypeScript and PostgreSQL, with Meta, Shopify and Discord integrations
- One release
- Advertising and store data connected with reconciled totals, visible account-access states, and explicit missing-data states
- Kept safe
- Access by role and client, encrypted credentials, reviewed releases, and a separate test environment for the operational AI
Systems engineeringNext.js, PostgreSQL, Meta, Shopify
Delivery recordVX-02
Shared-drive ownership and access rebuilt for Ingersoll Support Services
- Problem
- Shared drives, groups and personal drives had grown over time, and access needed a clear structure.
- Done
- Shared Drive architecture by department, role-based access through Google Groups and permission tiers, personal-drive migrations, and a provisioning workflow written down so the next hire follows the same path
- Result
- Access that matches the org chart and survives staff changes.
Cloud, infrastructure and identityGoogle Workspace
Delivery recordVX-03
QuickBooks to Mailchimp integration repaired for Gabriel Service and Repair
- Problem
- A customer sync between QuickBooks and Mailchimp that stopped whenever OAuth tokens expired or the server restarted
- Done
- Token validation and refresh rebuilt, tokens persisted in a database so the sync survives restarts, the whole pipeline validated end to end
- Result
- A sync that runs without anyone re-authorizing it by hand.
Systems engineeringQuickBooks, Mailchimp, Supabase
Delivery recordVX-04
Application and database moved from Azure to OVH for Classlete
- Problem
- A PHP Laravel platform and its SQL database on Azure that had to move hosts without a long outage
- Done
- Infrastructure and database moved to OVH with minimal downtime, SSL and DNS cut over, Windows VM replication and load balancing set up
- Result
- The product running on its new host.
Cloud, infrastructure and identityAzure, OVH, Laravel
What needs building or fixing?
Tell VXSec what the system does, what you want to change, and what is getting in the way. Include links if you have them. Within two business days you get a written reply with the next step.
Or email [email protected] directly.
- You send: what should happen, what happens now, and the systems involved. No diagnosis needed.
- You get back: a written reply with the next step. For a defined job, a plan and a fixed price.
- Then: the work, verified and handed over in writing.