Daveth

In development

Infrastructure engineering · Opening 2026

Understand it. See it. Configure it. Break it. Fix it. Prove it.

Daveth teaches Linux, networking, cloud, and automation as one stack — and doesn't call anything learned until you can produce the evidence.

— engineers waiting

The only thing we'll show you before launch

Every Daveth lesson ends in a state you can point at.

Six network nodes. Physical links appear, two candidate routes light up, and one route is finally selected. A B C D E F

Nothing is connected. Six devices exist. None of them can reach each other yet.

Scope

Being honest about this is the whole product.

Most platforms tell you what they include. The more useful list is usually the other one, so here are both.

What it is

One connected stack

Linux, networking, cloud, and automation taught as a single system, because that's how they fail in production.

What it is

Evidence over completion

A lesson isn't finished when you've read it. It's finished when you've produced output that proves the thing works.

What it isn't

A video library

Nothing here is a recorded lecture you watch at 1.5×. Every concept is an instrument you operate.

What it isn't

Ready yet

Curriculum and platform are both still in development. We'd rather say that than open a half-built product.

The difference

Most lessons end when you've read them.

Same concept, two teaching structures. Step through both and watch where they stop. The gap on the right is the entire product.

Step 0 of 6

How it's usually taught 0 / 4
  1. 01

    Definition

    Here is what it is.

  2. 02

    Diagram

    Here is a picture of it.

  3. 03

    Worked example

    Here it is working.

  4. 04

    Quiz

    Which of these statements is true?

  5. —

    nothing here

  6. —

    nothing here

Marked complete You can now say you finished it. Nothing was proved.
How Daveth does it 0 / 6
  1. 01

    Purpose

    Here is the problem this exists to solve.

  2. 02

    Familiar comparison

    Here is something you already understand.

  3. 03

    Where the comparison breaks

    Here is exactly where that comparison stops being true.

  4. 04

    Healthy

    Here is what correct evidence looks like.

  5. 05

    Broken

    Here is how failure changes that evidence.

  6. 06

    Proof

    Now produce the evidence yourself.

Proved You produced output that shows it works. So did we.

Step three is the one almost nobody ships. An analogy that is never bounded quietly replaces the real behaviour, and the learner never finds out which parts were the metaphor.

Founder

Why this is being built.

AM
Arif Mohammad Founder, Daveth Currently in product and curriculum development.
“Daveth exists because difficult technology should not require difficult teaching.”

I want Daveth to be useful to someone opening a terminal for the first time, and still credible to an experienced engineer testing production-level judgment.

That means a lesson cannot stop at a definition. It has to explain why the technology exists, compare it with something familiar, clearly state where that comparison becomes inaccurate, expose the real packet or process behaviour, and then let you prove the skill.

Daveth will not call a page complete merely because it has many sections, a clean design, or a successful build. It has to make sense to a beginner, survive expert review, and end in evidence.

Arif Mohammad · Founder

Waitlist

Be there the day it opens.

— engineers waiting