The stack we engineer on, and how we engage.

Assessments and clearly specified builds are quoted as fixed price against a written scope. Evolving work is priced as a dedicated pod with a monthly rate per named role. Managed services are priced on the estate under management plus a reserved engineering allocation. In every case you receive a breakdown by component and the assumptions behind it, so you can challenge the model rather than just the number.

You do, from the first commit. Work is delivered into repositories you control, under your accounts and your credentials. We do not retain private forks, and we do not build deliberate dependencies on Vandorq-hosted tooling. Third-party licences, where any are required, are disclosed in the proposal.

Regularly. We are often engaged as the design authority across a mixed supplier landscape. We will document interfaces and responsibilities clearly, raise conflicts early, and provide an honest assessment of another party's work when asked — in writing, and with evidence.

Every managed engagement includes an exit plan from the start: access inventory, runbook completeness checklist, knowledge-transfer sessions and a defined handover period. We would rather leave cleanly and be re-engaged later than hold a client through operational dependency.

Production data is not copied into development environments. Where realistic test data is required we generate synthetic or masked datasets. Access is least-privilege and time-bound, engineers work through logged access paths, and data-residency requirements are agreed before any environment is created.

That is the most common shape of our long engagements. Our engineers work in your repositories, your ceremonies and your review process, with an agreed split of ownership. Your team sits in our design reviews from day one, which is also how the knowledge transfer happens.