Home / Services

Four ways to hire VXSec, one written plan before any work starts.

Pick the job you need done. The technical discipline underneath is explained further down for the people who want to inspect it.

Get a plan and a price See the work

The four ways

Each one starts with a written plan and ends with a handoff that is verified and written down. If none of them fits, send the situation in writing and the reply will say which one applies.

Build and integrate

You want something built. A report that writes itself, a monitor that pages someone, a sync between two systems, a feature your application is missing, a workflow that runs without a person pushing it.

  • What you get: a defined application, feature, integration or AI workflow, delivered and verified on real data before it is called done.
  • Fits when: you can describe what should happen, even roughly, and the job has a clear end.
  • Proof: the internal operations platform and integrations VXSec builds for RayInTheDark, and the QuickBooks to Mailchimp integration made reliable for Gabriel Service and Repair.
  • How it is priced: fixed price after a written plan.
Describe what you need built

Repair and improve

Something you rely on keeps breaking. A sync that dies when a token expires, an application that fails under real use, admin roles nobody remembers granting, connected apps with more access than anyone meant to give.

  • What you get: investigation of a failing system, the cause corrected, the change verified.
  • Fits when: something you rely on is failing, slow or fragile, whoever built it, including work by another developer or an AI tool.
  • Proof: the QuickBooks to Mailchimp sync repaired for Gabriel Service and Repair, and the data and reliability work inside RayInTheDark's operations platform.
  • How it is priced: fixed price after a written plan. A short, separately priced investigation comes first only when the cause is genuinely unknown.
Describe what is failing

Ongoing engineering

It exists and nobody owns it. Systems someone built, maybe a contractor who left, maybe a tool that grew. They run until they do not.

  • What you get: agreed monthly capacity for named systems after an initial assessment: fixes, small changes and monitoring inside the agreed capacity, and a written record of what was done.
  • Fits when: named systems need someone accountable every month, and you want the capacity and its limits agreed in writing.
  • Proof: the systems engineering for RayInTheDark's internal operations platform: application, integrations, infrastructure, releases and security, looked after month to month.
  • How it is priced: monthly, after an assessment of the inherited system. The capacity is agreed in writing and the runbook stays with you.
Describe what you inherited

Security review and hardening

It acts on real systems and you need to know what it can do. A workflow that reads customer email, touches money or writes to production, or a customer asking you to fill in a security questionnaire about it.

  • What you get: 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.
  • Fits when: a system reaches customer data, money or production, or a customer or partner is asking what it can do before they rely on it.
  • Proof: the security engineering inside RayInTheDark's operations platform, and the access rebuilt for Ingersoll Support Services.
  • How it is priced: fixed price after a written plan. The review gives findings, hardening implements them, verification confirms the agreed fixes. Bought together or separately, and remediation beyond the agreed plan is priced as its own line.
Describe what it can reach

What every engagement includes

The same commitments on every job. They are what make a fixed price possible.

  • A written reply within two business days of your message, with the next step. For a defined job, a plan and a fixed price, with what is out.
  • A plan with acceptance criteria that you approve before anything is built or changed.
  • Verification with evidence: the agreed checks run on real data, with the results attached to the handoff.
  • Access and security inside the work: what the system may read, change and send is listed and gated, credentials are kept out of prompts, logs and repositories, and a person approves what ships.
  • Handoff documentation: what was built or changed and how to run it, with an access map where access was involved. You own the deliverables and the access. Third-party software and services stay under their own terms.
  • Least access, removed at the end unless ongoing engineering continues. Admin actions are recorded where the systems allow it.

What the work covers

Every job above draws on four areas. Security can be part of any engagement or a separately scoped review.

  • SYSTEMS

    Systems engineering

    Internal applications, APIs, integrations, databases, debugging and release engineering.

  • AI

    AI and agentic systems

    Reporting, monitoring, retrieval and controlled operational workflows: AI that does a defined job inside limits you can see.

  • CLOUD

    Cloud, infrastructure and identity

    Hosting, migrations, deployment, accounts, permissions and the access lifecycle, from the first day to offboarding.

  • SECURITY

    Security engineering

    Authorization, credential handling, isolation, scoped review, remediation and verification.

How a price is reached

There is no price list. The written plan sets the price before any work starts.

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.

Is there a minimum project size?

No. Small first jobs are welcome, and they are priced the same way: a written plan, then a fixed price.

When do you charge for investigation?

Only when the cause, or the size of the job, genuinely cannot be known from your description. The investigation is short, priced on its own and agreed before it starts. Simple, well-understood requests never go through paid discovery.

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.

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.

Get a plan and a price

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.