Skip to main content

Dev Station Technology

Get a quote
Get in touch

United Kingdom

Software for UK companies, built to the standards you are audited against

Our first two published builds were both for British companies: a manufacturer of portable pull testers, and an inspection provider working at height. Both turned on getting a measured value into a record that would still stand up two years later.

Book a 30-minute scoping call See the standards we build against

Your 9am in London, Manchester or Edinburgh is our 3pm. An engineer reads what you send, not a sales rep.

What a UK buyer usually asks in the first ten minutes.
Where does our data sit Azure UK South or AWS LondonUK region
Working day overlap Vietnam is 6 to 7 hours aheadTo 12pm
Who owns the code From the first commitYou do
Published UK builds Hydrajaws and a work-at-height provider2
Who you talk to The engineer writing itDirect
The first row is the one that ends most conversations early, so we answer it first.

Our UK work

  • Hydrajaws LimitedUK manufacturer of portable pull testers
  • Work-at-height providerUK anchor and torque proof-load testing
  • Data in a UK regionLondon or Cardiff, in your own tenant
  • Ho Chi Minh City10+ years working with UK teams

What the record has to survive

British Standards decide what your software must store, not just what it should show

Most inspection products are designed around a generic checklist. UK compliance work is not generic, and the gap usually shows up on the day somebody asks for the file.

Anchor testing, BS 8539 and BS 7883
BS 8539 covers the selection, supply, installation and testing of post-installed anchors in concrete and masonry, and it draws a line most software ignores: the proof load is not invented on site. It comes from the designer, the specification, the manufacturer or a competent person. A system that lets an engineer type any number has already failed the standard. The sampling rules matter too, since testing one in forty fixings and one in twenty-five carry different load factors.
Lifts, LOLER 1998 and BS EN 81
Regulation 9 requires a thorough examination by a competent person, at least every six months for anything that lifts people. The report is a statutory document with a defined list of items it must contain, and where the equipment lifts people it has to be kept for the working life of that equipment rather than a couple of years. Software that treats the report as a printout rather than as a retained record is the wrong shape.
Calibration, UKAS and BS EN ISO/IEC 17025
Your torque wrench comes back from a laboratory with a certificate that names a parameter, a range and an uncertainty, tied to that laboratory's schedule of accreditation. What the software has to do is hold that certificate against the instrument, know when it expires, and refuse a reading taken after that date rather than accepting it and flagging it in a report a fortnight later.
Quality management, BS EN ISO 9001
Clause 7.1.5 on monitoring and measuring resources is the one that reaches the software. An auditor asks for the reading, the instrument it came from and evidence that instrument was fit to use on the day. A system that answers all three in one screen turns a difficult hour into a short one.
Public sector bidding, Cyber Essentials and UK GDPR
Cyber Essentials has been a condition of central government contracts handling personal data since 2014, and every G-Cloud supplier needs it. The technical controls behind it are ordinary engineering: access enforced on the server, credentials in a vault, patching that happens, and a boundary somebody can describe. We build those during the project, and your certification body does the assessment.
Data residency under UK GDPR
Article 32 asks for appropriate technical measures, and in practice UK buyers ask a simpler question: where does the data physically sit. We deploy into your own tenant in a UK region, Azure UK South in London or UK West in Cardiff, or AWS in London, so the answer is one sentence rather than a paragraph about safeguards.

Our UK work

Two British builds, both about a number that had to be right

These are the UK engagements we can show you by name. We would rather list two you can read than a wall of logos.

Case study, United Kingdom

Reading the tester instead of reading the dial

Hydrajaws makes portable pull testers used across UK construction and safety compliance. Their old app could not talk to the instruments, so an engineer copied a number onto a form and typed it again later. We rebuilt the apps as a free tier and a premium tier from one codebase, put user management behind Azure AD B2C, and integrated the KTC SDK so torque and pull values arrive in the record as the instrument produced them.

  • Xamarin
  • .NET
  • Angular
  • Azure
  • Azure AD B2C
  • KTC SDK
Increase in potential clients after launch
500%
Tiers from one shared codebase
2
Digital torque testing opened automotive
New market

Case study, United Kingdom

Proof-load testing on a roof, filed by a duty holder months later

A UK inspection provider for work-at-height anchor systems needed to digitise proof-load and torque checks. Scheduled examinations against a defined procedure, capture on site where signal is unreliable, pass and fail logic tied to load values rather than to somebody's judgement, and a certificate at the end that the duty holder can file and defend.

  • Xamarin
  • .NET
  • Angular
  • Azure
Examinations against a defined procedure
Scheduled
Capture where signal is unreliable
Offline
Produced at sign-off, in the client format
Certificates

Read them in full: Hydrajaws Limited and the work-at-height testing platform.

What we build for UK companies

Twelve of the services UK enquiries actually start with

The full directory runs to twenty-five. These are the ones British companies bring to the first call most often.

Inspection and compliance

Where a British Standard, a regulation or an insurer decides what the record has to contain.

Digital quality inspection

Checklists replaced by a record that carries the measured value, the operator, the asset and the procedure it was taken against.

Gauge and instrument capture

Torque and load values read from the instrument, with the calibration certificate and its expiry held against every reading.

Lift examination software

Six-monthly thorough examinations, defect to repair, and a report that carries what a statutory report is required to carry.

Security and governance

The technical controls a UK procurement questionnaire asks about, built during the project rather than retrofitted before an assessment.

Building the software

The systems that carry the work, and the interfaces engineers use standing on a roof in the rain.

Web applications

Angular and React over .NET or Node, deployed into a UK cloud region you own.

Field mobile apps

Offline first for basements, plant rooms and sites with no signal, reading instruments over Bluetooth.

Data engineering

Ingestion, migration and reporting, including moving years of records off a system that is past end of life.

Teams and ways of working

How a UK company actually engages a Vietnamese supplier, and what each arrangement costs you in management time.

Staff augmentation

Engineers inside your process and your standup, under your management.

The rest sit on our full services directory, grouped the same way.

Tell us what your engineers do today

Three fields. An engineer reads it, not a sales rep. You get an answer within one working day, usually before your afternoon.

  • We map the procedure, the instruments and what the record must contain
  • You get a written view, including the view that a product already does it
  • No obligation, and no phone number needed to start

The practical side

What working with a Vietnamese supplier actually involves

None of this is exotic, and all of it is worth settling before anybody signs.

The working day
Vietnam runs six hours ahead of the UK in winter and seven in summer. Our afternoon is your morning, so you get an overlap to roughly midday your time every working day. That is enough for a standup, a demo and a decision, and it means questions asked at 9am are answered before lunch rather than the next day.
Where the data lives
In your own cloud tenant, in a UK region. We do not host client data on our own infrastructure and we do not need to, which removes a whole section from most security questionnaires.
The contract
A services agreement between your company and ours. Because you are buying a service from a supplier rather than engaging individuals, the questions your accountant will ask are about VAT treatment on imported services rather than about employment status. Take that one to them; we will give them whatever they need.
Intellectual property
Yours from the first commit, written into the agreement, in every engagement model. Repositories, pipelines and documentation are handed over on request rather than at the end of the relationship.
Visits and site time
For inspection work we ask to watch the job being done at least once, because the workarounds engineers have invented are the requirements nobody writes down. That has meant a site in the UK for both of our British builds.
Evidence for procurement
If you are bidding for public sector work, tell us early. The controls, the audit trail and the residency answer are far cheaper to build during the project than to retrofit three weeks before a submission deadline.

Who does the work

Twenty engineers, eight of them senior

Small for an offshore supplier, and deliberately so. On a team this size the person who scopes your build is the person who writes it, and you meet them before anything is signed.

Engineers in Ho Chi Minh City
20
Senior engineers
8
Average experience
5+ yrs
Working with US, UK and EU teams
10+ yrs

You interview everyone we put forward, on every engagement model. We screen and shortlist, you take the final call.

How we work

Five engagement models, and you pick how much you keep

The models differ in one thing: how much of the management you hand over. Everything else, including who owns the code, is the same in all five.

Changing model later is normal. Augmentation into a dedicated team is the common direction, and the people stay.

01

Staff Augmentation

Engineers join your team and work inside your process, your board and your code review.

Team control
You manage the day to day
Pricing
Monthly per person, by role and seniority
Minimum
1 month

02

Dedicated Team

A team that works only on your product, with a lead on our side running delivery.

Team control
Shared. Our lead runs delivery, you set priorities
Pricing
Monthly per role, lead included
Minimum
3 months

03

Offshore Development Centre

A long-term engineering site under your standards, where we carry recruitment, HR, payroll and equipment.

Team control
You direct the work, we run operations
Pricing
Monthly per role plus site costs
Minimum
6 months

04

Fixed Price

One price for a scope that is genuinely settled, with the overrun carried by us.

Team control
We deliver, you accept against written criteria
Pricing
Fixed bid, paid against milestones
Minimum
Project based, usually 10 to 14 weeks

05

Build, Operate, Transfer (BOT Model)

Everything in the centre model, with the whole team moving into your own Vietnamese entity on an agreed date.

Team control
Transfers from us to you
Pricing
Monthly per role, transfer price agreed up front
Minimum
2 to 6 years

FAQs

Questions UK companies ask first

How much of the working day do we actually overlap?

Vietnam is six hours ahead of the UK in winter and seven in summer, so our working afternoon covers your morning through to roughly midday. In practice that is a standup, a demo and any decision that needs both sides. Anything you send after your lunch gets picked up first thing our next morning, which is still before your following working day starts.

Can our data stay in the UK?

Yes, and it is the normal arrangement rather than a special request. We deploy into your own Azure or AWS tenant in a UK region, London or Cardiff, and we do not hold client data on our own infrastructure. Access is granted by you and revocable by you.

Do you understand British Standards, or will we be explaining them?

You will be explaining your specific procedure, because every duty holder writes it slightly differently, and we would rather ask than assume. What you will not be explaining is why the proof load has to come from the specification rather than from the engineer, or why a report has to be retained rather than printed. Our two UK builds were both in this territory.

Have you worked with British companies before?

Two published builds, both British: Hydrajaws, a manufacturer of portable pull testers, and an inspection provider working at height. Our other named engagements are Norwegian and German. We list what we can show rather than a map with pins in it.

Are you the right size for us?

Twenty engineers, so we are the right size for a team of two to eight working on your product, and the wrong size for a programme needing fifty people next quarter. We will say which one you are on the first call rather than after a proposal.

What happens if we need somebody on site?

We travel for it. For inspection work we ask to watch the job at least once, and both of our UK builds included that. After the first visit most of the relationship runs on a fortnightly demo and a shared board.

Can you work alongside our existing supplier or in-house team?

Yes, and it is common. Under staff augmentation our engineers work inside your process and your code review. Where a boundary between teams is needed, we would rather draw it in the code than in a meeting, because the second kind never holds.

Who owns the code?

Your company, from the first commit, in every engagement model. That is written into the agreement rather than assumed, and the handover terms go in at the start rather than being negotiated at the end.

Send us the procedure, not the requirements document

The schedule of examination, the test regime, or a photo of the form your engineers actually fill in. Thirty minutes on that is worth more than a month of specification writing, and you will get a straight answer about whether building is the right call at all.

Book a 30-minute scoping call Read the standards section

Let's Talk