Skip to content

Veva core · Veva.Web

A Blazor CMS in one line of .NET.

builder.BuildVeva() gives you the host. Modules load themselves, pages route by wildcard, and the editor, the admin API and an MCP endpoint come with it. Everything else is a package.

dotnet add package Veva.Web.Essentials

What it does

Small pieces, plain .NET Blazor.

One call

BuildVeva() sets up routing, sign-in, static assets and the setup wizard, on SQL Server or PostgreSQL.

Modules

A module is a class that implements IModule. It registers services, components, hooks and endpoints.

Components with metadata

EditorBrowsable properties become settings, AgentHint tells AI agents what a component is for.

Themes

A theme sets the layout, breakpoints, CSS classes and colour palettes. Templates hold its settings.

Data binding

Bind {_PageTitle}, a query string value or a document field into any text, in every render mode.

Ready for agents

An MCP endpoint at /mcp gives AI agents the editor's tools, with the same permissions.

How a request is served

From an address to HTML.

  1. 01

    Request

    Every path outside /_, /veva, /api and /library is a page address.

  2. 02

    Resolve

    The page is found, then routing rules run for redirects and other addresses.

    IRoutingRule
  3. 03

    Prepare

    Page request hooks and the theme add the layout, scripts and meta tags.

    IPageRequestHook
  4. 04

    Render

    The layout renders the template's areas. Each component runs through its render hooks.

    IContentRenderHook
  5. 05

    Respond

    HTML in the page's render mode: prerendered, interactive, or static for bots.

    ComponentRenderMode

For developers

Start with Program.cs.

BuildVeva() replaces the Blazor boilerplate. Your own code goes in modules, which Veva finds and loads at startup.

Program.cs
using Veva.Web;

var builder = WebApplication.CreateBuilder(args);
var app = builder.BuildVeva();
app.Run();

// A module of your own, found and loaded at startup
public class MyThemeModule : IModule
{
    public string Name => "My Theme";
    public int Priority => (int)ModulePriorityEnum.Default;

    public void ConfigureServices(IServiceCollection services, IConfiguration configuration)
    {
        services.AddNamed<ITheme, MyTheme>(Name);
    }
}

Keep reading

Guides for this module.

All articles

Guide

Creating modules

The unit every feature of Veva is built from.

Read the guide

Modules

What it is made of.

All of them come with Veva.Web.Essentials.

Module library

Essentials

Veva.Web.Essentials

Veva.Web.Core plus pages and the designer, documents, forms, navigation menus, routing, cookie consent, logging and background tasks.

Layer
dotnet add package Veva.Web.Essentials

Web core

Veva.Web.Core

Veva.Web plus the admin, the asset library, tags, the audit log and the setup wizard.

Layer
dotnet add package Veva.Web.Core

Web

Veva.Web

The host: BuildVeva(), the module loader, components, themes and data binding.

Layer
dotnet add package Veva.Web

Admin

Veva.Modules.Admin

The admin at /veva: the editing views, the Users, Websites and Versions sections, and the e-mail settings.

Built in
dotnet add package Veva.Modules.Admin

Audit log

Veva.Modules.AuditLogging

Records what users do through the admin, in the Audit Logs section. By default requests are kept 90 days and changes a year.

Built in
dotnet add package Veva.Modules.AuditLogging

Setup wizard

Veva.Modules.Setup

The first-run wizard at /veva/setup: it connects the database, creates the first user and website, then restarts the site.

Built in
dotnet add package Veva.Modules.Setup

MCP server

Veva.Modules.MCP

The MCP server at /mcp and the admin's AI assistant. Each module adds its tools: pages, documents, assets, tags, menus and routes.

Built in
dotnet add package Veva.Modules.MCP

Pages

Veva.Modules.Pages

Renders the pages: finds the website, page, template and theme, serves the 404 page and security headers, and holds the page settings.

Built in
dotnet add package Veva.Modules.Pages

Routing

Veva.Modules.Routing

The route table in the Routing section: 301 and 302 redirects, and routes that keep the address. Also alternative addresses for a page.

Built in
dotnet add package Veva.Modules.Routing

Logging

Veva.Modules.Logging

Writes the site's log to the database, and shows it in the Logs section, filtered or live.

Built in
dotnet add package Veva.Modules.Logging

Task daemon

Veva.Modules.TaskDaemon

The Tasks section: schedule background tasks by interval or cron, run one now, and read its history and log.

Built in
dotnet add package Veva.Modules.TaskDaemon

Hangfire

Veva.Modules.Tasks.Hangfire

Runs the task daemon's tasks on Hangfire, with Hangfire's dashboard for administrators at /_veva/hangfire.

Built in
dotnet add package Veva.Modules.Tasks.Hangfire

More of Veva

Explore the other features.

Each one is made of modules. Reference a package, restart, and its components are in the editor.

All features

Page builder

Compose pages from components, then preview and publish

Open

Components and data

Components that show, components that fetch, and the binding between them

Open

Documents

Structured content you list, filter and serve anywhere

Open

Forms

Document forms that save, generic forms that filter or post

Open

PDFs and signing

Form answers made into a PDF, downloaded or sent to be signed

Open

Assets

One media library, with images sized on request

Open

Search

Crawl, index and search the whole site

Open

AI and agents

The admin's AI assistant, and the MCP server coding agents connect to

Open

Tech stack

Plain .NET Blazor: three render modes, standard components

Open

Integrations

Data sources, sign-in, mail, analytics and media

Open

Module library

Every module: what comes with Essentials, and the add-ons

Open

Type to search the docs, components and API.

↑↓ to move ↵ to open Esc to close Search by Veva