Dyad review

What is Dyad?

Dyad is a local, open-source app builder that combines a conversation with code and a running preview. Instead of keeping the entire development workflow inside a hosted builder, it gives you a desktop application and projects on your own machine. That can be appealing if you want to choose model providers and keep a practical route to independent development. It also means you take on more setup responsibility. Installing the app, managing model credentials, and understanding where the project runs are part of using it. We would think of Dyad as an approachable local development tool rather than a maintenance-free publishing service.

What’s changed in 2026

The recent release made Cloudflare Workers publishing generally available and added guided Neon deployment. It can also automate conversion from Vite to Nitro for that publishing route, reducing some manual configuration. Older descriptions that say you must always handle deployment entirely yourself are therefore incomplete. The new conveniences still involve external hosting and database accounts, so they do not turn the desktop app into an unlimited bundled hosting plan. These changes are most useful when local ownership matters but you would like help crossing the gap from a working project on your machine to an application that other people can reach.

What it’s like to use

The combination of chat, source, and preview can feel more understandable than switching among unrelated tools. Small web applications and focused MVPs are sensible starting projects. Model flexibility is another attraction, especially for builders who already have a preferred provider. The workflow does require attention to modes: asking for an explanation is not necessarily the same as asking Dyad to edit files. We would state the desired behavior, check that the intended file changed, and then confirm it in the app. This is particularly useful when an agent says a task is complete but the visible result does not match the response.

Where it falls short

Unchanged or blank previews can turn a simple iteration into debugging. As projects grow, managing context and input usage can also require more effort than expected. A local project gives you access to investigate those problems, but does not automatically explain them. Database changes are another important boundary: rolling back application code should not be assumed to restore the database or its data. Keep those recovery steps separate. When seeking a repair, describe the action that triggers the error as well as the message itself. That is more useful than sending a long log without explaining what the application was meant to do.

Pricing and credits in practice

Dyad Free includes Basic Agent access capped at 20 messages per day and requires your own API key. Pro costs $20 per month with 200 AI credits, while Max costs $79 with 900 credits. External model usage can have its own bill, and supported external subscriptions or models can incur an orchestration charge. Those distinctions make it important to track both Dyad and provider usage rather than comparing only the subscription headline. Free software can be useful without making inference free. We would begin with a bounded task and inspect actual consumption before deciding which paid level fits ongoing development.

Who should use it (and who shouldn’t)

We would choose Dyad for someone who values local project access and is willing to learn enough about model providers and hosting to remain in control. It is a good candidate for small web apps, exploratory tools, and a gradual transition toward working with code. It is less suitable for a person who expects unchanged previews, database recovery, and deployment errors to resolve without technical checking. Cursor offers a more general code editor workflow, while Bolt keeps development in the browser. Lovable is another option when a guided hosted start is more important than keeping the building environment on your own machine.

Bottom line

Dyad’s strongest reason to exist is the balance between accessible AI building and a project you can continue locally. The new publishing tools make that balance more practical, but do not remove the responsibilities that come with external models, databases, and hosts. We would choose it for independence and an understandable workflow, while budgeting time to investigate problems and review changes. A useful first app is achievable without surrendering direct access to the implementation. The tradeoff is that the builder must participate when the preview, source, and services stop agreeing about what the application is supposed to do.

Developer Resource

If you use Dyad to build AI-native features, a unified OpenAI-compatible API layer can make model switching, API key management, and inference cost planning simpler.

Explore ValueAPI