~ / contact

Send us the hard version of the question

This form goes to a shared engineering inbox, not a CRM. A principal engineer reads it and replies — usually within one working day, always with something useful, even if the answer is that we are not the right people.

POST /enquiries

Technical enquiry

Fields marked * are required. The more specific the problem statement, the more specific the reply.

Cloud, orchestrator, IaC, CI, observability, primary datastore.
Minimum 20 characters. We read all of it.

Or email engineering@gridworks.engineering directly.

202 Accepted

 enquiry queued        ref GW-0000-XXXXXX
 routed to             principal on rotation
 expected first reply  < 1 working day
  ── no autoresponder follows this message

Thanks, there — that is in the queue. If it is urgent, reply to the confirmation email with [URGENT] in the subject and it will page the on-call principal instead of waiting for the morning triage.

The architecture review

90 minutes, free, no slides

A working session with a principal engineer. Bring whatever you have — a diagram, a Terraform repo, a post-incident doc, or just the thing that keeps going wrong.

  • 0–15 min · your architecture, as it actually is
  • 15–45 min · the failure modes we can see, and the ones you have hit
  • 45–70 min · cost, delivery and reliability baselines — what is measurable today
  • 70–90 min · the five things we would do first, in order

You get a written summary within two working days whether or not you engage us. It is yours — use it to brief your own team or another vendor.

contact — channels whois
general     engineering@gridworks.engineering
security    security@gridworks.engineering
pgp         4F2C 91AE 77D3 0B18 6C55
            A0E9 3B71 D4C2 88FE 1A60
registered  GridWorks Engineering Ltd
            Company No. 11938204
            Unit 4, Temple Studios
            Bristol BS1 6QA
hours       08:00–19:00 UTC, Mon–Fri
on-call     24/7 for contracted clients
now         00:00:00Z
Median first reply
6.2h
working hours, last 90 days
Reviews booked / qtr
31
roughly 1 in 4 becomes work
Security disclosure

Found something in one of our open-source projects or on this domain? Email security@gridworks.engineering, encrypted if you prefer. We acknowledge within 24 hours, aim to remediate inside 14 days, and will credit you publicly unless you ask us not to.

security.txt · /.well-known/security.txt

What happens next

The whole process, before you commit anything

STEP 01

Reply from an engineer

Within one working day, with either clarifying questions or a proposed time. Not a calendar link from a coordinator.

< 1 working day
STEP 02

The review

Ninety minutes on a call, screen shared, whiteboard optional. NDA before it if you want one — send yours, we rarely object.

90 minutes · free
STEP 03

Written summary

Top five risks, what we would do about each, and a rough shape of effort. Yours to keep regardless of what you decide.

2 working days
STEP 04

Proposal, if it fits

Scope, milestones, named engineers, acceptance criteria and an end date. One page of commercials, not twelve.

1 week