We build and secure the systems your business runs on.

VXSec builds the software, automations and tool connections your business depends on, fixes them when they break, and looks after the cloud and access underneath so they keep working.

Start in writing. Say what you need built or what is going wrong. A written reply with the next step comes back within two business days.

Written replyWithin two business days
You send
What should happen, what happens now, the systems involved, and links if you have them
Next step
For a defined job, a plan and a fixed price. When the cause is unclear, the questions or a short priced investigation
Price
Fixed, agreed in writing before work starts
Verification
How the result is checked on real data before it is called done
Security
What the work may read, change and send, listed and gated
Starts in writingReply from [email protected]

What you can hire VXSec for

Pick the job. The technical work underneath is VXSec's problem.

Build and integrate

A defined application, feature, integration or AI workflow, delivered and verified.

See what you get

Repair and improve

A failing system investigated, the cause fixed, the change checked.

See what you get

Ongoing engineering

Agreed monthly capacity for the systems you name.

See what you get

Security review and hardening

Access, credentials, authorization and release controls reviewed, with findings you can act on. Fixes implemented and rechecked where the plan includes them.

See what you get

Situations VXSec can help with

Three common starting points. You do not need to know which category the problem belongs to. Describe it in writing and the reply says what comes next.

Your application needs more engineering.

An internal tool or product needs new capabilities, more dependable data, or a clearer permission model.

See related work

Your systems keep losing the connection.

An integration stops updating, a background job fails, or staff keep repeating work the software should handle.

See related work

Your infrastructure or access needs to change.

You need to move an application, organize shared resources, or change who can reach sensitive systems and data.

See related work

Selected work

Real deliveries: what the client had, what was built, what changed.

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

Read the full record

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 the work covers

VXSec covers all four, so the software, the automation, the hosting and the access are planned together instead of patched together.

  • SYSTEMS

    Systems engineering

    Internal tools, product features and the syncs between your apps, built to be changed safely and repaired when they stop working.

  • AI

    AI and agentic systems

    Reports that write themselves, monitors that flag problems, and assistants that answer staff questions, each doing one defined job inside limits you can see.

  • CLOUD

    Cloud, infrastructure and identity

    Where your applications run, moves between providers, and who can log in to what, from a new hire's first day to their last.

  • SECURITY

    Security engineering

    Permissions, passwords and API keys handled properly inside every build, plus a standalone review and fixes when a system needs checking.

How the work runs

Four steps, each recorded in writing, so you always know where the work is.

  1. Describe the need

    Send the system, the problem or the planned change, and any constraints. You do not need to diagnose it first.

  2. Get the plan

    VXSec replies in writing with the next step. For a defined job that is a plan and a fixed price. When the cause is not yet clear, it is the questions or the short, priced investigation needed to get there.

  3. Build or repair

    Changes follow the agreed plan, with progress and decisions recorded in writing.

  4. Verify and hand over

    Agreed outcomes are checked, the result documented, and the code, configuration and operating instructions handed over. Ongoing engineering is available where agreed.

Access and security are part of the engineering

The plan names the systems and data involved, who needs access, and which actions need extra controls. Authorization, credential and release checks are included in the work and documented at handoff.

This applies to every engagement, not only the ones bought as a security review. Who can log in, where the keys are kept, and what gets checked before a change goes live are decided while the system is built, not added afterward.

Need the review on its own? Security review and hardening is also sold separately: a scoped review of access, credentials, authorization and release controls, with evidence-backed findings and remediation. Fixes are implemented and rechecked where included in the agreed plan. See Security review and hardening on the Services page.

Common questions

What will it cost?

A fixed price after a written plan. When the cause is not yet known, a short investigation is priced first, on its own, only where it is really needed. Small first jobs are welcome.

Can you work on something another developer, or an AI tool, built?

Yes, after an initial look at its behavior, dependencies and access. You get the repair or development plan in writing.

How do I start?

Use the intake form to describe what should happen, what happens now, and the systems involved. A written reply with the next step comes back within two business days.

How do I know the job is done?

Outcomes and acceptance checks are agreed before the work starts and shown at handoff.

Who does the work?

VXSec does the work directly. Anyone else involved in a job is named in the plan before work starts.

What happens afterward?

Handoff, an agreed correction period, and optional ongoing engineering.

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.