Actively building

Meshtein

Build. Learn. Explore.

A personal technology ecosystem and engineering laboratory, where products, engineering practice and learning are built as one long-term system.

It is under construction right now, and every part of it is described as it actually is — planned, exploring, or shipped.

Focus
Products · Engineering · Learning
Stage
Early — foundations
Principle
Documented as it is built

01Ecosystem

Five directions, and where each one really stands

These are the areas Meshtein is being built towards. None of them has shipped. Each carries the status it actually has, and nothing here links to a product that does not exist.

Meshtein Hub

The intended centre of the ecosystem: one place where its products and tools come together. Scoped as its own repository, not started.

Status: Planned

Meshtein AI

Applied AI and agent workflows inside the ecosystem. Currently an open question being tested, not a product.

Status: Exploring

Meshtein Cloud

Infrastructure and deployment for whatever the ecosystem eventually runs. A direction only; no architecture committed.

Status: Planned

Meshtein Learning

Structured learning drawn from real work — notes, experiments and material that fall out of building. Shape still being worked out.

Status: Exploring

Meshtein Services

Engineering offered as a service. Deliberately parked until there is finished work standing behind it.

Status: Planned

The list stays open. A direction is added here only once there is real work behind it.

02Projects

Projects will appear here as they ship

This section is reserved for work that is finished and usable, not for work that is intended.

Nothing is listed yet. The space stays empty until there is something real to put in it — no placeholders dressed up as products.

03Engineering

The work is documented as it happens

Meshtein keeps a written record of how it is actually built, while it is being built — not a tidy account reconstructed afterwards.

Decisions
What was chosen, and what it ruled out.
Experiments
What was tried, and what the result was.
Failures
What broke, and why it broke.
Fixes
What changed, and whether the change held.
Lessons
What carries forward into the next build.

Status

Engineering journal — coming as the project evolves.

04About

The builder

Meshtein is built and maintained by one engineer. It exists to do three things at once: ship real software, practise engineering deliberately, and learn by building rather than by reading about building.

The work is run as an engineering system rather than a portfolio. Scope is written down before it is built, changes go through review, and the state of the project is recorded as it actually is — including the parts that are still only an idea.

  • Build real things

    Nothing is announced before it exists.

  • Document reality

    Status is reported as planned, exploring, or shipped — never better than it is.

  • Learn by shipping

    Understanding comes out of finished work, not intentions.