WevoaWeb Runtime 786.0.0

Build web apps with one language, one runtime, and one clear server-first model.

Wevoa brings together a custom language, templates, routing, packages, and CLI tooling into one installable platform for HTML-first products. It is built for teams that want the stack to feel smaller, clearer, and easier to ship.

Runtime

1

single binary

Language, templates, routing, CLI, and build flow ship together.

Shipping

2

deployment paths

Export static sites or run the full Wevoa runtime for dynamic apps.

Model

0 JS

required by default

The primary path stays HTML-first and server-rendered.

Why Wevoa

A smaller stack that still feels complete.

Wevoa is designed to keep the important parts of web development together instead of scattering them across multiple tools, frameworks, and conventions.

Core

Language and runtime together

Wevoa is designed as one system, so templates, routes, values, imports, and execution semantics fit together cleanly.

Framework

Full web stack built in

Routing, sessions, CSRF, uploads, JSON helpers, static assets, and SQLite are already part of the runtime.

Tooling

CLI that ships the platform

Create, doctor, build, serve, package, and install flows all come from the same binary and the same product surface.

Shipping

Deployment choices without framework drift

Frontend-only sites can export static HTML, while full-stack apps still run with the full Wevoa backend.

Deploy the right way

Frontend-only sites can export static HTML. Full-stack apps still run on the full runtime.

You do not have to force every project into the same deployment model. Wevoa supports a static export path for public-facing frontend sites and a full runtime path for apps that need live routes, sessions, or database work.

Static

Static export for frontend sites

Use `wevoa build --static` when the site is mostly pages, docs, marketing, or download content. The output is plain HTML, CSS, assets, and files ready for static hosting.

Runtime

Full runtime for dynamic apps

Use `wevoa serve` when the app needs live route execution, sessions, database access, form handling, or request-time API calls.

Wevoa runtime flow diagram

Contributors

People building Wevoa in the open.

The contributor board is rendered by Wevoa itself from GitHub data. The founder stays pinned at #1, and everyone else is ranked by repo commits.

Live GitHub data

Founder pinned at #1

Rendered by Wevoa

#1

Founder

19 commits

Abdul Ahad S avatar

Abdul Ahad S

@AHADBAVA

Pinned at the top of the official contributor board. Founder details are loaded through Wevoa, and everyone else is ranked below by repo commit count.

2

contributors ranked

20

public commits tracked

#1

founder always pinned

Ahmad avatar

#2

Ahmad

@ahmadshajhan

1 commit

Ranked live from the Wevoa repository contributors list by public commit count.

Fetched by Wevoa from the GitHub API.