Skip to main content
Everything on this page happens on your machine. No account, no database, no model API and no network call until you choose to publish.
1

Install the CLI

See Install for the Homebrew and Scoop routes.
2

Create a workspace

cordango new needs an empty directory. It creates a workspace and its first app. One workspace holds many apps, so cordango add app <name> adds the next one.
3

Check it

Parse, lower and validate. No model, no database, no network. This is the command to keep in a pre-commit hook and in CI, and it works from a clone of the open source repository with nothing else installed.
4

See what you can build it into

Each target reports what it can generate and what it deliberately won’t. Ask whether one specific target can build one specific app:
5

Generate the application

That writes a complete ASP.NET Core, EF Core, PostgreSQL, Vue 3 and Vuetify project into generated/support/. It’s ordinary source code, and it’s yours. What comes out has no license server, no account and no runtime dependency on Cordango.
6

Run it

The first screen asks you to create the administrator account. A password delivered by a log line isn’t really delivered, so the endpoint that creates that first account closes for good once it has been used.

​
When the generator can’t finish

Missing behaviour is loud. If an app uses something the target can’t generate yet, the build refuses instead of quietly producing an application that’s subtly wrong.
--allow-incomplete accepts the build anyway, and tells you exactly what got left out.

​
Next

Build with an AI agent

Tuned starting prompts for Claude Code, Codex, Cursor and GLM.

Concepts

What a workspace, an app and an App Definition actually are.

Editing an app

Changing semantic source, and the four rules worth knowing.

Deploying

Running what the generator produced.