Skip to content
UVS

Technologies

65 tools in use

Tools are a consequence of the problem, not a position.

This list is generated from the stack each service and desk actually declares, so it cannot drift into claiming things nobody uses. If a tool is here, something on this site depends on it.

The index

What exactly would I be buying?

Every tool, and what it is used for.

Sorted by how widely each is used across the work. We change tools when the problem changes and we do not defend a choice because it is on a website.

How we choose

How does this start, and what do I get at each step?

Four rules, and none of them are about fashion.

  • 01

    It has to be leaveable

    Anything we build on has to be something you could hire for or migrate off. A tool that only we can operate is a dependency on us, and that is not a service, it is a hostage situation.

  • 02

    Boring where it can be

    PostgreSQL over something newer, unless the newer thing solves a problem PostgreSQL genuinely cannot. Novelty is a cost paid in operations for years.

  • 03

    Model choice is a measurement

    Because evaluation sets exist before prompts do, swapping a model is a scored comparison rather than a rebuild. That is why no model is named as a commitment here.

  • 04

    Your existing stack wins

    We work in your CRM, your helpdesk, your ERP. Migrating you to our preferred tool would be convenient for us and expensive for you.

Start

What is the next step?

Already running something? We will work in it.

The most useful first call is a description of what is going wrong. We will tell you which half of the business it belongs to, roughly what it costs, and whether it is worth doing.

Start a conversation