Managed · verified · written delivery

Software work without another project to manage.

You describe the outcome. CodeVolt locks the scope, does the work, checks it and returns a clear delivery pack.

Choose a starting point See how it is checked

No model names. No invented test results. No production access by default.

Services

Five practical ways to start

Available means the delivery lane is open now. Pilot means we confirm suitability and controls before accepting the work.

available Assessment

Repository Baseline

A clear, evidence-backed view of what is healthy, what is uncertain and what should be fixed first.

Best for

  • Taking over an unfamiliar repository
  • Planning investment, handover or stabilisation

You receive

  • Build, test and dependency findings
  • Risk-ranked code, documentation and security observations
  • A practical first-three-actions plan
  • Checks we could and could not run

Assessment only. No production changes, secrets, pentest or certification.

Assess a repository
available Delivery

Verified Fix

A bounded defect diagnosed, fixed, tested and delivered as a reviewable patch or pull request.

Best for

  • A reproducible bug with expected behaviour
  • A small change that needs proper evidence

You receive

  • Root-cause explanation
  • The smallest complete code change
  • Regression-test and quality-check results
  • Independent review, known limits and rollback note

No merge or live deployment unless separately agreed.

Request a verified fix
pilot Assurance

Release Readiness Check

A written ready, ready-with-warnings or not-ready decision tied to reproducible evidence.

Best for

  • A release branch approaching production
  • An independent check before a significant merge

You receive

  • Build, test and dependency evidence
  • Migration, configuration and rollback review
  • Risk-ranked blockers and warnings
  • A concise release decision with stated limitations

Not a business, legal or regulatory approval. Deployment is separate.

Check a release
pilot Ongoing

Managed Repository Care

Ongoing repository attention without making you manage another development queue.

Best for

  • A small business with one important repository
  • Dependable maintenance without another full-time hire

You receive

  • Dependency and CI health review
  • Documentation and test-drift findings
  • Agreed low-risk maintenance pull requests
  • Exception-led reports and an evidence summary

Only agreed repositories and change classes. Sensitive or production work is separately controlled.

Discuss repository care
pilot Build

Website Build and Management

A new or rebuilt website designed, built and delivered to agreed scope — with an optional ongoing management plan.

Best for

  • A business that needs a working website without managing a development queue
  • An existing site that is outdated, slow or difficult to maintain

You receive

  • Design direction, page structure and agreed content list
  • Built and tested site delivered to a reviewable state
  • SEO fundamentals: page titles, meta descriptions and structured URLs
  • One review cycle; material scope changes return for a revised quote

Hosting, domain and DNS not included unless separately agreed. No unlimited revisions, ongoing content writing or third-party integrations.

Discuss a website project
available Consultancy

Cyber & Technical Security Consultancy

Senior, human-led support for policies, standards, document sets, requirements, assurance and technical review.

Best for

  • A defined security decision or documentation need
  • Project support or bounded recurring oversight

You receive

  • Agreed scope, evidence and deliverables
  • Documented findings, limitations and next actions

Not an emergency or on-call service. Recurring work uses agreed capacity and response windows.

Explore security consultancy
Confidence

What "verified" means here

  1. The job is locked

    The expected outcome, repository boundary, prohibited areas and acceptance checks are written before work starts.

  2. The evidence is real

    Commands, tests and checks are run against the supplied material. Failed and unavailable checks stay visible.

  3. The work is independently checked

    Implementation does not approve itself. Relevant code, quality and security checks are reviewed separately.

  4. You receive a delivery pack

    Changes, evidence, limitations, refused work and rollback information arrive together in writing.

Access

Start with less access, not more

A sanitised copy or temporary private repository is preferred. Do not send passwords, tokens, private keys or customer data. Repository write access, merging, deployment and production administration are separate decisions — not defaults.

Request

Tell us what outcome you need

The website does not collect or store requests. Send a short, non-confidential description by email. We review suitability and scope before payment or access.

Email your request Read the privacy notice