# Our Approach to Engineering

## Other companies resell someone else's kit. We design our own patentable hardware and pass on savings of up to 80%.

<figure><img src="/files/wH7CpkWMjH0PY5JgsYTz" alt=""><figcaption><p>Computle V1 Blade Workstation</p></figcaption></figure>

***

A typical VDI provider will purchase off-the-shelf servers or workstations, cram a bunch of virtual machines onto them, and place them in a data centre.\
\
Whilst this is fine for some use cases, when you start to scale the service or use more demanding application, the platform's users start to face *significant* barriers and bottlenecks.\\

* You'll experience CPU, GPU and disk contention.
* Your costs will be significantly more than a regular computer or workstation.
* And you will inefficiently utilise data centre space, resulting in poor-cost optimisations and a difficultly adding more nodes efficiently.

**Computle took a different approach from day one.**\\

**‍**At the outset of Computle's foundation, Jake engineered his own hardware, placing an emphasis on dedicated, single-user servers/workstations.\
\
We are now on *revision four* of our hardware, and currently operate Computle from a series of blade workstations, each equipped with:‍

* A dedicated CPU;
* A dedidicated GPU;
* And a dedicated NVMe and RAM modules.

Because of this, each Computle seat delivers unparalleled performance compared to VDIs, with each seat/user having dedicated access to an entire blade workstation.\
\
**What's more, each Computle blade costs around half the price of off-the-shelf hardware, enabling us to pass on significant cost savings to our customers.**


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.computle.com/corporate-governance/computle-ethos/our-approach-to-engineering.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.