Infrastructure and Technologies

We don't write everything ourselves; what we build on is a decision too

Home
/
Corporate
/
Infrastructure and Technologies

There's a lot underneath a system that we didn't write. The network that resolves the domain, the database that holds the data, the production line that prints the board, the services the application talks to. None of these are details to wave off as a procurement line item — they determine how the system actually behaves in the field.

We don't call these solution partners, because they aren't. There's no partnership agreement between us; but the DNS, proxy, and caching layer sitting in front of a site comes from outside, and when that layer goes down, so does the site. Our prototype boards come off a production line that isn't ours either. The real name for this relationship is dependency, not partnership — and a dependency has to be chosen deliberately.

That's why which infrastructure to use gets discussed as part of the project decisions, not as a preference tacked on afterward. Below are a few of the layers we build on today; the list changes by project and shortens or lengthens depending on the structure an organization already has in place.

The list changes by project. On every job, the infrastructure used is put together again to fit the organization's existing setup and what the work requires.

Our selection criteria

Availability of supply

A component that looks ideal on the datasheet isn't the right choice if it takes a long time to source or comes from a single supplier. We prefer parts that have an alternative and are widely available.

Durability

The fastest tool today can end up being the tool you can't find anyone to maintain three years from now. For us, this standard comes before performance.

Compatibility with the existing setup

A component that doesn't talk to an organization's existing systems raises the total cost even if it's technically superior. The cost of compatibility is factored in at the selection stage.

Room for independence

We don't lock in to a single supplier without discussing the cost of exit. A dependency built without knowing that cost works against you later, at the negotiating table.

Let's talk about working together

If you have a proposal or a question on this, let's start with a short conversation.

Get in touch