Hardware

We design printed circuit boards, and the prototypes and enclosures that go with them, together with the software that runs on them or on their own for software you already have.

A device drawn from the front and the side, with its width, height and depth marked

Circuit boards drawn up for the job they do

We produce the schematic and lay out the board around what the system needs it to carry: the controller, its connections, its power and the headers that join it to everything else. Where a board will sit in a cabinet, on a machine or by a door shapes where its connectors go and what it has to put up with.

Where we also write the software that runs on the board, the two are designed at the same time, which keeps them honest with each other. A pin is not left unconnected because nobody told the firmware about it. Where the software already exists, the board is designed to it.

A printed circuit board seen from above and to one side, with a microcontroller, headers, a voltage regulator and routed traces
An enclosure pulled apart on guides: the lid with its light window, the circuit board, and the base with the bosses the board sits on

Prototypes and enclosures, made to fit the board

Prototypes, enclosures and mounts are made to fit the board, by whichever method suits the part, so a design can be checked in the hand before it is settled. If a connector is hard to reach or a wall is too thin, that shows up on the first part in days, and the next version is made with the fix.

An enclosure drawn around the board holds it in place and leaves its connectors, indicators and fixings where they can be reached.

How a hardware project runs

The same stages as a software project, with a prototype in the middle.

  1. The requirements go into the specification

    What the board has to do, where it will sit, what it connects to and what it must survive, agreed in writing before anything is drawn.

  2. Schematic, then layout

    The circuit is drawn up and checked, then its parts are placed and the connections routed on the board.

  3. A prototype, built and tested

    The board is made up, the firmware loaded, and the whole thing tested against the requirements before the design is settled.

  4. The enclosure is made and the design written up

    An enclosure is made to fit, and the design is documented so that it can be revised or manufactured later.

What you receive

  • Schematic and board layout files
  • A prototype, built and tested
  • An enclosure made to fit the board
  • Written documentation of the design

Production manufacturing and certification are separate work and are agreed separately. For a first view of which rules are likely to apply to a product, try the free product compliance checker.

Tell us what the board has to do

Where it will sit, what it connects to and what the software around it needs. We will reply to arrange a conversation.