Enkido
How to use Enkido

From a requirementto a solution you can build.

Six steps, the same for every kind of infrastructure. Write what you need as you would to a senior consultant; Enkido asks when something is missing, designs across vendors, argues the design through, checks it, and hands you the pack.

1

Create your account

Register with your email, your organisation (it goes into the title block of every drawing) and how your designs run.

  • Your own keys: your runs cost nothing; a version's Visio files, workbooks and documentation unlock for a fixed fee.
  • Enkido's models: each run is charged from the tokens it used, never below a minimum.
Create your account CREATE ACCOUNT
2

Describe the requirement

Write it in your own words: sites and users, applications and where they run, compute, storage, security and cloud, the vendors you prefer, and what must keep working when something fails. Attach what you have: a sketch, an existing Visio drawing, a PDF of the tender.

  • Up to 25 MB a file
  • Choose the kind: an infrastructure design or a workflow
  • Nothing is invented: what is missing becomes a question
sketch.png site-a.vsdx tender.pdf
3

Follow the discussion

The designer writes the design; the reviewer raises points; each point is accepted and fixed, or defended with a reason. You watch every round in the activity column.

  • When something only you can decide is missing, a question card appears
  • Answer it, or choose Design it anyway and every assumption is listed
Version 1 is ready Point: no second WAN path Accepted in version 2 Agreed
4

Read the checks and the drawing

Every version is checked against seventy-six engineering rules before you see it. The drawing preview, the checks and the scorecard are free to see on every version.

  • A failing check sends the design back to the designer, not to you
  • What cannot be proven is listed in the documentation
Sizing Cabling N-1 Traceability
5

Unlock and download the pack

Open Export on a version: the Visio topology and flows, the Bill of Materials, the sizing workbook, the rationale and the design itself, one by one or all together in one ZIP.

  • Hosted runs: the outputs are yours when the run ends
  • Own keys: unlock a version once, download it as often as you like
.vsdx .xlsx .md .zip
6

Change it, version by version

Write what should change in the same project and run again: a new version is made from the last one, and every earlier version stays as it was.

  • Each version keeps its own drawing, checks and discussion
  • Delete a project when it is no longer needed
v1 v2 v3, the latest
What the agent holds for you

Your intent, turned into a design you can stand behind.

The craft beneath it stays out of sight; what reaches you is its result. A design questioned before you read it, and documents that agree with one another down to the last figure.

Describe the need in your own words; it asks only what would change the design.
Drawings, workbooks and documentation arrive together, and they agree.
Each design is argued, tested and corrected before it reaches you.
Every version is kept, so each change can be traced and each decision revisited.
Questions

What people ask before their first design.

What should I write?

What you would tell a colleague who is going to design it: the sites and how many users each has, the applications and where they run, the compute, storage and security they need, what must keep working when a component or a link fails, the vendors you prefer or must use, and any limits (budget, rack space, existing equipment). Missing details become questions; nothing is guessed silently.

What does a design cost?

With your own model keys, runs cost nothing and a version's outputs unlock for a fixed fee. On Enkido's models, each run is charged from the tokens it used, never below a minimum. One credit is a small amount. The preview, the checks and the scorecard are always free.

Which models can it use?

Enkido works with thirty-two model providers, among them Claude, Gemini, GPT, Mistral and OpenRouter, and with models on your own servers (LM Studio, Ollama). The designer should be a strong model; smaller local models do well as reviewers.

What if the checks fail?

The design goes back to the designer with the failing checks, and a new version is made. You see the final version with its scorecard; what the checks cannot prove is written down in the documentation.

Where are my files kept?

With your account, on the server Enkido runs on. On an Enterprise installation that is your own server, on your own premises. Deleting a project removes its versions and files.

Can we run it on our own servers?

Yes: Enkido Enterprise installs on Linux, Windows or Docker, also without internet access, with your own HTTPS certificate and updates signed by your supplier. Contact us for a license.