Ecosystem

The platform around the runtime matters too.

Wevoa is more than syntax and routing. The official packages, starter packs, download flow, and deployment choices are part of what makes the platform usable.

Packages

Official packages

Core packages such as @auth, @db, and @utils give projects a real starting point without turning the framework into a dependency maze.

@auth for session-backed authentication
@db for database helpers and query wrappers
@utils for response and helper functions

Starters

Starter packs

Wevoa ships with focused built-in starters instead of a cluttered example collection.

app for a minimal production-grade starting point
dashboard for an auth + CRUD starter built with official packages

Platform

Product ecosystem

The runtime, installer, packages, docs, starters, and download flow are designed to feel like one platform instead of separate tooling islands.

Single-binary runtime distribution
Installer-first onboarding on Windows
Static export and runtime hosting paths

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.

Great for docs, product pages, and landing sites
Deployable to Vercel and other static hosts
Live data is captured at build time

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.

Best for dashboards, internal tools, and products
Keeps Wevoa routing and server helpers active
Deploy on a VPS or normal server environment