What changed in Milvey, and what I’m building now.

Milvey is built by one person. Each entry below says what changed and where it stands. The weeks are a sample timeline while the product is in early build.

in demo
2
in demo
in progress now
1
in progress now
next up
1
next up
planned for later
1
planned for later

2026

I build Milvey alone and write down what changes each week.

In demo means it works in the demo, with no real runs yet. Building means I’m on it this week. Next and Planned are decided but not started.

Each entry gets a real date and a screenshot once the first public build is out. If something you need isn’t on this list, reply to the first email and tell me.

Faiz

  1. Week 01

    In demo

    Workflow import v0

    Drop a ComfyUI JSON into Milvey and it lists the custom nodes and model files the graph needs, by name, before anything runs.

  2. Week 02

    In demo

    Node and model resolver

    Node packs are pinned to a git commit, so a workflow that ran last week runs the same way today. Model weights are matched by hash and cached after the first download.

  3. Week 03

    Building

    Expose inputs, get a form

    Click a widget in the graph to put it on the form. The rest of the graph stays hidden from whoever fills the form in. This is what I’m working on now.

    Macro of a mechanical watch movement (description; prompt not published)
  4. Week 05

    Next

    Template library and versions

    Save a workflow, fork it, roll back to an earlier version, and share a pinned version without showing the graph.

  5. Later

    Planned

    Endpoints and studio apps

    A saved workflow becomes an HTTP endpoint, and a template becomes a form you can hand to a client.

Get an email when signups open.

An email when signups open. Unsubscribe any time.

Tell me which workflow to support next.

Join the list, then reply with the ComfyUI JSON or model you need. Replies help me pick what goes into Next.

Email when signups open · Unsubscribe any time