Skip to main content
Every organization has its own technology constraints: approved lists, existing databases, in-house skills, and systems that have to keep running. You choose the stack a Web project is built on when you create it, either a tested pre-built combination or one you assemble yourself.
The stack is set once, when the project is created, and can’t be changed afterwards.

Choosing a Stack

In Create Project, select Web Application, then pick a Tech Stack: one of the pre-built stacks, or Custom. Prefer to build on a low-code platform your team already runs? See the Low Code overview.

Pre-Built Stacks

Building a Custom Stack

Custom offers four groups of recommended, pre-configured options. Each starts at None; choose at least one option, or write Special Instructions. The options are starting points, not limits. To build on something else entirely, leave every group at None and describe the stack you want in Special Instructions. The footer sums up your choices as you make them, for example Angular (Micro-frontends) + Python (Microservices) + PostgreSQL.

Architecture

Picking a frontend shows Frontend architecture: Single app, or Micro-frontends, where a shell app loads pages from separate apps by business area. Picking a backend shows Backend architecture: Unified, or Microservices, with one service per business area, each holding its own data and migrations. In both split designs, each part runs in its own container behind one gateway.
Unified and single-app builds keep most projects simple. Reach for microservices and micro-frontends when different teams own and release different business areas.

Special Instructions

Use up to 10,000 characters for anything the menus don’t cover: languages and frameworks not on the list, coding standards, naming rules, folder structure, extra libraries, or an accessibility standard such as USWDS.

Built-In Guidance

The form steps in before a conflicting choice can waste a build.
  • .NET Blazor replaces Frontend and Backend. Blazor builds both, so choosing it while a frontend or backend is selected offers a one-click Switch to .NET Blazor instead of letting the choices conflict.
  • A database without a backend. Veylo warns that the agent will write the data-access code itself, in the language you name in Special Instructions or one it chooses.
  • Database Viewer. Choosing a database turns on the Database Viewer and data snapshots for the project. See Codebase and Database.

Examples

Your Next Step

Whichever stack you choose, what the agent does with it is governed by a longer set of rules.

See how the agent works

Its tools, its operating rules, and the limits it works within.

Inspect the generated code

Browsing the codebase and querying the database.